Bug#647978: nslcd slows down everything when I unplug my notebook from network

November 07th, 2011 - 09:20 pm ET by Jiri Kanicky | Report spam
Package: nslcd
Version: 0.8.4
Severity: important

Dear Maintainer,

When I unplug notebook from my network, nslcd is not able to contact LDAP
server and some task like "clicking on logout" takes long time and the
following errors are reported.
I believe that the nslcd is waiting for responce, and than the task can
proceed, but it should not work like that. In Windows, I also do not wait for
tasks when I work offline.

ov 8 12:46:24 knightrider nslcd[2146]: [bb2b99] <passwd001> no available
LDAP server found: Can't contact LDAP server
Nov 8 12:46:24 knightrider nslcd[2146]: [e3dfe6] <passwd001> no available
LDAP server found: Server is unavailable
Nov 8 12:46:24 knightrider nslcd[2146]: [5b37f3] <passwd001> no available
LDAP server found: Server is unavailable
Nov 8 12:46:24 knightrider nslcd[2146]: [db7e02] <passwd001> no available
LDAP server found: Server is unavailable
Nov 8 12:46:24 knightrider nslcd[2146]: [7ec0c4] <passwd001> no available
LDAP server found: Server is unavailable
Nov 8 12:46:24 knightrider nslcd[2146]: [73bb22] <passwd001> no available
LDAP server found: Server is unavailable
Nov 8 12:46:24 knightrider nslcd[2146]: [9e1dd3] <passwd001> no available
LDAP server found: Server is unavailable
Nov 8 12:46:24 knightrider nslcd[2146]: [d141cc] <passwd001> no available
LDAP server found: Server is unavailable
Nov 8 12:46:46 knightrider nslcd[2146]: [f9357a] <passwd=-1> failed to bind to
LDAP server ldap://maverick.allsupp.corp: Can't contact LDAP server: Connection
timed out



Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nslcd depends on:
ii adduser 3.113
ii debconf [debconf-2.0] 1.5.41
ii libc6 2.13-21
ii libgssapi-krb5-2 1.9.1+dfsg-3
ii libldap-2.4-2 2.4.25-4

Versions of packages nslcd recommends:
ii bind9-host [host] 1:9.7.3.dfsg-1+b1
ii host 1:9.8.1.dfsg-1
ii ldap-utils 2.4.25-4
ii libnss-ldapd [libnss-ldap] 0.8.4
ii libpam-krb5 4.4-3
ii libpam-ldapd [libpam-ldap] 0.8.4
ii nscd 2.13-21

Versions of packages nslcd suggests:
pn kstart <none>

nslcd/ldap-sasl-realm:
nslcd/ldap-starttls: false
nslcd/ldap-sasl-krb5-ccname: /var/run/nslcd/nslcd.tkt
nslcd/ldap-auth-type: none
nslcd/ldap-reqcert:
* nslcd/ldap-uris: ldap://maverick.allsupp.corp
nslcd/ldap-sasl-secprops:
nslcd/ldap-binddn:
nslcd/ldap-sasl-authcid:
nslcd/ldap-sasl-mech:
* nslcd/ldap-base: dc=allsupp,dc=corp
nslcd/ldap-sasl-authzid:



To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 5 repliesReplies Make a reply

Replies

#1 Arthur de Jong
November 08th, 2011 - 05:10 pm ET | Report spam

On Tue, 2011-11-08 at 13:06 +1100, Jiri Kanicky wrote:
When I unplug notebook from my network, nslcd is not able to contact LDAP
server and some task like "clicking on logout" takes long time and the
following errors are reported.
I believe that the nslcd is waiting for responce, and than the task can
proceed, but it should not work like that. In Windows, I also do not wait for
tasks when I work offline.



If you want to support off-line operation you either have to have a
local replica of the LDAP server of perform some caching with nscd (or
something else). Currently nss-pam-ldapd does not implement caching.

If the connection to your LDAP server is normally reliable, you could
tune the timing settings to something like this:

bind_timelimit 3
timelimit 3
reconnect_sleeptime 1
reconnect_retrytime 3

This ensures that unavailability of the LDAP server is recorded quickly.

Nov 8 12:46:24 knightrider nslcd[2146]: [e3dfe6] <passwd=10001> no available
LDAP server found: Server is unavailable



It is a bit strange that this query is retried so often because I would
expect nscd to have cached the result.

Thanks,








To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics