Michael S. Moody wrote:
I'm not seeing anything obvious, but in both cases, slapd log
files look
very similar to this. Attached.
I don't see any evidence of crashing in this log though it only covers
about 30 minutes.
I'd check the system logs to see if that shows anything (OOM kiler for
example).
Otherwise this looks like normal operation. Are you sure this covers the
period you saw ns-sladp go away? I guess what do you mean by won't stay
running? How do you notice it isn't running, things not working? It is
that point you'd want to see what is going on: is ns-slapd running but
not responding, is it down altogether, is there a reason why logged
anywhere?
rob
On Thu, Jan 11, 2018 at 3:30 PM, Rob Crittenden <rcritten(a)redhat.com
<mailto:rcritten@redhat.com>> wrote:
Michael S. Moody via FreeIPA-users wrote:
> Within the last week, in two completely separate environments, I've had
> a first master go where the Directory Server won't stay running, and as
> a result, pki-tomcatd, and other services will never start. This has
> happened in two completely separate distinct environments. I've had to
> basically fix it by uninstalling the first master, and putting it back.
>
> Does anyone have any idea why? Is there a bug that started very
> recently? Both on CentOS 7, both slightly different releases of FreeIPA.
Check abrt and /var/log/messages to see if ns-slapd is crashing. If it
is then see
http://directory.fedoraproject.org/docs/389ds/FAQ/faq.html#debugging-crashes
<
http://directory.fedoraproject.org/docs/389ds/FAQ/faq.html#debugging-cras...
rob