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

[Král Gergely <kral.gergely [at] robolution.eu>]

2015-09-01 10:03 időpontban Král Gergely ezt írta:
> 2015-08-31 20:35 időpontban Arthur de Jong ezt írta:
> > 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).
>
>
> This was also something I suspected but I believe I have the right
> packages installed:
>
> # dpkg -l | egrep -i -v 'openss|insserv' | egrep -i 'ldap|nss'
> ii  dovecot-ldap                         1:2.2.18-1
>     i386         secure POP3/IMAP server - LDAP support
> ii  ldap-utils                           2.4.41+dfsg-1
>     i386         OpenLDAP utilities

...

> Adding "debug" option to pam_ldap.so in /etc/pam.d/common-auth it
> looks that pam_ldap and pam_unix modules are working well.
> But where does the nss_ldap messages are coming from then? Why do cron
> processes need to connect to the ldap server at all?
>
> Sep  1 09:12:01 isa CRON[4008]: nss_ldap: reconnecting to LDAP 
> server...
> Sep  1 09:12:01 isa CRON[4007]: nss_ldap: reconnecting to LDAP 
> server...
> Sep  1 09:12:01 isa CRON[4008]: nss_ldap: reconnected to LDAP server
> ldapi://%2fvar%run%2fslapd%2fldapi after 1 attempt
> Sep  1 09:12:01 isa CRON[4007]: nss_ldap: reconnected to LDAP server
> ldapi://%2fvar%run%2fslapd%2fldapi after 1 attempt
> Sep  1 09:12:01 isa CRON[4008]: pam_unix(cron:session): session opened
> for user root by (uid=0)
> Sep  1 09:12:01 isa CRON[4007]: pam_unix(cron:session): session opened
> for user root by (uid=0)

...

Just to close my issue: due to a need of hard disk expansion the machine 
had to be shut down. After the restart the messages are gone...

It must have been some bug during the replacement of nss_ldap to 
nss_ldapd. I have no idea what process could get stuck though. Anyway, 
problem "solved"...

--
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/