RE: nslcd: error reading from client: Timer expired
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
RE: nslcd: error reading from client: Timer expired
- From: Mark Jas <mark [at] nieuwenborg.nl>
- To: Arthur de Jong <arthur [at] arthurdejong.org>, nss-pam-ldapd-users [at] lists.arthurdejong.org <nss-pam-ldapd-users [at] lists.arthurdejong.org>
- Subject: RE: nslcd: error reading from client: Timer expired
- Date: Wed, 9 Jan 2013 23:36:51 +0100
Hi Arthur,
Thanks for your answers!
I increased the threads to 16 (just tob e sure) and nslcd is now running in
debug mode.
I'm using version 0.7.5-15.el6_3.2. Does anyone know if the fix is backported
tot his version?
--
Met vriendelijke groet,
Mark Jas
Nieuwenborg Solit Solutions
Piuslaan 70a
5614 CM Eindhoven (NL)
Telefoon: 0031-(0)40-2141720
Fax: 0031-(0)40-2141729
www.nieuwenborg.nl
www.solit-solutions.nl
info@nieuwenborg.nl
-----Oorspronkelijk bericht-----
Van: nss-pam-ldapd-users-bounces+mark=nieuwenborg.nl@lists.arthurdejong.org
[nss-pam-ldapd-users-bounces+mark=nieuwenborg.nl [at] lists.arthurdejong.org]
Namens Arthur de Jong
Verzonden: woensdag 9 januari 2013 23:05
Aan: nss-pam-ldapd-users@lists.arthurdejong.org
Onderwerp: Re: nslcd: error reading from client: Timer expired
On Wed, 2013-01-09 at 16:26 +0100, Mark Jas wrote:
> 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
This is a notification that communication between nslcd and the NSS module
timed out.
> And does anybody know how to debug the issue?
Which version of nss-pam-ldapd are you using? Versions 0.7.18 and 0.8.11
contain a fix for when a large number of file descriptors are open.
Running nslcd in debugging mode ensures that it produces a lot more debugging
information that could be useful to pinpoint the issue.
Amongst other things it logs the pid that made the request and the kind of
request.
If the problem turns out that nslcd is being held up while trying to return
large query results back to the application while the application is not
reading information quickly enough, increasing the number of threads nslcd uses
could be an option.
--
-- 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/
--
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/