On Wed, 2008-03-19 at 15:47 +0100, Bas van der Vlies wrote: > We have installed nslcd on out 800 node cluster and once in a while we > get these message from some nodes: > > Mar 19 15:17:47 gb-r3n8 nslcd[3236]: failed to bind to LDAP server > ldaps://ldap.cua.sara.nl: Can't contact LDAP server: Operation now in > progress
The problem is most likely that calling connect() to the LDAP server failed with the error EINPROGRESS (Operation now in progress). Probably because the number of connection to the server is too large. If you have a large cluster, having too many connections to the LDAP server may be a problem. If that is the case this problem may be mitigated by using the threads keyword introduced in release 0.6.2 (setting it to something lower than the default 5). The error itself is a bit weird because this should only happen when the socket is in non-blocking mode. Since OpenLDAP has control over the socket I suspect this may be a bug in OpenLDAP. You also appear to be using OpenLDAP from stable which is much older than the current version in unstable/testing. > Versions of packages libnss-ldapd depends on: > ii grap 1.39-2 program for typesetting graphs Btw, I'm a bit puzzled how this dependency ended up in libnss-ldapd. -- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
