----- Missatge original -----
Hi,
We had similar problem before, but I am not sure if it is related to
your case.
The file descriptors that were opened by the ns-slapd process was all
in a CLOSE_WAIT state. You can try execute "netstat -anput | grep
CLOSE_WAIT" and see if there's a lot of dangling CLOSE_WAIT socket
opened by ns-slapd.
seems that is not the case.
i can see lot of ESTABLISHED connections, but not a single CLOSE_WAIT. ex:
tcp 0 0 ::ffff:172.26.67.79:389 ::ffff:192.168.224.16:53143 ESTABLISHED
315/ns-slapd
the quick and dirty workaround is restarting the instance every night.
regards,
abosch