Re: Bug#321561: dlerror: /lib/libresolv.so.2: symbol __res_maybe_init, version GLIBC_PRIVATE

[Russ Allbery <rra@stanford.edu>]

Daniel Jacobowitz <drow@false.org> writes:
> On Sat, Aug 06, 2005 at 03:12:16AM -0400, simon raven wrote:

>> Package: libc6
>> Version: 2.3.2.ds1-22
>> Severity: important
>> 
>> downgraded glibc, since i was getting errors like:
>> 
>> Aug  6 06:35:02 pylon CRON[306]: PAM unable to dlopen(/lib/security/pam_ldap.so)
>> Aug  6 06:35:02 pylon CRON[306]: PAM [dlerror: /lib/libresolv.so.2: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so
>> .6 with link time reference]
>> 
>> and:
>> 
>> Aug  6 06:35:03 pylon CRON[306]: PAM adding faulty module: /lib/security/pam_krb5.so
>> Aug  6 06:35:03 pylon CRON[305]: PAM unable to dlopen(/lib/security/pam_krb5.so)
>> Aug  6 06:35:03 pylon CRON[305]: PAM [dlerror: /lib/libresolv.so.2: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so
>> .6 with link time reference]

> These errors indicate bugs in those libraries (pam_ldap, pam_krb5).

As the co-maintainer of pam_krb5.so, I'd love some more information here.
I certainly do believe you, but nothing about that error message helps me
figure out where the bug is in pam_krb5.so.  It looks completely internal
to the linkage between libresolv.so.2 and libc.so.6.

Is there a standard cause of this bug or a standard thing that pam_krb5.so
should be doing that it's not?  This just showed up with the new glibc
version.  I'm also seeing:

Aug 10 22:53:01 rivendell CRON[30864]: PAM [dlerror: /lib/libpthread.so.0: symbol __libc_stack_end, version GLIBC_2.1 not defined in file ld-linux.so.2 with link time reference]

with another PAM module, similar to another reported bug, but restarting
the software doesn't help.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>