LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions
User Name
Password
Linux - Distributions This forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on... Note: An (*) indicates there is no official participation from that distribution here at LQ.

Notices

Reply
 
Search this Thread
Old 05-01-2003, 03:57 AM   #1
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Rep: Reputation: 15
windoze-like nightmares with rpm upgrade of glibc on RH9


After half a year happy Redhat Linux (first 8.0 and now 9)
I finally experienced Windows-like nightmares when I tried to
use rpm to upgrade glibc.

Older and wiser now, I realise that glibc is pretty fundamental
so that if anything goes wrong here, everything may get screwed up.
And so it did:

[root@greifswald Installs]# rpm -Uvh glib*
Preparing... ###########################################
[100%]
1:glibc-common ###########################################
[
33%]
2:glibc ###########################################
[
67%]
error: %post(glibc-2.3.2-27.9) scriptlet failed, exit status 121
3:glibc-devel ###########################################
[100%]

After this, any further attempts to rpm got "Segmentation fault",
I couldn't open a new xterm, and finally the system crashed and
would not reboot [I'll spare you the gory details of what it did do,
though they probably would give a clue as to what had got ****ed-up].
I couldn't figure out how to get out of the mess and finally installed RH9
Linux anew on the second hard disk so that at least I could recover
my data from the first.

Was I just being stupid or is there a bug in the rpm's?
Is there a way I could have cleverly backtracked and got out
of the mess, with the the emergency rescue disk?
 
Old 05-01-2003, 04:14 AM   #2
mhearn
Guru
 
Registered: Nov 2002
Location: Durham, England
Distribution: Fedora Core 4
Posts: 1,565

Rep: Reputation: 47
Yeah, I really need to bug Jeff about putting in some form of warning into RPM for users trying to upgrade glibc. A bit Windowsish but way too many people have trashed their machien doing this. What with all the press about this upgrade due to Wine/Java breaking, people have been turning their attention towards it a lot.

Anyway, you can probably boot up a rescue system and force the reinstall of the default RH9 glibc package. rpm --force -Ivh glibc-2.3.whatever....

I rather suspect that you used an RPM of glibc not designed for Redhat 9 - glibc isn't like other packages, you don't upgrade it unless there's a security fault with it.
 
