Re: nslcd: DEBUG: accept() failed (ignored): Resource temporarily unavailable

[Arthur de Jong <arthur [at] arthurdejong.org>]

On Mon, 2015-08-31 at 19:38 +0200, Král Gergely wrote:
> After an upgrade of slapd and a change to the use of nslcd last week
> I receive a lot of messages like these into auth.log:
> 
> Aug 31 17:29:01 isa CRON[1209]: nss_ldap: reconnected to LDAP server 
> ldapi://%2fvar%run%2fslapd%2fldapi after 1 attempt
> Aug 31 17:30:01 isa CRON[1245]: nss_ldap: reconnected to LDAP server 
> ldapi://%2fvar%run%2fslapd%2fldapi after 1 attempt
> Aug 31 17:30:01 isa CRON[1246]: nss_ldap: reconnected to LDAP server 
> ldapi://%2fvar%run%2fslapd%2fldapi after 1 attempt
> Aug 31 17:30:17 isa exim4: nss_ldap: reconnecting to LDAP server...
> Aug 31 17:30:17 isa exim4: nss_ldap: reconnected to LDAP server 
> ldapi://%2fvar%run%2fslapd%2fldapi after 1 attempt
> Aug 31 17:30:46 isa smbd[1288]: nss_ldap: reconnecting to LDAP server...
> Aug 31 17:30:46 isa smbd[1288]: nss_ldap: reconnected to LDAP server 
> ldapi://%2fvar%run%2fslapd%2fldapi after 1 attempt
> Aug 31 17:30:46 isa smbd[1289]: nss_ldap: reconnecting to LDAP server...
> Aug 31 17:30:46 isa smbd[1289]: nss_ldap: reconnected to LDAP server 
> ldapi://%2fvar%run%2fslapd%2fldapi after 1 attempt

These messages seem to be from PADL's nss_ldap module (libnss-ldap
package), not the NSS modules that is shipped as part of nss-pam-ldapd
that talks to nslcd (libnss-ldapd package).

> I am not sure if it is related, but running 'nslcd -d' prints lines 
> as quoted in the subject:

> 
> nslcd: [3dd3e8] DEBUG: connection from pid=29268 uid=0 gid=0
> nslcd: DEBUG: accept() failed (ignored): Resource temporarily unavailable
> nslcd: [3dd3e8]  DEBUG: myldap_search(base="dc=robolution", 
> filter="(&(objectClass=posixAccount)(uid=sarab))")
> nslcd: [3dd3e8]  DEBUG: ldap_result(): uid=sarab,ou=Users,dc=robolution
> nslcd: [3dd3e8]  DEBUG: ldap_result(): end of results (1 total)
> nslcd: [c91298] DEBUG: connection from pid=29268 uid=0 gid=0
> nslcd: DEBUG: accept() failed (ignored): Resource temporarily unavailable
> nslcd: [c91298]  DEBUG: myldap_search(base="dc=robolution", 
> filter="(&(objectClass=posixAccount)(uid=lapisa))")
> nslcd: [c91298]  DEBUG: ldap_result(): uid=lapisa,ou=Users,dc=robolution
> nslcd: [c91298]  DEBUG: ldap_result(): end of results (1 total)
> nslcd: [daf632] DEBUG: connection from pid=29268 uid=0 gid=0
> nslcd: [daf632]  DEBUG: myldap_search(base="dc=robolution", 
> filter="(&(objectClass=posixAccount)(uid=kasop))")
> nslcd: [daf632]  DEBUG: ldap_result(): uid=kasop,ou=Users,dc=robolution
> nslcd: [daf632] "kasop"> DEBUG: ldap_result(): end of results (1 total)
>  
> I am using Debian testing. Could anyone give me a hint where to look 
> for the root of the problem?

The "DEBUG: accept() failed (ignored): Resource temporarily
unavailable" can be safely ignored (occur during normal operation) and
do not seem to be related to the nss_ldap messages above.

-- 
-- 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/