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.
Fixed a deadlock in asynchronous simple paged results requests
A previous fix to deadlock in the asynchronous simple paged results requests caused another self deadlock due to a regression. To address this problem, a simple `PR_Lock` on a connection object has been replaced with a re-entrant `PR_Monitor`. As a result, the deadlock no longer occurs.
Created attachment 1112618[details]
full stack trace from 310-ccpp-2016-01-07-11-58-56-5760.2016-01-07-11.58.26-5760
Description of problem:
stack trace review request, will need summary change.
apparent ns-slapd crash in RHEL 6.7 IPA context with
1.2.11.15-68.el6_7
I attached 2 stack traces, nearly the same, the long file names have some context information:
sf.01534564.rhel67.389-ds-base-1.2.11.15-68.el6_7.ns-slapd.stacktrace.310-ccpp-2016-01-07-11-58-56-5760.2016-01-07-11.58.26-5760.txt
sf.01534564.rhel67.389-ds-base-1.2.11.15-68.el6_7.ns-slapd.stacktrace.320-ccpp-2016-01-06-13-00-34-28822.txt
there were some initial reports of ns-slapd "hang" in salesforce case number, but I seem to see crashes:
Core was generated by `/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-BS-BR-BSCH -i /var/run/dirsrv/slapd-BS-'.
Program terminated with signal 11, Segmentation fault.
#0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136
136 2: movl %edx, %eax
Version-Release number of selected component (if applicable):
RHEL 6.7
389-ds-base-1.2.11.15-68.el6_7
How reproducible:
N/A
Steps to Reproduce:
1. N/A
2.
3.
Actual results:
Expected results:
Additional info:
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://rhn.redhat.com/errata/RHBA-2016-0737.html
Created attachment 1112618 [details] full stack trace from 310-ccpp-2016-01-07-11-58-56-5760.2016-01-07-11.58.26-5760 Description of problem: stack trace review request, will need summary change. apparent ns-slapd crash in RHEL 6.7 IPA context with 1.2.11.15-68.el6_7 I attached 2 stack traces, nearly the same, the long file names have some context information: sf.01534564.rhel67.389-ds-base-1.2.11.15-68.el6_7.ns-slapd.stacktrace.310-ccpp-2016-01-07-11-58-56-5760.2016-01-07-11.58.26-5760.txt sf.01534564.rhel67.389-ds-base-1.2.11.15-68.el6_7.ns-slapd.stacktrace.320-ccpp-2016-01-06-13-00-34-28822.txt there were some initial reports of ns-slapd "hang" in salesforce case number, but I seem to see crashes: Core was generated by `/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-BS-BR-BSCH -i /var/run/dirsrv/slapd-BS-'. Program terminated with signal 11, Segmentation fault. #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136 136 2: movl %edx, %eax Version-Release number of selected component (if applicable): RHEL 6.7 389-ds-base-1.2.11.15-68.el6_7 How reproducible: N/A Steps to Reproduce: 1. N/A 2. 3. Actual results: Expected results: Additional info: