Earlier this morning while working on a CentOS Linux development server I received errors when doing anything with the yum package manager. I believe the error started after upgrading the kernel on the server from kernel version 2.6.18-164.15.1.el5 to kernel version 2.6.18-194.3.1.el5. After upgrading the kernel yum would output the same error multiple times as shown in the below output example.
Yum Package Manager Error After Upgrading Kernel On CentOS Linux:
- [root@cent1 ~]# yum list *YUM*
- Loaded plugins: dellsysid, fastestmirror
- Loading mirror speeds from cached hostfile
- * addons: yum.singlehop.com
- * base: holmes.umflint.edu
- * epel: ftp.osuosl.org
- * extras: mirrors.serveraxis.net
- * rpmforge: ftp-stud.fht-esslingen.de
- * updates: pubmirrors.reflected.net
- (process:4197): GLib-WARNING **: gmessages.c:387: could not find handler with id `939534952' for domain ""
- (process:4197): GLib-WARNING **: gmessages.c:387: could not find handler with id `939534952' for domain ""
- (process:4197): GLib-WARNING **: gmessages.c:387: could not find handler with id `939534952' for domain ""
- (process:4197): GLib-WARNING **: gmessages.c:387: could not find handler with id `939534952' for domain ""
- (process:4197): GLib-WARNING **: gmessages.c:387: could not find handler with id `939534952' for domain ""
I am not 100% sure on what resolved the issue but I wanted to list the steps I took which ended up resolving the error. Below are the steps taken and when yum started working properly again.
Steps Taken To Resolve Yum Errors:
- Yum Clean Cache: I thought that maybe clearing the yum cache as shown in the below example output would resolve the issue however it did not.
- [root@cent1 ~]# yum clean all
- Loaded plugins: dellsysid, fastestmirror
- Cleaning up Everything
- Cleaning up list of fastest mirrors
- Reboot Server: After running the above yum clean command I rebooted the server. Once the server was back on the network after being rebooted I attempted to use yum again but received the same errors.
- Update glibc: Next I used yum to update glibc and all of the required dependencies thinking that maybe the kernel upgrade caused an issue with glibc. After upgrading glibc the yum errors still existed.
- Complete CentOS Server Update: After this I decided to upgrade every package on the server using the “yum update” command. Still after upgrading everything the error existed.
- Yum Clean All Cache: Again I ran “yum clean all” to clear the cache in an attempt to correct the issue after upgrading all of he packages on the server but the yum errors still existed.
- Reboot CentOS Server: I again rebooted the server and once the server was back online issued the same yum commands that had been causing the errors and this time they were corrected.
So while I am not exactly sure which step or package upgrade resolved the issue I do know that upgrading the kernel appears to have caused the initial problem and taking all of the above steps corrected the problem with the YUM (Yellowdog Updater Modified) Package Manager.
