1 |
On Sat, Nov 26, 2011 at 6:25 PM, Adam Carter <adamcarter3@×××××.com> wrote: |
2 |
>>>> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by |
3 |
>>>> >> /lib64/libcrypt.so.1) |
4 |
>>>> >> |
5 |
>>>> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I |
6 |
>>>> >> rebuilt pam and things seem to be working again. Are there any other |
7 |
>>>> >> packages I should rebuild before encountering a problem? Or some way |
8 |
>>>> >> to detect which need to be rebuilt? Should I re-emerge world against |
9 |
>>>> >> my new glibc? :) |
10 |
> |
11 |
> How did you know to rebuild pam? |
12 |
> |
13 |
> Both /lib64/libc.so.6 and /lib64/libcrypt.so.1 are from glibc, and I |
14 |
> interpret your error as 'libcrypt.so.1 couldn't find a GLIBC_2.14 |
15 |
> version of /lib64/libc.so.6', which doesn't make any sense to me as |
16 |
> both files are from the same package. How could the version dependency |
17 |
> between them be incorrect? |
18 |
|
19 |
Sorry, I accidentally pasted the incomplete error message. It was part |
20 |
of this kind of message in my syslog: |
21 |
|
22 |
Nov 25 19:40:01 [cron] PAM unable to |
23 |
dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version |
24 |
`GLIBC_2.14' not found (required by /lib64/security/pam_unix.so) |
25 |
Nov 25 19:40:01 [cron] PAM adding faulty module: /lib64/security/pam_unix.so |
26 |
|
27 |
and xdm wouldn't restart after i upgraded glibc, until I rebuilt PAM. |
28 |
Or maybe it was coincidental... |