| View previous topic :: View next topic |
| Author |
Message |
Gigantopithicus
n00b
Joined: 05 Aug 2002
Posts: 17
Location: Chicago, IL
|
 Posted: Tue Dec 24, 2002 8:16 pm Post subject: PAM SNAFU: dlerror |
 |
|
I'm using gentoo 1.4_rc1. Last evening... I did an 'emerge world' in a hurry...
This morning, I try to open a new ssh connection, cannot login and get this in the /var/log/auth.log:
| Code: |
Dec 24 13:45:57 chipper sshd[18180]: PAM unable to dlopen(/lib/security/pam_env.so)
Dec 24 13:45:57 chipper sshd[18180]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_env.so)]
Dec 24 13:45:57 chipper sshd[18180]: PAM adding faulty module: /lib/security/pam_env.so
Dec 24 13:45:57 chipper sshd[18180]: PAM unable to dlopen(/lib/security/pam_unix.so)
Dec 24 13:45:57 chipper sshd[18180]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_unix.so)]
Dec 24 13:45:57 chipper sshd[18180]: PAM adding faulty module: /lib/security/pam_unix.so
Dec 24 13:45:57 chipper sshd[18180]: PAM unable to dlopen(/lib/security/pam_cracklib.so)
Dec 24 13:45:57 chipper sshd[18180]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_cracklib.so)]
Dec 24 13:45:57 chipper sshd[18180]: PAM adding faulty module: /lib/security/pam_cracklib.so
Dec 24 13:45:57 chipper sshd[18180]: PAM unable to dlopen(/lib/security/pam_limits.so)
Dec 24 13:45:57 chipper sshd[18180]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_limits.so)]
Dec 24 13:45:57 chipper sshd[18180]: PAM adding faulty module: /lib/security/pam_limits.so
Dec 24 13:45:57 chipper sshd[18180]: Failed password for garth from 192.168.1.10 port 1718 ssh2
|
I then did 'emerge pam' to remerge it, but still has same error. What could be the problem? Any suggestions on how to fix this? The same errors come up when trying to login courier-imapd-ssl.
Thanks in advance. |
|
| Back to top |
|
 |
hast
n00b
Joined: 29 Sep 2002
Posts: 9
|
| Posted: Thu Dec 26, 2002 11:10 am Post subject: |
|
|
| have you restarted sshd? |
|
| Back to top |
|
|
Gigantopithicus
n00b
Joined: 05 Aug 2002
Posts: 17
Location: Chicago, IL
|
| Posted: Fri Dec 27, 2002 4:01 pm Post subject: |
|
|
Hast:
Thanks for responding. Yes, I restarted sshd. Same with courier-imap. I think upgrading glibc messed it all up. I'll be more astute next time.
For the time being, I tore down the box and started from stage 1 install. Working well now. |
|
| Back to top |
|
|
shamgar
n00b
Joined: 23 Sep 2002
Posts: 14
Location: Texas
|
| Posted: Tue Feb 11, 2003 4:46 pm Post subject: Re: PAM SNAFU: dlerror |
|
|
| Gigantopithicus wrote: |
| Code: |
Dec 24 13:45:57 chipper sshd[18180]: PAM unable to dlopen(/lib/security/pam_env.so)
Dec 24 13:45:57 chipper sshd[18180]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_env.so)]
Dec 24 13:45:57 chipper sshd[18180]: PAM adding faulty module: /lib/security/pam_env.so
Dec 24 13:45:57 chipper sshd[18180]: PAM unable to dlopen(/lib/security/pam_unix.so)
Dec 24 13:45:57 chipper sshd[18180]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_unix.so)]
Dec 24 13:45:57 chipper sshd[18180]: PAM adding faulty module: /lib/security/pam_unix.so
Dec 24 13:45:57 chipper sshd[18180]: PAM unable to dlopen(/lib/security/pam_cracklib.so)
Dec 24 13:45:57 chipper sshd[18180]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_cracklib.so)]
Dec 24 13:45:57 chipper sshd[18180]: PAM adding faulty module: /lib/security/pam_cracklib.so
Dec 24 13:45:57 chipper sshd[18180]: PAM unable to dlopen(/lib/security/pam_limits.so)
Dec 24 13:45:57 chipper sshd[18180]: PAM [dlerror: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/security/pam_limits.so)]
Dec 24 13:45:57 chipper sshd[18180]: PAM adding faulty module: /lib/security/pam_limits.so
Dec 24 13:45:57 chipper sshd[18180]: Failed password for garth from 192.168.1.10 port 1718 ssh2
|
I then did 'emerge pam' to remerge it, but still has same error. What could be the problem? Any suggestions on how to fix this? The same errors come up when trying to login courier-imapd-ssl.
Thanks in advance. |
I had the same problem. I read in another post that rebooting would fix it, but didn't really want to do that. I tried rebuilding pam and ssh to no avail. On a hunch, from an earlier post indicating a similar problem with imap ssl, I tried rebuilding openssl as well and then restarted ssh and it worked. |
|
| Back to top |
|
|
|
Networking & Security
