View previous topic :: View next topic |
Author |
Message |
vdracula n00b
Joined: 03 Aug 2004 Posts: 51 Location: NGC 5907
|
Posted: Sun Feb 06, 2011 11:11 am Post subject: WARNING: prelink and glibc-2.13 update |
|
|
Hello!
Just wanted to warn all those who are just updated to glibc-2.13 and using prelink.
I got everywhere a segfault...
more here:
https://bbs.archlinux.org/viewtopic.php?pid=885429 |
|
Back to top |
|
|
seqizz Tux's lil' helper
Joined: 14 Jan 2008 Posts: 103
|
Posted: Sun Feb 06, 2011 1:02 pm Post subject: Omg |
|
|
Thank you very much to give this info. I was f*** up. I didn't see something like this before. I can't even chroot to fix "whatever it is". |
|
Back to top |
|
|
Yuu Apprentice
Joined: 23 Dec 2008 Posts: 223 Location: France
|
Posted: Sun Feb 06, 2011 1:12 pm Post subject: |
|
|
Hi,
thank you for the information. Hopefully, I'm still in amd64 stable branch, but I hope that'll be fixed soon, because I like prelink :]
Also, I noticed that there's an opened bug here.
@seqizz : maybe you should see that opened bug, there's instructions to undo prelinking from the liveCD. _________________ Main laptop : T8300 cpu | 200 GB hard drive | 2 GB of ram | 8600M GT | Gentoo x86_64
Server : Celeron 220 cpu | 250 GB hard drive | 2 GB of ram | SiS 662 VGA | Gentoo x86_64 |
|
Back to top |
|
|
seqizz Tux's lil' helper
Joined: 14 Jan 2008 Posts: 103
|
Posted: Sun Feb 06, 2011 1:39 pm Post subject: |
|
|
Thanks @Yuu,
Even if i had to force my one friend to compile a binary prelink package with -march=atom cflags. After a successful prelink -ua, i guess everything is ok. |
|
Back to top |
|
|
Odysseus Apprentice
Joined: 23 Jun 2004 Posts: 250 Location: Miami, FL. I miss San Francisco!!!
|
Posted: Sun Feb 06, 2011 1:59 pm Post subject: WARNING: updating to glibc-2.13 w/prelink hoses system |
|
|
If you're running a ~ arch, DO NOT update to glibc-2.13 if you have prelink installed!!! It will completely hose your box!!! I just spent several hours trying to recover from this bug https://bugs.gentoo.org/show_bug.cgi?id=353814
If you want the new glibc, you must first uninstall prelink or if you want to keep prelink, you need to mask the new glibc until one or the other is fixed.
When I updated yesterday morning glibc was in the queue. It installed without issues. I then 'emerge -eavND @system' to rebuild against it. Halfway through the emerge, portage crashed, bash segfaulted and my KDE DE ceased functioning. I tried to ssh into my box, but it was impossible because all of my network connections ceased functioning. The only way to get out of X was a hard reboot, but then all three of my kernels panicked just after leaving the grub splash.
I was finally able to regain control of my machine by booting into a rescue disc and following the instructions posted in comment #3 in the bug report I linked to. I had to chroot into my box to uninstall prelink, before I was able to regain control and reboot back into my system.
Please be aware that this is a serious issue.
You have been forewarned!
Ciao
Edit: apparently this isn't the only distro to be affected by this bug. Arch Linux is as well, as evidenced by these posts: https://bbs.archlinux.org/viewtopic.php?id=112510 and https://bbs.archlinux.org/viewtopic.php?pid=884397#p884397 |
|
Back to top |
|
|
hielvc Advocate
Joined: 19 Apr 2002 Posts: 2805 Location: Oceanside, Ca
|
|
Back to top |
|
|
FireBurn Apprentice
Joined: 19 Sep 2004 Posts: 170 Location: Edinburgh, UK
|
Posted: Mon Feb 07, 2011 6:24 am Post subject: |
|
|
I tried to get the committer of the new glibc to mask the package immediately before I figured out it was caused by the interaction with prelink
It's more than a day on and still nothing has been done to stop people from hosing their systems
All it would take is a !sys-devel/prelink in the DEPEND of the new glibc or a !sys-lib/glibc-2.13 in the prelink builds
It's not rocket science - I wonder how many folks have hosed their system because of this? |
|
Back to top |
|
|
furanku l33t
Joined: 08 May 2003 Posts: 905 Location: Hamburg, Germany
|
Posted: Mon Feb 07, 2011 7:29 am Post subject: |
|
|
Wow --- that was scary!
Thanks you so much for giving the link to the workaround so quickly. |
|
Back to top |
|
|
SoLoR n00b
Joined: 22 Sep 2004 Posts: 26
|
Posted: Mon Feb 07, 2011 8:16 am Post subject: |
|
|
glibc-2.13 also breaks postfix for me...
Feb 7 08:02:18 mih postfix/master[11799]: daemon started -- version 2.8.0, configuration /etc/postfix
Feb 7 08:02:18 mih postfix/qmgr[11803]: A82474006E: from=<root@xxxx.xxx.xxx>, size=14500, nrcpt=1 (queue active)
Feb 7 08:02:18 mih postfix/local[11805]: fatal: unable to determine open file limit
Feb 7 08:02:19 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 11805 exit status 1
Feb 7 08:02:19 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:03:19 mih postfix/local[11826]: fatal: unable to determine open file limit
Feb 7 08:03:20 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 11826 exit status 1
Feb 7 08:03:20 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:04:20 mih postfix/local[11841]: fatal: unable to determine open file limit
Feb 7 08:04:21 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 11841 exit status 1
Feb 7 08:04:21 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:05:21 mih postfix/local[11861]: fatal: unable to determine open file limit
Feb 7 08:05:22 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 11861 exit status 1
Feb 7 08:05:22 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:06:22 mih postfix/local[11868]: fatal: unable to determine open file limit
Feb 7 08:06:23 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 11868 exit status 1
Feb 7 08:06:23 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:07:23 mih postfix/local[12215]: fatal: unable to determine open file limit
Feb 7 08:07:24 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 12215 exit status 1
Feb 7 08:07:24 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:08:24 mih postfix/local[21471]: fatal: unable to determine open file limit
Feb 7 08:08:25 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 21471 exit status 1
Feb 7 08:08:25 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:09:25 mih postfix/local[22152]: fatal: unable to determine open file limit
Feb 7 08:09:26 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 22152 exit status 1
Feb 7 08:09:26 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:10:26 mih postfix/local[23152]: fatal: unable to determine open file limit
Feb 7 08:10:27 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 23152 exit status 1
Feb 7 08:10:27 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:11:27 mih postfix/local[23861]: fatal: unable to determine open file limit
Feb 7 08:11:28 mih postfix/master[11799]: warning: process /usr/lib/postfix/local pid 23861 exit status 1
Feb 7 08:11:28 mih postfix/master[11799]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Feb 7 08:11:55 mih postfix/postfix-script[24050]: stopping the Postfix mail system
Feb 7 08:11:55 mih postfix/master[11799]: terminating on signal 15
reverting glibc back to 2.12.2 and problem is gone. |
|
Back to top |
|
|
Etrans n00b
Joined: 19 Nov 2006 Posts: 8 Location: Russia
|
Posted: Mon Feb 07, 2011 9:33 am Post subject: |
|
|
Read this post too late..now I have a kernel panic with some mentioning of ld.so-2.13 |
|
Back to top |
|
|
FireBurn Apprentice
Joined: 19 Sep 2004 Posts: 170 Location: Edinburgh, UK
|
Posted: Mon Feb 07, 2011 10:15 am Post subject: |
|
|
Etrans wrote: | Read this post too late..now I have a kernel panic with some mentioning of ld.so-2.13 |
Don't panic (unlike your kernel)
1) Boot from CD
2) mount your root partition to /mnt/gentoo
3) run: /mnt/gentoo/usr/sbin/prelink -u /mnt/gentoo/bin/bash
4) chroot into your install: chroot /mnt/gentoo /bin/bash
5) Switch of prelink: prelink -au
6) Unmerge prelink: emerge --unmerge prelink
Alternatively instead of 6) you could downgrade glibc and mask 2.13 |
|
Back to top |
|
|
grozin n00b
Joined: 14 Mar 2005 Posts: 72 Location: Novosibirsk, Russia
|
Posted: Mon Feb 07, 2011 10:48 am Post subject: |
|
|
I run a pure ~x86 box. After upgrade to glibc-2.13, skype segfaults immediately at start-up. Please help! My wife is worried!
Is it possible to downgrade glibc in any way? Higher computer-related things can wait, I urgently need skype. _________________ Andrey Grozin |
|
Back to top |
|
|
SoLoR n00b
Joined: 22 Sep 2004 Posts: 26
|
Posted: Mon Feb 07, 2011 10:57 am Post subject: |
|
|
grozin wrote: | I run a pure ~x86 box. After upgrade to glibc-2.13, skype segfaults immediately at start-up. Please help! My wife is worried!
Is it possible to downgrade glibc in any way? Higher computer-related things can wait, I urgently need skype. |
there is: here
im trying to recompile whole system with new glibc to see if it fixed my postfix issue, but it will take a while... |
|
Back to top |
|
|
vdracula n00b
Joined: 03 Aug 2004 Posts: 51 Location: NGC 5907
|
Posted: Mon Feb 07, 2011 11:04 am Post subject: |
|
|
Even for testing it's a very bad QA, in particular for glibc. |
|
Back to top |
|
|
FireBurn Apprentice
Joined: 19 Sep 2004 Posts: 170 Location: Edinburgh, UK
|
Posted: Mon Feb 07, 2011 11:12 am Post subject: |
|
|
vdracula wrote: | Even for testing it's a very bad QA, in particular for glibc. |
The ebuild was marked ~unstable for x86 amd64 ppc ppc64 spark ia64 sh & s390
I very much doubt if all these targets were tested especially the latter; I doubt very many people have access to a mainframe to do testing |
|
Back to top |
|
|
tnt Veteran
Joined: 27 Feb 2004 Posts: 1221
|
Posted: Mon Feb 07, 2011 11:21 am Post subject: |
|
|
FireBurn wrote: | Etrans wrote: | Read this post too late..now I have a kernel panic with some mentioning of ld.so-2.13 |
Don't panic (unlike your kernel)
1) Boot from CD
2) mount your root partition to /mnt/gentoo
3) run: /mnt/gentoo/usr/sbin/prelink -u /mnt/gentoo/bin/bash
4) chroot into your install: chroot /mnt/gentoo /bin/bash
5) Switch of prelink: prelink -au
6) Unmerge prelink: emerge --unmerge prelink
Alternatively instead of 6) you could downgrade glibc and mask 2.13 |
thx _________________ gentoo user |
|
Back to top |
|
|
vdracula n00b
Joined: 03 Aug 2004 Posts: 51 Location: NGC 5907
|
Posted: Mon Feb 07, 2011 11:27 am Post subject: |
|
|
FireBurn wrote: | vdracula wrote: | Even for testing it's a very bad QA, in particular for glibc. |
The ebuild was marked ~unstable for x86 amd64 ppc ppc64 spark ia64 sh & s390
I very much doubt if all these targets were tested especially the latter; I doubt very many people have access to a mainframe to do testing |
That's true, but at least for the very popular archs it could be tested. For instance, x86, amd64 (and if, ppc/ppc64). |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
Posted: Mon Feb 07, 2011 3:04 pm Post subject: |
|
|
Yes, three of my boxes were running overnight and were screwed. There is no need to unmerge prelink, though, just make sure you have
in your /etc/conf.d/prelink.
I assume most of us want to keep prelink despite this little @#$%. _________________ My Gentoo installation notes.
Please learn how to denote units correctly! |
|
Back to top |
|
|
tomk Bodhisattva
Joined: 23 Sep 2003 Posts: 7221 Location: Sat in front of my computer
|
|
Back to top |
|
|
Simon196405 n00b
Joined: 22 Sep 2003 Posts: 42 Location: Utrecht, Holland
|
Posted: Mon Feb 07, 2011 8:08 pm Post subject: |
|
|
I just wonder if prelink is still usefull.
Nowedays we some linker optimizations like: --as-needed, hash-style=gnu, O1.
Also there was something like a useflag kdeenablefinal.
These basically make sure there is less to link and that linking goes faster.
So the befit of prelink is smaller these days.
I just wonder if prelink is still worthwhile? |
|
Back to top |
|
|
SamuliSuominen Retired Dev
Joined: 30 Sep 2005 Posts: 2133 Location: Finland
|
Posted: Mon Feb 07, 2011 8:20 pm Post subject: |
|
|
Simon196405 wrote: | I just wonder if prelink is still usefull.
Nowedays we some linker optimizations like: --as-needed, hash-style=gnu, O1.
Also there was something like a useflag kdeenablefinal.
These basically make sure there is less to link and that linking goes faster.
So the befit of prelink is smaller these days.
I just wonder if prelink is still worthwhile? |
No. It's not worth it on modern systems.
http://lwn.net/Articles/341244/ |
|
Back to top |
|
|
js08 n00b
Joined: 04 Mar 2008 Posts: 46
|
Posted: Mon Feb 07, 2011 8:24 pm Post subject: |
|
|
Jaglover wrote: | Yes, three of my boxes were running overnight and were screwed. There is no need to unmerge prelink, though, just make sure you have
in your /etc/conf.d/prelink.
I assume most of us want to keep prelink despite this little @#$%. |
thanx this helped. _________________ Train Hard Or Don't Train At All |
|
Back to top |
|
|
rhill Retired Dev
Joined: 22 Oct 2004 Posts: 1629 Location: sk.ca
|
Posted: Mon Feb 07, 2011 10:13 pm Post subject: |
|
|
vdracula wrote: | Even for testing it's a very bad QA, in particular for glibc. |
Yes it sucks, but prelink is run by a cron job. Until prelink is run, everything appears to work. No amount of testing would catch it unless the cron job happened to trigger. _________________ by design, by neglect
for a fact or just for effect |
|
Back to top |
|
|
robinmarlow Apprentice
Joined: 10 Mar 2004 Posts: 167
|
Posted: Tue Feb 08, 2011 12:04 am Post subject: |
|
|
Cripes! That was scary.
Thanks for the solution. I'd have never figured this one out.
Robin |
|
Back to top |
|
|
NightMonkey Guru
Joined: 21 Mar 2003 Posts: 356 Location: Philadelphia, PA
|
Posted: Tue Feb 08, 2011 12:19 am Post subject: |
|
|
Welcome to unstable, everyone. _________________
|
|
Back to top |
|
|
|