Re: slapd shuts down for no reason

[GALAMBOS Daniel <dancsa@dancsa.hu>]

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.

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.

The slapd runs on a VM with 6 GiB memory (slapd uses 7-900MiB), the VM
is dedicated for the slapd.

Dancsa

On 2014-03-15 14:23, Christian Kratzer wrote:
> Hi,
>
> On Sat, 15 Mar 2014, GALAMBOS Daniel wrote:
>
>> Hi,
>>
>> We recently left the debian openldap, and compiled the 2.4.39 and
>> installed on our servers.
>>
>> The old slapd failed multiple times a day, and now the new one too.
>
> It doesn't fail. See below ...
>
>> The log says:
>> Mar 15 07:06:25 ldap1 slapd[2798]: daemon: shutdown requested and
>> initiated.
>
> your slapd received a HUP signal and has stopped gracefully.
>
> <snipp/>
>> I've run out of the ideas.
>>
>> The configure was with the following switches: --enable-crypt
>> --enable-spasswd --enable-modules --enable-ppolicy --enable-syncprov
>> --enable-unique --with-cyrus-sasl   using libdb5.1-dev (deb 5.1.29-5)
>>
>> Can you give me some pointers where to search for errors?
>
> do you have a cronjob using kill -HUP to the slapd pid for some kind
> of log rotation setup ?
>
> Check your logrotate configs etc...
>
> Greetings
> Christian
>