I have two instances of 389ds 1.2.11.25 (389-ds-base-1.2.11.25-1.el5.x86_64, from EPEL) running on CentOS 5.9 that are crashing at a very regular, 4 hour interval.
There is nothing in the error log about the crash, but it does complain about the "disorderly" shutdown when starting back up which shows the regularity.
[14/Feb/2014:11:17:02 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [14/Feb/2014:15:17:08 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [14/Feb/2014:19:17:15 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [14/Feb/2014:23:16:31 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [15/Feb/2014:03:16:34 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [15/Feb/2014:07:17:52 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [15/Feb/2014:11:13:20 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [15/Feb/2014:15:13:14 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [15/Feb/2014:19:17:24 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [15/Feb/2014:23:16:57 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [16/Feb/2014:03:17:50 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [16/Feb/2014:07:23:20 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [16/Feb/2014:11:18:10 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [16/Feb/2014:15:17:04 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [16/Feb/2014:19:17:55 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [16/Feb/2014:23:20:46 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [17/Feb/2014:03:18:13 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [17/Feb/2014:07:20:29 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [17/Feb/2014:11:17:03 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [17/Feb/2014:15:22:53 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [17/Feb/2014:19:22:01 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [17/Feb/2014:23:23:01 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [18/Feb/2014:03:17:14 -0700] - Detected Disorderly Shutdown last time Directory Server was running, recovering database.
I have an automated process (CFEngine) that restarts the service within 5 minutes of it crashing.
I have a core file, stacktrace, and access log capture that I will attach.
This from IRC: [2014-02-18 15:11:22] <mreynolds> Authority: it crashed from a double free in paged results. I'm not sure if this is a known issue or not.
Access log buffer from core file access.buf
Stacktrace from core file stacktrace.1392755991.txt
Core file, compressed with xz ns-slapd.core.16289.xz
Since 389-ds-base-1.2.11.25-1.el5.x86_64 was released, no Simple Paged Results related bugs were fixed. So, it seems like a new bug.
Looking at the access log (Attachment access.buf​), there is no Simple Paged Results operations logged. I wonder how the crash in the Simple Paged Results occurs in the timing. Do you run some Simple Paged Requests and leave the connection open for a while? Could provide us your use cases?
Also, are you setting nsslapd-idletimeout? If you could share your config file (dse.ldif) with us, that would be useful, too.
Thank you.
The bug seems to have fixed in this version. http://directory.fedoraproject.org/wiki/Releases/1.2.11.29
Could you please upgrade to 1.2.11.29 and retry the test? https://admin.fedoraproject.org/updates/389-ds-base-1.2.11.29-1.el5
In addition to Ticket 47347, a simple paged results bug was fixed fo 47707. I'm closing this ticket as a duplicate of 47707 for now.
If you still see the problem, please feel free to reopen it.
Metadata Update from @authority: - Issue set to the milestone: 1.2.11.30
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1041
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Duplicate)
Login to comment on this ticket.