After upgrading nss-pam-ldapd from 0.8.10 to 0.8.11 nslcd can't connect to the LDAP-Server anymore. I get the same error messages like in this thread of the upstream-mailing-list: http://lists.arthurdejong.org/nss-pam-ldapd-users/2012/msg00198.html There is also a proposal for a patch witch I add to this bug. Please include this into the ebuild of Version 0.8.11 Reproducible: Always Steps to Reproduce: 1.upgrade from 0.8.10 to 0.8.11 or 0.8.11-r1 2.start nslcd Actual Results: "ldap_set_option(LDAP_OPT_X_SASL_NOCANO N) failed: Can't contact LDAP server" Expected Results: no error messages and successful connection to LDAP-Server
Created attachment 329516 [details, diff] proposed patch for nss-pam-ldapd-0.8.11
Can you test with the sasl use flag enabled?
I just testet it. I was surprised that with the sasl use flag "xemacs" was pulled in. But it still does not work: Nov 14 19:05:54 localhost nslcd[8394]: caught signal SIGTERM (15), shutting down Nov 14 19:05:54 localhost nslcd[8394]: version 0.8.10 bailing out Nov 14 19:05:54 localhost nslcd[2933]: version 0.8.11 starting Nov 14 19:05:59 localhost nslcd[2933]: accepting connections Nov 14 19:05:59 localhost nslcd[2933]: [8b4567] <group/member="nslcd"> ldap_set_option(LDAP_OPT_X_SASL_NOCANON) failed: Can't contact LDAP server N
I'm asking if he's going to release a new version soonish, if no response in the next day I will patch 0.8.11 in -r2 also, for refrence http://arthurdejong.org/viewvc/nss-pam-ldapd?revision=1824&view=revision
Yeah, I could live with that (waiting for a new upstream-version)...
I expect the new release to come out in the next couple of days. (this came from upstream) that good for you then?
perfect.
fixed in nss-pam-ldapd-0.8.12
Yeah it works! Thanks!