I was having problems with GPG ring for Red Hat Entreprise while using up2date, I asked support at the ServerMatrix DC if they could look into it. I also started trying to use up2date myself, and after some more problems occurred, rebooted the server. Then I got a reply to my support ticket saying the reboot screwed things cos they were almost done fixing it. I said ok, won't touch the server until they say so.
Then I get a reply saying that the reboot caused glibc to be corrupted cos they were in the middle of rebuilding some of the files at the time, and that it would need an OS Reload.
Is there any way to fix this glibc problem without an OS reload? Is it for sure that the glibc is the problem here?
Try to uninstall glibc using rpm -e command and then reinstall it (rpm -ivh )...you can get glibc rpm form http://rpmfind.net or from redhat download. ServerMatrix support will be able to more idea about the rpm: relocation error:
Originally posted by shibucvarughese Try to uninstall glibc using rpm -e command and then reinstall it (rpm -ivh )...you can get glibc rpm form http://rpmfind.net or from redhat download. ServerMatrix support will be able to more idea about the rpm: relocation error:
The admin there says that "It would take a good bit of admin time to even try and correct this issue"... which is weird, because according to him, the error was caused when I rebooted while he was recompiling stuff, but I didn't even ask him to modify anything, just asked him if he had any clue about what might be causing a GPG keyring error.
I guess I should ask again?
Also, which RPM would I need for Red Hat Enterprise?
rpm will not work, because it itself uses glbc!
Get the rpm to your local computer (suppose you use linux) extract it (rpm2targz, or other), and upload (if you can) to your server and replace the files.