Hi,
On Sat, 15 Mar 2014, GALAMBOS Daniel wrote:
Thanks, but there is only one ldap releated cronjob, it monitors the slapd resource usage, but that did not do anything. For logging we use rsyslogd, and reloading, restarting or stopping the rsyslogd doesn't affect the slapd. Also there are no logrotate config which restarts the slapd, only reloades the rsyslog.
These were also checked by one of our senior sysadmins.
well you need to keep searching then.
The message:
Mar 15 07:06:25 ldap1 slapd[2798]: daemon: shutdown requested and initiated.
you are sseing is from slapd receiving a HUP signal, so something must be sending it.
1. check again all user crontabs and the system crontab once more 2. search your disk for anything referencing slapd.pid ( grep -r slapd.pid / ) 3. check the dmesg output for OOM killer in case linux is killing slapd because of memory usage 4. check all other logs around the time slapd is being stopped 5. check all scripts under /etc/logratate.d 6. anything else you can think of
Most of the slapd shutdowns happens at 7:01, 8:01 ... etc when other machines uses the ldap more than usually(syncing users to other system what can't use ldap, generating mail identities to users...), but there are "only" 3-7 shutdown per day. There are sometimes a day, when it survives the whole day.
could well be linux OOM or anything else that rate limits processes based on load...
The slapd runs on a VM with 6 GiB memory (slapd uses 7-900MiB), the VM is dedicated for the slapd.
Greetings Christian
<snipp/>