cPanel/WHM messed with CentOS updates

[thisisit3]

Today the cPanel update script exectued "yum update" which failed to update anything.

I did a manual "yum update" to see what went wrong and found this:

--> Running transaction check
--> Processing Dependency: glibc-common = 2.3.4-2.25 for package: glibc-dummy-centos-4
--> Finished Dependency Resolution
Error: Missing Dependency: glibc-common = 2.3.4-2.25 is needed by package glibc-dummy-centos-4

Anyone having a similar problem?

[Smithjp]

On the VPS do

rpm –qa | grep glibc

it will list the glibc rpms installed on the VPS, look for an rpm glibc-dummy-centos-4 and erase it by

rpm -e glibc-dummy-centos-4

glibc-dummy-centos-4 is developed by swsoft. It is save to deinstall this package from a VPS before upgrading glibc.

[thisisit3]

Thanks, its working fine now and updates are being installed as we speak.

[thisisit3]

CentOS 4.4 update to CentOS 4.5 is now complete.

Only thing that i haven't yet solved is the file /sbin/ifup, the new rpm installed it as /sbin/ifup.rpmsave. I've taken a look at the differences:

diff -u /sbin/ifup /sbin/ifup.rpmsave |less

there are 6 changes but i'm not sure if my old ifup has been modified for a reason, so i'm not sure if i should overwrite it with the new one.

[Smithjp]

As far as I know, .rpmsave file contains the old version of the file. The original file has been replaced by the file contained in the RPM.

[thisisit3]

Nope, its the exact opposite, the .rpmsave is the new file and its only created of the existing file has been modified (based on the original of the previous RPM).

For example, the upgrade also created the files issue.rpmnew and issue.net.rpmnew, both of which contain the new version numbers (CentOS 4.5 etc) but they don't replace the existing ones which contain a custom disclaimer.

[Smithjp]

rpmnew file contains the new file from the RPM so thats fine. What repositories you are using for YUM?

If your file contains specific changes, then it will not be overwritten. The 'new' default file from the update package is installed as rpmnew.

Some updates may involve default config file settings that were unsafe or made obsolete in a major rewrite. In such cases the new might be installed and your old file renamed as something.rpmsave.

[thisisit3]

i'm only using the default "base" and "updates", so far i haven't needed anything else.