Package: nscd Version: 2.10.1-1 Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The recent upgrade of nscd from 2.9-27 to 2.10.1-1 resulted in my LDAP server no longer being reachable: Oct 19 14:43:17 debian getent: nss_ldap: could not connect to any LDAP server as (null) - Can't contact LDAP server Oct 19 14:43:17 debian getent: nss_ldap: failed to bind to LDAP server ldaps://ldap.local: Can't contact LDAP server Oct 19 14:43:17 debian getent: nss_ldap: reconnecting to LDAP server... Oct 19 14:43:17 debian getent: nss_ldap: could not connect to any LDAP server as (null) - Can't contact LDAP server Oct 19 14:43:17 debian getent: nss_ldap: failed to bind to LDAP server ldaps://ldap.local: Can't contact LDAP server Oct 19 14:43:17 debian getent: nss_ldap: reconnecting to LDAP server (sleeping 1 seconds)... It first manifested itself with the classic "I have no name" prompt. Turning on debugging on the LDAP server (running Lenny) resulted in no useful information. The only thing that fixed the problem was reverting to 2.9-27. I am hesitant to make this bug RC, since I do not know how widespread the problem is. If it makes a difference, the sid installation being affected by this is an amd64 Sid chroot on an amd64 Lenny system that I use for development. Regards, - -Roberto -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkrcftsACgkQ5SXWIKfIlGQxpgCfQncqC/CGHxFX3wP8z2S2PFIr yNkAoIdlHenAz2HQ4Tbx32u6t8G27KDQ =Duu4 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
