[SOLVED] Fedora Directory Server not accepting new connections

custangro · 04-05-2010, 01:36 PM

Looks like our Directory Server stopped answering

[/code]
[05/Apr/2010:11:24:18 -0700] - Not listening for new connections - too many fds open
[05/Apr/2010:11:24:19 -0700] - Listening for new connections again
[05/Apr/2010:11:24:19 -0700] - Not listening for new connections - too many fds open
[05/Apr/2010:11:24:25 -0700] - Listening for new connections again
[05/Apr/2010:11:24:25 -0700] - Not listening for new connections - too many fds open
[05/Apr/2010:11:24:26 -0700] - Listening for new connections again
[05/Apr/2010:11:24:26 -0700] - Not listening for new connections - too many fds open
[05/Apr/2010:11:24:26 -0700] - Listening for new connections again
[05/Apr/2010:11:24:26 -0700] - Not listening for new connections - too many fds open
[05/Apr/2010:11:24:34 -0700] - Listening for new connections again
[05/Apr/2010:11:24:34 -0700] - Not listening for new connections - too many fds open
[05/Apr/2010:11:24:45 -0700] - Listening for new connections again
[05/Apr/2010:11:24:45 -0700] - Not listening for new connections - too many fds open
[05/Apr/2010:11:24:55 -0700] - Listening for new connections again
[05/Apr/2010:11:24:55 -0700] - Not listening for new connections - too many fds open
[05/Apr/2010:11:25:05 -0700] - Listening for new connections again
[05/Apr/2010:11:25:05 -0700] - Not listening for new connections - too many fds open[/code]

I failed over to our backup DS...but not sure why it stopped responding

-C

acid_kewpie · 04-05-2010, 04:07 PM

it says there are too many fds open.... ;-) that means File Descriptors. An "lsof" will show that that the ns-slapd process will have maxed out it's allowed file handles, 1024 by default. This might be network connections, log files, shared libraries etc...

custangro · 04-05-2010, 04:51 PM

Quote:

Originally Posted by acid_kewpie

it says there are too many fds open.... ;-) that means File Descriptors. An "lsof" will show that that the ns-slapd process will have maxed out it's allowed file handles, 1024 by default. This might be network connections, log files, shared libraries etc...

Which would make sense as my network is growing

Okay; just wondering what "fds" stood for...thanks

-C

custangro · 05-19-2011, 11:22 AM

I know this is an "oldie" but I thought I'd post some tuning I did to help "ease" the issue

First the /etc/sysctl.conf

Code:

echo "fs.file-max = 203568" >> /etc/sysctl.conf
      
echo "* soft nofile 8192" >> /etc/security/limits.conf
      
echo "* hard nofile 8192" >> /etc/security/limits.conf
      
echo "ulimit -n 8192" >> /etc/profile

Next edit the /etc/sysconfig/dirsrv file and uncomment the following line

Code:

ulimit -n 8192

Next edit your /etc/sysconfig/dirsrv/slapd-instance/dse.ldif file and change the nsslapd-maxdescriptors entry

Code:

nsslapd-maxdescriptors: 8192

Now load up your sysctl entries and restart your dirsrv

Code:

sysctl -p
/etc/init.d/dirsrv restart

This should increase your FDS available to the dirsrv

acid_kewpie · 05-20-2011, 12:56 AM

hey, it's your thread, totally fine. Must've been very confusing with FDS reporting too many FDS's open!

infinitiguy · 03-26-2012, 04:11 PM

a note about /etc/sysconfig/dirsrv/slapd-instance/dse.ldif.

I found that I needed to stop ldap before I could edit this file. Otherwise any edits I made were overwritten when I restarted.

stop
edit
start
magic