nslcd: error reading from client: Timer expired
[Date Prev][Date Next] [Thread Prev][Thread Next]nslcd: error reading from client: Timer expired
- From: Mark Jas <mark [at] nieuwenborg.nl>
- To: nss-pam-ldapd-users [at] lists.arthurdejong.org <nss-pam-ldapd-users [at] lists.arthurdejong.org>
- Subject: nslcd: error reading from client: Timer expired
- Date: Wed, 9 Jan 2013 16:26:59 +0100
Hi all, I’m having touble when my users have lots of files opened on a samba file server. (Serveral thousand files from 1 client (terminal server)) Samba complains that it cannot lookup uid’s, file locks are lost and my log files show lots of error messages like: nslcd[1477]: [d22003] error reading from client: Timer expired My first thought was that ldapd is not responding, but the ldap debug log shows nothing strange. Can someone tell me what the error means? Is the timeout really in the connection between ldap and nslcd? And does anybody know how to debug the issue? Regards, Mark |
-- To unsubscribe send an email to nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see http://lists.arthurdejong.org/nss-pam-ldapd-users/
- nslcd: error reading from client: Timer expired, Mark Jas
- Re: nslcd: error reading from client: Timer expired, Arthur de Jong
- Message not available
- RE: nslcd: error reading from client: Timer expired,
Mark Jas
- Re: nslcd: error reading from client: Timer expired,
Jakub Hrozek
- Re: nslcd: error reading from client: Timer expired, Arthur de Jong
- Re: nslcd: error reading from client: Timer expired,
Jakub Hrozek
- RE: nslcd: error reading from client: Timer expired,
Mark Jas
- Prev by Date: Re: RPM packaging for version 0.8.12
- Next by Date: Re: nslcd: error reading from client: Timer expired
- Previous by thread: Re: RPM packaging for version 0.8.12
- Next by thread: Re: nslcd: error reading from client: Timer expired