connection limits: how to overcome?
807573Feb 6 2007 — edited Feb 8 2007Dearest DS guru!
I'm afraid this question is quite often here. And I've seen some instances, but I failed to find any usefull information.
I have SunDS 5.2 running on RHEL 3.
One day I've experienced the problem of open FD limit (the message in the error log file:
ERROR<12293> - Connection - conn=-1 op=-1 msgId=-1 - fd limit exceeded Too many open file descriptors - not listening on new connection)
So as it is advised in the tuning manual I've changed the OS limits (at this time I have ulimit -n 65535 in both /etc/profile and in the script which starts up the DS) and I've also changed the nsslapd-maxdescriptors in the directory itself (set it to 65535).
But unfortunately it looks like DS has not applied the changes. Although I was permited to change the nsslapd-maxdescriptors (so he knows about new OS limit, as when the OS limit was 1024 I wasn't able to set maxdescriptors more than 1024) I still have the limitation of allowed connections set to 960 (it is 1024 = 960 + 64, where 64 is nsslapd-reservedescriptors).
The value of nsslapd-maxconnections is set to 0. My attempts to increase it fail with the message:
additional info: max connection out of range. Valid range is [1..1024].
So, the question is: why does DS consider the connection number limit to be 1024 when the maxdescriptors set to 65535.
Thanks a lot!