2007/2/7, Morris, Patrick <patrick.morris at hp.com>: > > From: fedora-directory-users-bounces at redhat.com > > > > This night, FDS (1.0.2) refused to start after backup. I > > found this in the logs : > > > > [06/Feb/2007:22:04:39 +0100] - slapd stopped. > > Fedora-Directory/1.0.2 B2006.060.1951 > > host:389 (/opt/fedora-ds/slapd-supann) > > > > [06/Feb/2007:22:04:51 +0100] dse - The entry cn=config in > > file /opt/fedora-ds/slapd-supann/config/dse.ldif is invalid, > > error code 53 (DSA is unwilling to perform) - > > nsslapd-maxdescriptors: invalid value "65536", maximum file > > descriptors must range from 1 to 1024 (the current process limit) > > [06/Feb/2007:22:04:51 +0100] dse - Could not load config file > > [dse.ldif] > > How are you settigng your file descriptor limits, and how does the > backup run? Chances are that when the server is restarted after the > backup, they are not set correctly. I'm going to take a wild guess that > it runs out of cron with an environment that's not set with the right > number. Thanks for your answers, To reply the first mail, "ulimit -n" returns 1024. I run my backup with a script called by bacula (which runs with root privileges). Here's the content of the script : #!/bin/sh echo "stopping fedora directory server" /etc/init.d/fds stop echo "rsyncing" /usr/bin/rsync -a --delete /opt/fedora-ds /opt/fedora-ds.rsync sleep 10 echo "starting fedora directory server" /etc/init.d/fds start Do you know what command I should add to this script to set up the environment correctly ? Thanks in advance, -- Mikael Kermorgant
