Bug 1580523
| Summary: | 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] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | 389-ds-base | Assignee: | mreynolds |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | high | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | high | ||
| Version: | 7.5 | CC: | enewland, gparente, mmuehlfe, mreynolds, msauton, nkinder, rmeggins, tbordaz, tmihinto, vashirov |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1567042 | Environment: | |
| Last Closed: | 2018-06-26 16:49:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1567042 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-05-21 17:12:10 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. 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 |