Hello, I'd like to ask you here for help with problem with 389 Fedora LDAP. Our LDAP fail every day, because of "too many fds open" problem, as is logged in log file… I've found many posts about it on internet (this is one seems to be useful http://www.linuxquestions.org/questions/linux-enterprise-47/fedora-directory...), but still the problem is there even after raise of few limits.
When the ldap failed, I checked number of created "fd" by dirsrv process with ls -l /proc/$DIRSRV_PID/fd | wc -l and it was about ~1000 files, so probably some limit in system is still in use (fds per process or user??).
Please, could you give me a hint? Thanks a lot!
you need to edit /etc/security/limits.conf add an entry for nofile the the default is 1024 the max is 65536 (1024 * 64 ) here is an extreme example setting it to the max for all users
" * hard nofile 65536 * soft nofile 65536 "
after you have made the change log out and log back in you can use "ulimit -a " to verify after you log back in then restart the directory server.
On 8/26/2011 2:11 AM, Martin Stiborský wrote:
Hello, I'd like to ask you here for help with problem with 389 Fedora LDAP. Our LDAP fail every day, because of "too many fds open" problem, as is logged in log file… I've found many posts about it on internet (this is one seems to be useful http://www.linuxquestions.org/questions/linux-enterprise-47/fedora-directory...), but still the problem is there even after raise of few limits.
When the ldap failed, I checked number of created "fd" by dirsrv process with ls -l /proc/$DIRSRV_PID/fd | wc -l and it was about ~1000 files, so probably some limit in system is still in use (fds per process or user??).
Please, could you give me a hint? Thanks a lot!
That is not enough. You have to update /etc/sysconfig/dirsrv
Otherwise, the process will still only get 1024.
On Fri, Aug 26, 2011 at 10:28 AM, Paul Robert Marino pmarino@snap-interactive.com wrote:
you need to edit /etc/security/limits.conf add an entry for nofile the the default is 1024 the max is 65536 (1024 * 64 ) here is an extreme example setting it to the max for all users
"
- hard nofile 65536
- soft nofile 65536
"
after you have made the change log out and log back in you can use "ulimit -a " to verify after you log back in then restart the directory server.
well her is the section from that file that talks about it # In order to make more file descriptors available # to the directory server, first make sure the system # hard limits are raised, then use ulimit - uncomment # out the following line and change the value to the # desired value # ulimit -n 8192
if you increase both the hard and soft limit there is no reason to run the ulimit command keep in mind the soft limit is the default.
On 8/26/2011 12:54 PM, cfr100@acm.org wrote:
That is not enough. You have to update /etc/sysconfig/dirsrv
Otherwise, the process will still only get 1024.
On Fri, Aug 26, 2011 at 10:28 AM, Paul Robert Marino pmarino@snap-interactive.com wrote:
you need to edit /etc/security/limits.conf add an entry for nofile the the default is 1024 the max is 65536 (1024 * 64 ) here is an extreme example setting it to the max for all users
"
hard nofile 65536
soft nofile 65536
"
after you have made the change log out and log back in you can use "ulimit -a " to verify after you log back in then restart the directory server.
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Hi,
cat /proc/<PID>/limits
You can check what effective ulimits are applied to your process. To use this feature, your kernel has to be at least 2.6.25, if vanilla. RHEL5.2+ or 5.3+ (I don't remember exactly) if on RedHat.
Hope this helps Marco
2011/8/26 Martin Stiborský martin.stiborsky@gmail.com
Hello, I'd like to ask you here for help with problem with 389 Fedora LDAP. Our LDAP fail every day, because of "too many fds open" problem, as is logged in log file… I've found many posts about it on internet (this is one seems to be useful http://www.linuxquestions.org/questions/linux-enterprise-47/fedora-directory... ), but still the problem is there even after raise of few limits.
When the ldap failed, I checked number of created "fd" by dirsrv process with ls -l /proc/$DIRSRV_PID/fd | wc -l and it was about ~1000 files, so probably some limit in system is still in use (fds per process or user??).
Please, could you give me a hint? Thanks a lot!
-- S pozdravem Martin Stiborský
Jabber: stibi@njs.netlab.cz
389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
389-users@lists.fedoraproject.org