[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: nslcd and Ubuntu 10.04
- To: openldap-technical@openldap.org
- Subject: Re: nslcd and Ubuntu 10.04
- From: Christopher Wood <christopher_wood@pobox.com>
- Date: Wed, 26 Sep 2012 17:11:06 -0400
- Content-disposition: inline
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to:content-transfer-encoding; s=sasl; bh=txFctfEFmuHjW bKC6bDzsUwlT6A=; b=BVpFBr4AX+jcLB1xiAjpfqTyNsP5jmcHhJrgIIZavivZf eOubNFHl4vxB9tfuD7eaw7oor3eLl9TjhJ575dFIaZcPcjN5reWzREdl/Kupa6oh HFrX0jcKCzab7pN0eIczRVwJu1Zlp9mDUw4wE2mgyWpuNEC3eTqSZZpLSxYzEM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to:content-transfer-encoding; q=dns; s=sasl; b=uctbTcP I7yJ7SnEKER8HHA6CWNTffGMyp8ZacNcHu55gb/HkS8hrLnt34lfb756tfq9DomS 8D6Kdv7P0th6mP/cF7JKI4LPEAsqICzBNrh77BepAMAcsWOrMOviYCnRpiJZcbY4 dl9+iXZKLbKDAhoUdJ1qNYGZcDiQI9nAJpeo=
- In-reply-to: <506369A6.1020800@gmail.com>
- References: <20120920074500.GB23707@homeworld.netbsd.org> <alpine.BSO.2.00.1209201034500.1594@morgaine.smi.sendmail.com> <506369A6.1020800@gmail.com>
- User-agent: Mutt/1.5.21 (2010-09-15)
http://ubuntuforums.org/showthread.php?t=1633524
http://lists.arthurdejong.org/nss-pam-ldapd-users/2011/msg00082.html
My fix was to "apt-get source nslcd" on a Debian Squeeze box, then use those files to build a new deb on Ubuntu and shove the result in my repository. Presto, working nslcd on Ubuntu 10.04.
On Wed, Sep 26, 2012 at 04:46:30PM -0400, Adam Wolfe wrote:
> I'm having trouble keeping my servers connected to our openLDAP server.
>
> All through syslog I see messages like this:
>
> Sep 26 14:06:01 hostname nslcd[930]: [2aeb87] connected to LDAP server
> [1]ldaps://ldap.domain.com/
> Sep 26 14:07:01 hostname nslcd[930]: [aae0a3] ldap_result() failed: Can't
> contact LDAP server
> Sep 26 14:07:01 hostname nslcd[930]: [74310e] ldap_result() failed: Can't
> contact LDAP server
> Sep 26 14:07:01 hostname nslcd[930]: [aae0a3] ldap_abandon() failed to
> abandon search: Other (e.g., implementation specific) error
> Sep 26 14:07:01 hostname nslcd[930]: [b2a65f] ldap_result() failed: Can't
> contact LDAP server
> Sep 26 14:07:01 hostname nslcd[930]: [b2a65f] ldap_abandon() failed to
> abandon search: Other (e.g., implementation specific) error
> Sep 26 14:07:01 hostname nslcd[930]: [74310e] ldap_abandon() failed to
> abandon search: Other (e.g., implementation specific) error
> Sep 26 14:07:01 hostname nslcd[930]: [73c9b8] ldap_result() failed: Can't
> contact LDAP server
> Sep 26 14:07:01 hostname nslcd[930]: [73c9b8] ldap_abandon() failed to
> abandon search: Other (e.g., implementation specific) error
> Sep 26 14:07:01 hostname nslcd[930]: [73c9b8] connected to LDAP server
> [2]ldaps://ldap.domain.com/
>
> I'm at the point where I want to start blaming the server, but this is
> happening on all the new servers I am bringing up (Ubuntu 10.04) and not
> on the older servers (8.04).
> Everything seems fine and we can sudo and su with our ldap accounts and
> then out of no where "so-and-so is not in the sudoers file". A simple "id
> user" re-establishes the connection and all is well again for a while.
>
> Has anyone else ran into this and finally, permanently made it work?
>
> References
>
> Visible links
> 1. file:///tmp/ldaps:/ldap.domain.com/
> 2. file:///tmp/ldaps:/ldap