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.

Bug 968503

Summary:	flush_ber error sending back start_tls response will deadlock
Product:	Red Hat Enterprise Linux 6	Reporter:	Rich Megginson <rmeggins>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED ERRATA	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	jgalipea, jrusnack, lnovich, nhosoi, nkinder, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-22.el6	Doc Type:	Bug Fix
Doc Text:	Cause: The server is processing a startTLS request and gets an error (network error usually) attempting to write the response back to the client. Consequence: The server will hang and become unresponsive to this an any new connection request, due to a deadlock in the connection handling code. Fix: Make sure the connection is not locked when this error condition occurs. Result: Server correctly processes startTLS requests when there are network errors, and continues to work fine for established and new connection requests.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 21:08:19 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:

Description Rich Megginson 2013-05-29 19:35:51 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47375

If the server is processing a start tls extop, and is sending back the "Start TLS request accepted.Server willing to negotiate SSL." response, and the ber_flush() call in flush_ber() returns non-zero, the server will deadlock.

One problem is that it is very difficult to get the server to return an error at this point.  The customer is using an F5 load balancer and that seems to have something to do with it.

Comment 6 Ján Rusnačko 2013-08-01 12:32:28 UTC

Is it possible to automate this ? If yes, could you please add verification steps ?

Comment 7 Rich Megginson 2013-08-01 14:18:20 UTC

(In reply to Ján Rusnačko from comment #6)
> Is it possible to automate this ? If yes, could you please add verification
> steps ?

We do not know how to reproduce this, much less automate.  The customer has verified that the patch works, so I think we will just have to mark the bug as verified by customer.

Comment 9 Ján Rusnačko 2013-09-25 07:32:49 UTC

Verified sanity only on 389-ds-base-1.2.11.15-24.el6.

Comment 10 errata-xmlrpc 2013-11-21 21:08:19 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.

http://rhn.redhat.com/errata/RHBA-2013-1653.html