Hi all.

I'm having a problem I thought I had resolved.

[EMAIL PROTECTED] ~]# grep files /var/log/messages
Jan  8 10:20:16 alpha slapd[21093]: warning: cannot open /etc/ 
hosts.allow: Too many open files
Jan  8 10:20:18 alpha slapd[21093]: warning: cannot open /etc/ 
hosts.allow: Too many open files
Jan  8 10:25:28 alpha slapd[21093]: warning: cannot open /etc/ 
hosts.allow: Too many open files
...

When this happens LDAP stops responding and everything falls to  
pieces.  LTSP logins fail, email fails and ltsp sessions grind to a  
halt.  I had been running a file server as the primary LDAP server  
with a couple of secondary slave servers.  The file server started  
having the same issues so I added a couple more slaves and reordered  
the host entry in my ldap.conf file of the client server to try to  
balance the load.  For the first time, one of the new slaves started  
reporting the same issue.  When LDAP on the slave stopped responding  
I assumed pam (reading /etc/ldap.conf) would move to the next slave.   
Its not.

Has anyone else run into this problem?  I know how to increase the  
number of allowed file handles.  What is the best way to determine  
what has all the files opened?  This server runs LDAP, bind and  
DHCP.  It is mirrored by another server with an identical  
configuration.  Both are Redhat ES 4.

Thanks,

Jason



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to