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 1580523 - ns-slapd segfaults with ERR - connection_release_nolock_ext - conn=0 fd=0 Attempt to release connection that is not acquired [rhel-7.5.z]
Summary: ns-slapd segfaults with ERR - connection_release_nolock_ext - conn=0 fd=0 Att...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.5
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
Marc Muehlfeld
URL:
Whiteboard:
Depends On: 1567042
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-21 17:12 UTC by Oneata Mircea Teodor
Modified: 2021-09-09 14:09 UTC (History)
10 users (show)

Fixed In Version: 389-ds-base-1.3.7.5-22
Doc Type: Bug Fix
Doc Text:
Directory Server uses the nunc-stans framework to manage connection events. This framework requires that only one handler is scheduled at a time. Previously, when the server shut down, the closure handler was scheduled at the same time as a read handler. As a consequence, a "connection that is not acquired" warning was logged and, in certain situations, Directory Server terminated unexpectedly. With this update the server only schedules one handler at a time. As a result, the warning is no longer logged and the server does not crash during shutdown.
Clone Of: 1567042
Environment:
Last Closed: 2018-06-26 16:49:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1988 0 None None None 2018-06-26 16:49:53 UTC

Description Oneata Mircea Teodor 2018-05-21 17:12:10 UTC 
This bug has been copied from bug #1567042 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 6 Viktor Ashirov 2018-06-13 17:47:54 UTC 
Build tested: 389-ds-base-1.3.7.5-23.el7_5.x86_64

I don't observe crash at shutdown anymore in my tests with ipa-server-install.

Marking as VERIFIED SanityOnly.
Comment 8 errata-xmlrpc 2018-06-26 16:49:33 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.

https://access.redhat.com/errata/RHBA-2018:1988
Note You need to log in before you can comment on or make changes to this bug.