Arthur de Jong wrote:
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).
I have made a calculation and and have increased the open files to
8192 and we have 2 server for this cluster. So 5 * 800 = 4000 is only
2000 connections per server. Must be enough
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.
Again thanks for the explanation. This error mostly occurs we i restart the
slapd servers. Then i client tries forever to connect to a slapd-server. We
have Round Robin DNS setup. The only way to stop this is to restart the
nslcd daemon.
Do you mean the client libraries or the slapd version?
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.
When i compiled it on our debian system it was needed for the man page.
--
--
********************************************************************
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Services phone: +31 20 592 8012 *
* Kruislaan 415 fax: +31 20 6683167 *
* 1098 SJ Amsterdam *
* *
********************************************************************
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
