Del wrote:
Hi,
The first of the init scripts, here:
http://directory.fedora.redhat.com/wiki/Howto:SysVInit
(URL to script:
http://www.directory.fedora.redhat.com/download/FedoraDirectoryServer-init.d)
... does not start the Fedora Directory Server on boot if the system ulimit
has been changed before the installation of FDS. If FDS detects a higher
ulimit then it will write:
(e.g.)
nsslapd-maxdescriptors: 8192
to:
/opt/fedora-ds/slapd-(servername)/config/dse.ldif
So that when the script above is run during bootup, the following message
will be generated in the logs, and FDS won't start:
dse - The entry cn=config in file
/opt/fedora-ds/slapd-fc3-dbw-1/config/dse.ldif
is invalid, error code 53 (DSA is unwilling to perform) -
nsslapd-maxdescriptors:
invalid value 8192, maximum file descriptors must range from 1 to 1024
(the
current process limit)
To fix this, insert the string:
ulimit -n 8192
On top of that, you also have to put the same ulimit line in any scripts
which call ns-slapd (bak2db, db2bak, bak2ldif, ldif2bak, etc). This
"feature" caused me major problems several weeks ago when those scripts
failed and left some files with wrong permissions, thus causing nearly
impossible to debug write deadlocks.
I really hope that this is redesigned in an upcoming release.
--
mike
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
