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.
DescriptionStanislav Zidek
2016-09-06 10:51:08 UTC
Description of problem:
After fixing bz1170722, occurence of the problem lowered, but I am still getting the bad behaviour sometimes, newly accompanied by INTERNAL ERROR. Filing this bug to track the issue.
Version-Release number of selected component (if applicable):
stunnel-4.56-6.el7
How reproducible:
sometimes
Steps to Reproduce:
1. run /CoreOS/stunnel/Regression/bz1170722-stunnel-loses-data-due-to-mishandled-POLLHUP (or do something equivalent - transfer a lot of data through stunnel and immediately close the connection)
Actual results:
:: [ FAIL ] :: File '/var/tmp/tmp.ZaFmmStLcj' should contain '1000000000'
...
:: [ BEGIN ] :: Running 'cat stunnel.log'
...
2016.09.06 05:48:34 LOG3[16351:70367262404816]: INTERNAL ERROR: s_poll_wait returned 0, but no descriptor is ready
...
:: [ PASS ] :: Command 'cat stunnel.log' (Expected 0, got 0)
Expected results:
* right file size
* no INTERNAL ERROR
Additional info:
See bz1170722 for details of the original issue.
There is no customer case associated with the issue, it is low severity, the fix is not known and would be with high probability non-trivial with risk of breaking other things. I am closing this.