On Thu, Feb 26, 2009 at 4:46 AM, Chavez, James R.
<james.chavez(a)sanmina-sci.com> wrote:
Hello Rich, list,
Earlier today we started getting this error in our FDS error log
repeatedly. Obviously connections were being refused at this point. I
had to restart the directory server for the server to function again.
Prior to releasing this box into production I did set the parameters
according to the Installation guide specifications. The output of
"ulimit -n" is 8192. The output of "sysctl -p" is below.(I increased
fs.file-max from 64000)Does anything look off?
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_keepalive_time = 300
fs.file-max = 128000
net.ipv4.ip_local_port_range = 1024 65000
I also changed the setting in the config from
nsslapd-maxdescriptors: 1024 to
nsslapd-maxdescriptors: 8192
Is there a way to tweak these settings so that this will not happen in
the future?
This is a dedicated consumer or read only replica.
Directory size is roughly 20,000 users.
We are running FC9 and FDS 1.1.1-3.
We are lacking in RAM but look to improve on that shortly.
I do see on the web past posts to this list regarding this error, I am
currently looking through them. Is there anyone out there that has
experienced this and gotten past it?
Thanks
James
[25/Feb/2009:13:30:08 -0600] - Not listening for new connections - too
many fds open
[25/Feb/2009:13:30:08 -0600] - Listening for new connections again
[25/Feb/2009:13:30:08 -0600] - Not listening for new connections - too
many fds open
[25/Feb/2009:13:30:08 -0600] - Listening for new connections again
Hi James,
Have you turned on "nscd" service on client side?
I got same problem and every 3 hours must re-start fds daemon to clear
all client connections and the error gone when I start "nscd" service
on each client.
Thanks,
Teguh
--
Semua rasa ada disini
http://www.teoteblung.co.cc