On Wed, 2 Jul 2003, Oisin Feeley wrote: > On Wed, 2 Jul 2003, djh wrote: > > > On Tue, 1 Jul 2003, Oisin Feeley wrote: > > > Hi, > > > I've been attempting to update an unregistered (with Red Hat) machine by > > > downloading the errata and then installing them. I ran into an error > > > with the glibc and glibc-common errata: > > > > > > Preparing... ##################################### [100%] > > > 1:glibc-common ##################################### [50%] > > > 2:glibc ##################################### [100%] > > > error: %post(glibc-2.3.2-27.9) scriptlet failed, exit status 121 > > > > > > any other attempts to use rpm (or any other command) result in a > > > segementation fault. > > > > Sounds like you upgraded to the i386 glibc RPM instead of the i686 RPM. > > See this URL for more details (and how to fix it). > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88456 > > > > Ah.... this seems like the business, thanks David. I'll report back on > success or otherwise in an hour or so. I guess I should really get into > the habit of searching bugzilla first before I bother the list. Thanks > for all the helpful suggestions guys. > OK, in the rescue environment I checked the installed rpms for the kernel etc for whether or not the problem was an i686/i386 mismatch as suggested by Mike Chambers. I used "rpm --root /mnt/sysimage -q --qf '%{arch}\n' kernel" and indeed the system was i686. So, I then rpm'ed over a copy of the glibc-2.3.2-27.9.i686.rpm using "rpm --root /mnt/sysimage -Uvh glibc-2.3.2-27.9.i686.rpm" and it installed after throwing up the usual db4 errors. The system now reboots perfectly. The problem all came down to not checking (as suggested by Mike Chambers (and also Jakub Jelinek in the URL cited by David) whether the system is i386 or i686 and then blindly rpm'ing the update rpms. The problem would be avoided by using up2date. For various reasons the latter wasn't an option for me with this system. Thanks a bunch to all that replied, Oisin Feeley
