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.
Created attachment 1187189[details]
full bt
Description of problem:
this is a clone of upstream ticket 48882 for RHEL6.
The server hangs with the scheduler thread locked by another working thread which makes the server unresponsive.
the stack differs from what seen in 48882 since the api's for RHEL6 are completely different.
We should be something of this sort in thread 1. Then another working thread, in this case a search blocked in IO sending data back to client operation.
The full stack trace of customer case is attached.
Version-Release number of selected component (if applicable): 1.2.11.15-68
How reproducible: difficult to reproduce.
Additional info:
a nsslapd-ioblocktimeout small enough could workaround the issue.
Created attachment 1187189 [details] full bt Description of problem: this is a clone of upstream ticket 48882 for RHEL6. The server hangs with the scheduler thread locked by another working thread which makes the server unresponsive. the stack differs from what seen in 48882 since the api's for RHEL6 are completely different. We should be something of this sort in thread 1. Then another working thread, in this case a search blocked in IO sending data back to client operation. The full stack trace of customer case is attached. Version-Release number of selected component (if applicable): 1.2.11.15-68 How reproducible: difficult to reproduce. Additional info: a nsslapd-ioblocktimeout small enough could workaround the issue.