If multiple threads call ldap_initialize at the same time, the program will crash. We have seen this in the server and in threaded tools such as ldclt on multiple platforms with openldap 2.4.24-2.4.30. Threaded programs need to have a mutex around calls to ldap_initialize.
This can be reproduced by increasing the number of threads used by ldclt - you should eventually hit the crash - or by configuring the directory server with many (8) replication agreements, and repeatedly stopping and starting the server. It will eventually crash at startup.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=815991
0001-Ticket-348-crash-in-ldap_initialize-with-multiple-th.patch 0001-Ticket-348-crash-in-ldap_initialize-with-multiple-th.patch
To ssh://git.fedorahosted.org/git/389/ds.git d4327cf..23c0889 master -> master commit changeset:23c0889/389-ds-base Author: Rich Megginson rmeggins@redhat.com Date: Tue Apr 24 20:09:38 2012 -0600
389-ds-base-1.2.10 branch commit changeset:3f73fa5/389-ds-base Author: Rich Megginson rmeggins@redhat.com Date: Tue Apr 24 20:09:38 2012 -0600
Added initial screened field value.
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.10.7
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/348
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: Fixed)
Log in to comment on this ticket.