Redhat 9ish.

Ok I've seen some threads around this topic, but all are slightly different than my situation.

I upgraded to glibc-2.3.2- and whenever I run rpm in a situation where dependencies are okay (i.e. when it is ready to install), I get a segmentation fault.

Everything else in the system (that I've tried) seems to work... it boots normally, and everything else seems to be running fine.

From what I glean from various postings, I need to upgrade rpm so that it jibes with the version of glibc I have.

I tried to boot via disk, and went into linux single user mode, but when I do rpm, it gives a segfault there, too!

How do I repair rpm long enough to repair rpm?

Thanks,
Dave

Whoops didn't fill out the version of glibc.

It's: glibc-2.3.2-27.9.7

I did the i686 version of it.

rpm is: rpm-4.0.4-7x

Dave

Rescue mode on your first CD provides a working rescue environment including a working version of RPM. Notice that unless you chroot into your mounted system, you can use the rescue mode's rpm together with a proper --root parameter to install/upgrade packages in your mounted system.

Sadly, I don't actually have a CD-ROM drive attached to the box.

Can I drop the image on the hard drive, and read it off from there?

Thanks,
Dave

The important bit is to boot into it, not to read it.

Does rpm2cpio still work? If so, you can read out a known good version of an rpm package and overwrite your installed files with it.

I don't know if this is a good idea or not, but you can access the components of an rpm package file by using the Midnight Commander program (mc).

Wow, the rpm2cpio trick worked.

It wasn't easy, I had to do all sorts of copying of libraries by hand (including all those weird symbolic links), but in the end, it actually worked.

Many thanks!

Dave

Dear Friends,

I am also facing the same problem of RPM segmentation fault after upgrading GLIBC. After booting with rescue CD, what I am supposed to do? I mean I have to reinstall the RPM package itself (rpm-xxxxx.rpm) or the software which I try to install in normal mode should be installed in this single user mode? If is second, for every software installation in future I have to do like this?

Regards
T.KaruppuSwamy

The former - you only have to update RPM and any dependent packages. The problem arises from an inconsistency between glibc and RPM, so once you get RPM up to date, you're good to go.

-Dave