Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This bug is created as a clone of upstream ticket:
https://pagure.io/389-ds-base/issue/49175
#### Issue Description
When fixing our freeipa cluster & redeploying of some replicas, I hit strange ns-slapd crashes. After little debugging & ASANning, I nailed down double-free in cl5NewDBFile error path. Patch is attached, feel free to ask me if you need more info.
#### Package Version and Platform
CentOS 7.2
$ rpm -q 389-ds-base
389-ds-base-1.3.5.10-11.x86_64
#### Steps to reproduce
1. Fill IPC semaphore table (/usr/bin/ipcs) - in my case all available semaphores were consumed by httpd
2. Try to setup replication (I installed FreeIPA replica)
#### Actual results
Crash:
$ dmesg -T
[Sat Mar 18 20:59:31 2017] traps: ns-slapd[3454] general protection ip:7f2fa2f08abd sp:7f2f787ef560 error:0 in libc-2.17.so[7f2fa2e8d000+1b7000]
#### Expected results
ns-slapd shouldn't crash, it should write errors to the log.
Fixed upstream
Build tested:
389-ds-base-1.3.6.1-14.el7.x86_64
[1] Exhaust available semaphores:
# for i in $(seq 1 $(awk '{print $NF}' /proc/sys/kernel/sem)); do ipcmk -S 1; done
[2] Run replication test:
# py.test -s -v /export/tests/suites/replication/acceptance_test.py::test_add_entry
Expectedly test fails, because server fails to create semaphore:
May 20 15:01:57 XXX ns-slapd[13260]: [20/May/2017:15:01:57.577477095 -0400] - ERR - NSMMReplicationPlugin - changelog program - _cl5NewDBFile - Failed to create semaphore /var/lib/dirsrv/slapd-master_2/changelogdb/97d41bc5-3d8e11e7-93918b95-29c229d4.sema; NSPR error - -5956
But it doesn't crash. Marking as VERIFIED.
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-2017:2086