Re: [Freeipa-users] SLAPD stops answering

2017-01-09 Thread Troels Hansen
- On Jan 9, 2017, at 3:37 PM, Adam Bishop adam.bis...@jisc.ac.uk wrote: > If you attach strace to the slapd process, do you see repeated (failing) calls > to getpeername()? > Actually, just tried attaching a running dirsrv (which responds to requests): This also spawns lots of failing

Re: [Freeipa-users] SLAPD stops answering

2017-01-09 Thread Adam Bishop
On 9 Jan 2017, at 13:06, Troels Hansen wrote: > Anyone with some thoughts about this, other that "Just upgrade". This sounds similar to the behaviour I'm seeing on my standalone instance; though I don't have anything in the error log:

Re: [Freeipa-users] SLAPD stops answering

2017-01-09 Thread Ludwig Krispenz
Hi, there seem to be to issues here, maybe related: a hanging slapd process and the retro CL errors. If the slapd process is not responding can we get a pstack or gdb backtrace (http://www.port389.org/docs/389ds/FAQ/faq.html#debug_crashes) of the process ? About the Retro CL messages, is it

[Freeipa-users] SLAPD stops answering

2017-01-09 Thread Troels Hansen
Hi, we have a IPA installation, which obviously needs upgrading. Its a single server running RHEL7.1 running IPA 4.1 However, it have been running smooth untill now: Rebooting makes everything running again, but only for a few days. It looks like everything fails around 0:17:47 and comes up