Re: failed to bind to LDAP server: Can't contact LDAP server: No such process
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
Re: failed to bind to LDAP server: Can't contact LDAP server: No such process
- From: Arthur de Jong <arthur [at] arthurdejong.org>
- To: nss-pam-ldapd-users [at] lists.arthurdejong.org
- Subject: Re: failed to bind to LDAP server: Can't contact LDAP server: No such process
- Date: Tue, 17 Jan 2012 20:56:53 +0100
On Tue, 2012-01-17 at 12:31 +0100, Volkel, Stefan (EXT-Other - DE/Ulm)
wrote:
> this is on Fedora 13, with nslcd 0.7.13.
>
> After rebooting one Machine, didn't work:
>
> Jan 16 18:58:30 foo nslcd[1594]: [8b4567] failed to bind to LDAP server
> ldaps://ldap1: Can't contact LDAP server: No such process
> Jan 16 18:58:30 foo nslcd[1594]: [8b4567] failed to bind to LDAP server
> ldaps://ldap2: Can't contact LDAP server: No such process
> Jan 16 18:58:30 foo nslcd[1594]: [8b4567] failed to bind to LDAP server
> ldaps://ldap3: Can't contact LDAP server: No such process
> Jan 16 18:58:30 foo nslcd[1594]: [8b4567] no available LDAP server found,
> sleeping 1 seconds
>
> I think what happened was, did not receive an IP from our DHCP server
> and thus DNS was not working.
>
> Later it did in fact get an IP address, but nslcd still failed to
> contact the LDAP servers. Restarting nslcd fixed this.
>
> Does nslcd cache DNS lookups?
nslcd does not cache DNS lookups, except if you use the DNS value for
the uri option. The hostname lookups are done by the OpenLDAP library
and libc, completely outside the scope of nslcd. If could be that the
information is cached there somehow.
In general, it is recommended to use an IP address to specify the LDAP
server if possible to avoid these kind of issues. The "No such process"
error is a bit weird though.
--
-- arthur - arthur@arthurdejong.org - http://arthurdejong.org --
--
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/