RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1278755 - deadlock on connection mutex
Summary: deadlock on connection mutex
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
Petr Bokoc
Depends On:
Blocks: 1299346
TreeView+ depends on / blocked
Reported: 2015-11-06 11:06 UTC by German Parente
Modified: 2020-09-13 21:35 UTC (History)
6 users (show)

Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Connection objects no longer deadlock Previously, an unnecessary lock was sometimes acquired on a connection object, which could then cause a deadlock. A patch has been applied to remove the unnecessary locking, and the deadlock no longer occurs.
Clone Of:
: 1299346 (view as bug list)
Last Closed: 2016-11-03 20:37:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1672 0 None closed deadlock on connection mutex 2020-10-02 09:39:05 UTC
Red Hat Product Errata RHSA-2016:2594 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2016-11-03 12:11:08 UTC

Description German Parente 2015-11-06 11:06:23 UTC
Description of problem:

this is a clone from upstream ticket 48341 

Version-Release number of selected component (if applicable): 389-ds-base- 

Details can be found in upstream ticket:

Thread 7 (Thread 0x7f8ab310c700 (LWP 7761)):
#0  0x00007f8b0050bb7d in poll () from /lib64/libc.so.6
#1  0x00007f8b00e43967 in _pr_poll_with_poll () from /lib64/libnspr4.so
#2  0x00007f8b02f239e8 in connection_read_operation ()
#3  0x00007f8b02f248df in connection_threadmain ()
#4  0x00007f8b00e477bb in _pt_root () from /lib64/libnspr4.so
#5  0x00007f8b007e8df5 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f8b005161ad in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f8b02eee840 (LWP 7715)):
#0  0x00007f8b007eef7d in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x00007f8b007ead68 in _L_lock_975 () from /lib64/libpthread.so.0
#2  0x00007f8b007ead11 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3  0x00007f8b00e41cb9 in PR_Lock () from /lib64/libnspr4.so
#4  0x00007f8b02f291e5 in slapd_daemon ()
#5  0x00007f8b02f1c17c in main ()

This behavior has been seen in several customer cases. I am associating two ones to this ticket.

Comment 8 Mike McCune 2016-03-28 23:13:32 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 10 Simon Pichugin 2016-07-12 15:43:13 UTC
Build tested:

Verification steps:
1. Set up IPA with SSL enabled:

2. Uninstall IPA server:
ipa-server-install --uninstall

3. Repeat 1 and 2 steps a few times.

All steps has successfully PASS. Nothing has hung.

Marking as verified.

Comment 12 errata-xmlrpc 2016-11-03 20:37:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.