Does produce anything helpful?

Hi,
I just showed me this.


I waited for almost 10 minutes just there.

yum check can take a while. I would start it and walk away. Last time I ran it, I think it took almost an hour.

Hi Tyler,
I followed your advice and left it and below is the results.

This is no big deal. It looks like you have duplicate packages 'installed'. I am assuming you still have nss-3.36.0-9.el6_10.x86_64.rpm and yum-3.2.29-81.el6.centos.0.1.noarch.rpm from when you used rpm to reinstall everything manually using rpm. If not, download them again.

Try this:

I am hoping that will get rpm to remove the older versions. It has been a while since I have ran into this. Worst case, you can tar up the files installed by rpm and yum, delete the packages, untar them, and reinstall the packages.

Hi Tyler,
Mine is

the nss is slight different then yours.

I tried running your commands.

@newbie14: I think what tyler2016 asks you to do is way beyond your current Linux skills.
The two tar commands above are meant to be backups of the files in the nss and rpm packages. These backups are needed in case the rpm --force -F command below causes more damage:
You were confused by tar's informational message, thinking that it was a request to remove the leading slash:
In fact, the above is not an error message but just information. Tar has removed the leading slash. Your backup has been made and is in file /root/nss.tar.
Tar reports an error since there is no directory named root in your current path.

Hi Berndbaucsh,
Yes I got confused here. So what exactly should I run now to ensure I follow you guys correctly. Which command to run and should I create any directory ?

I want to learn further . What does this two commands do ? Why this needed in the first place ?
tar cf /root/nss.tar $(rpm -ql nss)
tar cf /root/rpm.tar $(rpm -ql rpm)

Those create backups of the packages that have multiple versions installed. Now that I think about it, I would add the full version to the rpm -ql to ensure you are getting the correct files. This is in case the attempt to force rpm's update process, which should remove the older versions goes awry and you aren't left with a system with no rpm or nss. nss is a crypto library that a lot of applications use (yum is one), so you don't want to make sure you have a working version. I meant for you to backup yum instead of rpm. It was a tired moment.

Try this:

As mentioned earlier by berndbausch, tar's message about the leading slashes can be safely ignored. The tar command will still work as it should. If that doesn't let you do a yum reinstall '*', you can always remove the duplicate rpm's altogether with rpm and install the correct versions.

Hi Tyler,
I followed exactly as you mentioned. What you backing up is just the file which I have downloaded previous day right ?

My nss version in the recover folder is
and yum is

You are backing up rpm in case the attempt to resolve the conflict fails. Then you can restore from the tar files and fix your system. Are the files you downloaded still on your system? Rpm doesn't know anything about repositories, so you have to give it the location of the package files you wish to install as command line arguments.

Try backing up nss again. I didn't realize the .0 was part of the package name. Don't worry about the warnings. The added option prevents tar from failing when files are missing.

Do the same rpm command again, except this time make sure the files are available in your current working directory.

Hi Tyler,
So you are backing up using tar but the original file is still in the recover folder right. Yes I still have all the .rpm which you ask me to download is still in one of the folders. The folder is called recover.. So you can see I cd into it and ran this.

I am assuming the rpm files are there from when you downloaded them. Those messages are fine. It worked correctly. At this point, try using rpm as in post 24 to force an upgrade of the packages.