Old 05-01-2003, 04:55 AM   #3
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Original Poster
Rep: Reputation: 15
Thanks very much for the instant and useful reponse. Actually, I got the very latest rpm's for glibc, glibc-common, and glibc-devel from redhat network itself, and they were specifically built for redhat 9. So I think I was rightly surprised that everything went so spectacularly wrong. Haven't seen anything like it since windoze days (when of course it was a daily - now let's be honest, monthly - occurrence).

I'm a bit wary of getting myself into the same trouble again just to test this rescue business, but in case I do, just for the zen of it: do I need to have the old rpms somewhere in order to do this downgrade from the emergency disk? Don't I need to tell rpm that it is the rpm packages on the hard disk which I want to downgrade, not the rpm packages on the rescue floppy?
 
Old 05-01-2003, 04:57 AM   #4
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Original Poster
Rep: Reputation: 15
PS, it was redhat up2date itself which told me there were bugs in glibc (connected even with security issues) and that I should do the upgrade...
 
Old 05-01-2003, 05:02 AM   #5
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Original Poster
Rep: Reputation: 15
PPS. see also
http://www.linuxquestions.org/questi...threadid=55653
 
Old 05-05-2003, 01:24 AM   #6
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Original Poster
Rep: Reputation: 15
PPPS. and see

http://www.linuxquestions.org/questi...threadid=56690
 
Old 05-05-2003, 06:10 PM   #7
ogms
LQ Newbie
 
Registered: May 2003
Posts: 2

Rep: Reputation: 0
GLIBC -- bug reported -- solution on bugzilla

https://bugzilla.redhat.com/bugzilla...g.cgi?id=88456
 
Old 05-06-2003, 12:31 PM   #8
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Original Poster
Rep: Reputation: 15
Re: GLIBC -- bug reported -- solution on bugzilla

thanks! Iit's very difficult to find anything on redhat's website if you don't know in advance exactly what you are looking for. i had forgotten about bugzilla.
 
Old 05-18-2003, 02:18 AM   #9
pf1359
LQ Newbie
 
Registered: Mar 2003
Location: STL USA
Distribution: SuSE 9.0
Posts: 22

Rep: Reputation: 15
I had a very similar problem on a fresh install of RH9. I installed apt-get, and then did 'apt-get update' and 'apt-get dist-upgrade'. I got several failures during the dist-upgrade, including apparently glibc. After it was finished, I got segmentation faults whenever I tried to use apt-get or rpm. Fortunately, it was a fresh install, so I just started over. Guess I will stick with up2date for now...
 
Old 05-18-2003, 05:23 AM   #10
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by pf1359
Guess I will stick with up2date for now...
According to the bugzilla page mentioned earlier in this thread, some people have had this problem while doing everything according to the book, including using up2date! So first study the instructions there on how to recover gracefully. It seems that the problem occurs when up2date tries to install an i386 rpm over an older i686 rpm. At the very end it should remove files left from the old package. But then it notices that those files belonged to a more advanced computer architecture and refuses to do the job. I was in the lucky position that I had a second
and empty hard disk, so could do a fresh install on a second disk and then salvage my files from the first. I still have to see if I can repair the damage done on the original installation.
 
Old 05-18-2003, 08:55 AM   #11
pf1359
LQ Newbie
 
Registered: Mar 2003
Location: STL USA
Distribution: SuSE 9.0
Posts: 22

Rep: Reputation: 15
I would guess, if it's a problem with glibc, you could ignore that package before performing up2date. That's not an option with apt-get dist-update - it downloads and installs everything without an option to ignore.
 
Old 05-18-2003, 09:29 AM   #12
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by pf1359
if it's a problem with glibc, you could ignore that package before performing up2date
It is a problem with the rpm package containing glibc, not with glibc itself
 
Old 05-28-2003, 02:38 AM   #13
gill1109
Member
 
Registered: Dec 2002
Location: cyberspace
Distribution: Redhat 9
Posts: 61

Original Poster
Rep: Reputation: 15
I'd like to put on record what was the cause of this bug. It came about through inadvertently trying to upgrade an i686 rpm with an older version of glibc to an i386 rpm with a newer version. It turns out that this is "not done". At some stage the rpm program needs to clean up remnants of the older package, and at that stage the higher architecture takes precedence. The result is a mess.

The solution is spelled out by a contribution from Rob Cermak in the Bugzilla thread referred to above. It worked wonderfully for me.

My initial situation had glibc-2.3.2-11.9.i686.rpm, as part of my RH9 (a smooth update from a clean install of RH8.0 two months previously, everything kept up2date). The rhn applet advised me to update glibc-2.3.2-11.9 to glibc-2.3.2-27.9. I found glibc-2.3.2-27-9 on rhn, there was no choice of architecture and the recommendation was glibc-2.3.2-27-9.i386.rpm. In fact I did not even realise the old version was i686 and anyway I had come to understand that "i386" means "i386 and above" so even if I had noticed, I would not have been concerned.

It seems that rhn has now added an i686 version of the newer glibc so in future this problem is less likely to arise. Anyway, the episode shows what it means to live "on the bleeding edge"! The newest distro, kept completely up to date - living dangerously!
 
Old 05-28-2003, 05:28 AM   #14
unSpawn
Moderator
 
Registered: May 2001
Posts: 27,306
Blog Entries: 54

Rep: Reputation: 2857Reputation: 2857Reputation: 2857Reputation: 2857Reputation: 2857Reputation: 2857Reputation: 2857Reputation: 2857Reputation: 2857Reputation: 2857Reputation: 2857
I'd like to put on record what was the cause of this bug.
Excellent move to finalize your thread by summarizing the problem and posting the solution.
 
Old 08-19-2003, 09:32 AM   #15
VladStar
LQ Newbie
 
Registered: Aug 2003
Posts: 4

Rep: Reputation: 0
Quote:
Originally posted by gill1109
I'd like to put on record what was the cause of this bug. It came about through inadvertently trying to upgrade an i686 rpm with an older version of glibc to an i386 rpm with a newer version. It turns out that this is "not done".
...
Thank you for detailed explanations, they helped a lot ! Here is the solution, that I have applied yesterday and restored my system:

1) insert CD RedHat 9.0 disk 1 into CDROM
2) boot computer from CD
3) type "linux rescue" in the installation prompt
4) answer few questions about language and network settings, then press "Continue" when asked about old system mounting to /mnt/sysimage
5) when you get shell prompt, type "mount" to check if CD is mounted to /mnt/source and old system is mounted to /mnt/sysimage
6) type "rpm -ivh --force --root /mnt/sysimage /mnt/source/RedHat/RPMS/glibc-2.3.2-11.9.i686.rpm /mnt/source/RedHat/RPMS/glibc-common-2.3.2-11.9.i386.rpm" to reinstall original glibc
7) type "chroot /mnt/sysimage" to check if you can get old root instead of usual "Segmentation fault", then simply type "exit" twice to exit from shells and reboot computer. Enjoy.

Thanks to everyone in this thread !

VladStar.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
problem installing glibc-2.3.2-4.80.i686, glibc-common-2.3.2-4.80.8.i386.rpm martianpackets Red Hat 8 05-01-2009 03:22 PM
updating glibc-2.3.2-11.9 to glibc-2.3.4 under rh9 bloodiestmarry Linux - Software 5 02-27-2005 05:43 AM
upgrade glibc-2.2.4 to glibc-2.3.2 on redhat 7.2 Shuja Red Hat 0 07-28-2004 06:10 AM
RPM Upgrade (glibc-common) Linux4BC Linux - General 2 08-04-2003 10:20 PM
rpm upgrade documentation RH8 -> RH9 fails gill1109 Linux - Distributions 1 05-05-2003 01:19 AM


All times are GMT -5. The time now is 01:43 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration