did a emerge -u world yesterday which included these packages: -- sys-devel/autoconf-2.54 sys-apps/texinfo-4.3 sys-devel/gcc-3.2.1 sys-libs/glibc-2.3.1-r2 sys-libs/ncurses-5.3-r1 sys-apps/bash-2.05b-r3 dev-lang/python-2.2.2 sys-apps/portage-2.0.45-r3 sys-devel/binutils-2.13.90.0.16 sys-libs/cracklib-2.7-r6 sys-apps/hdparm-5.3-r1 -- and now I get this in my (sys)log every time someone logs in: -- sshd[31414]: PAM unable to dlopen(/lib/security/pam_cracklib.so) sshd[31414]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /usr/lib/libcrack.so.2)] sshd[31414]: PAM adding faulty module: /lib/security/pam_cracklib.so -- I tried to re-emerge cracklib but that did not help at all. I'm also having problems with ssh not being able to resolve 'localhost', I'm guessing that this is related allthough I don't have the time to investigate that now. (when logged in, resolving seems to work fine), resolve-problem occurs when I do this: `ssh -L110:localhost:110 torgeir@mybox.trenger.ro` It appears to work fine until I connect on local port 110 on my client, then mybox syslog tells me: sshd[20327]: error: connect_to localhost: unknown host (Name or service not known) #
did a emerge -u world yesterday which included these packages: -- sys-devel/autoconf-2.54 sys-apps/texinfo-4.3 sys-devel/gcc-3.2.1 sys-libs/glibc-2.3.1-r2 sys-libs/ncurses-5.3-r1 sys-apps/bash-2.05b-r3 dev-lang/python-2.2.2 sys-apps/portage-2.0.45-r3 sys-devel/binutils-2.13.90.0.16 sys-libs/cracklib-2.7-r6 sys-apps/hdparm-5.3-r1 -- and now I get this in my (sys)log every time someone logs in: -- sshd[31414]: PAM unable to dlopen(/lib/security/pam_cracklib.so) sshd[31414]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /usr/lib/libcrack.so.2)] sshd[31414]: PAM adding faulty module: /lib/security/pam_cracklib.so -- I tried to re-emerge cracklib but that did not help at all. I'm also having problems with ssh not being able to resolve 'localhost', I'm guessing that this is related allthough I don't have the time to investigate that now. (when logged in, resolving seems to work fine), resolve-problem occurs when I do this: `ssh -L110:localhost:110 torgeir@mybox.trenger.ro` It appears to work fine until I connect on local port 110 on my client, then mybox syslog tells me: sshd[20327]: error: connect_to localhost: unknown host (Name or service not known) #¤!"!#!"# !! I tried to re-emerge pam, and this is what I got now: -- sshd[3305]: PAM unable to dlopen(/lib/security/pam_env.so) sshd[3305]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_env.so)] sshd[3305]: PAM adding faulty module: /lib/security/pam_env.so sshd[3305]: PAM unable to dlopen(/lib/security/pam_unix.so) sshd[3305]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_unix.so)] sshd[3305]: PAM adding faulty module: /lib/security/pam_unix.so sshd[3305]: PAM unable to dlopen(/lib/security/pam_cracklib.so) sshd[3305]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_cracklib.so)] sshd[3305]: PAM adding faulty module: /lib/security/pam_cracklib.so sshd[3305]: PAM unable to dlopen(/lib/security/pam_limits.so) sshd[3305]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_limits.so)] sshd[3305]: PAM adding faulty module: /lib/security/pam_limits.so sshd[3305]: PAM rejected by account configuration[28]: Module is unknown -- and did I mention that I cannot log in via ssh anymore? :D And, the actual lib is there: /lib/libc-2.3.1.so /lib/libc.so.6 -> libc-2.3.1.so -- [09:12]root@mybox:/lib> strings libc-2.3.1.so |grep GLIBC_2.3 GLIBC_2.3 GLIBC_2.3.1 -- I'll try to rsync and rm -f /usr/portage/distfiles/* && emerge glibc :(
what does `qpkg -I -v glibc` show ?
# ls -l /lib/libdl* And paste please.
Here's the thing, since this is my dns,web,email,ftp,cvs,shell - whatever server, downtime is bad. really bad. So - I'm currently re-installing. Where I can find the qpkg tool? (emerge -s does not reveal anything) I am interested in helping finding the problem, so I will re-emerge the glibc-2.3.1 after the system install is complete .. and a backup of system binaries and libraries..
Btw, I tried to downgrade from 2.3.1 to 2.2.5 again by marking 2.3.1 as ~x86 and emerge -u glibc (I think it was), but that really did not help, and the result is that even though I got a backup of /lib, it only says libdl-2.2.5.so (11796bytes) and libdl.so.2
While reinstalling I noticed that the system wants to install perl-5.8.. which is marked as ~x86 .. and a `grep -r KEYWORD /etc/make.*` confirmed my thought - the system has not set ~x86 as an accepted keyword (or ARCH..), just x86 there. Apparently I have tried ~x86 at one point, as I had /etc/make.conf~ that had ~x86 enabled. I'm wondering if this is cached somewhere on the system (/var/cache/*/* ?), as with my settings, perl-5.8 should really not have been enabled. If there is a cache-bug then that could possibly be the reason that if fucked up the rest of my system?! (I did not remove /var/cache when I re-installed now)
Okey, the re-install is complete, and this time the glibc-upgrade was sucessfull! :) One big differance between this and my previous glibc-upgrade, was that this upgrade was done from local console, but the first one that went bad was done via a ssh-connection. Hope this won't happen again! :O
Great. I will keep looking into this, as it is critical that upgrades will be without issue ...
All hope is not lost; I have two systems running 1.4; one of which I update manually remote (the one that failed horribly), and one that updates automagically every night (cronjob) - the latter system updated successfully to glibc-2.3! :)
Weird one to be honest. I did a bootstrap and emerge system with the old binutils and glibc-2.2.5, and then afterwards updated binutils and glibc. Went with no problem :/ So I really guess its a problem that only occurs once in a few hundred times ?
Did you do it locally or via ssh? I'm thinking that the library rollover fails when done over ssh (or any other remove mecanism i guess)?
Hrm, nope ... did you try to restart sshd ?
Nope, the thought didn't even cross my mind since I only got errors about the missing GLIBC_2.3, like this one: /bin/sh: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /bin/sh) Unfortunately I haven't got the opportunity, nor the time to test this theory myself in the near future.
Have a look at: http://bugs.gentoo.org/show_bug.cgi?id=12078#c5
haha, I suck! ;( Nice to have an answer, though :)
This should be fixed.
