Our setup uses SSSD which periodically queries a 389DS instance to refresh its cache. The queries request paged results and that crashes the 389DS instance. The instance may run fine for an hour or two before crashing.
After disabling result paging in SSSD there were no more crashes. There are also other applications connecting to the 389DS. If some of them were to use result paging that could crash the server.
We are using the following package versions on CentOS6: sssd-1.9.2-82.10.el6_4.x86_64 389-admin-1.1.29-1.el6.x86_64 389-admin-console-1.1.8-1.el6.noarch 389-admin-console-doc-1.1.8-1.el6.noarch 389-adminutil-1.1.15-1.el6.x86_64 389-console-1.1.7-1.el6.noarch 389-ds-1.2.2-1.el6.noarch 389-ds-base-1.2.11.15-22.el6_4.x86_64 389-ds-base-libs-1.2.11.15-22.el6_4.x86_64 389-ds-console-1.2.6-1.el6.noarch 389-ds-console-doc-1.2.6-1.el6.noarch 389-dsgw-1.1.10-1.el6.x86_64
attachment core_stacktrace.crash-2_with-debuginfo.txt
I am narrowing down the crash, but I am still unable to reproduce. Looks like it is related to doing an abandon and unbind on page 2 or higher of a paged result. I have a custom test client that does this over and over but I cannot crash the server. It seems timing related - the abandon has to happen at just the right time in one thread while the server is sending back a search entry in another thread.
Would it be possible for you to send me a core file? I don't know if you can attach a bzip2'd core file to this ticket - if not, then you can try sending me an email at rmeggins@redhat.com, and if that doesn't work, we can figure something else out.
Trac only allows attachments smaller than 4MB so I sent you an email.
Duplicate of ticket #47367
Metadata Update from @rmeggins: - Issue set to the milestone: N/A
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/946
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)