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 still present in the just released socat 1.7.4.0

After some more talking with upstream, it seems that the testing script fails for reasons unrelated to socat:

    with this example script using SCTP I often get "Broken pipe" errors on client write. They a caused by the fact that the server/listener runs in
    background detached from stdin, but wants to read from stdin. It gets EOF and consequently shuts down the SCTP connection. When the client is
    not quick enough with writing the connection is already closed, thus that error.

    To work around this effect run the example server in unidirectional mode, not using stdin:

    socat -4 -U - SCTP-LISTEN:9999 &


    btw, with TCP that script would succeed due to half close feature.


I believe we should close this as NOTABUG.

Thanks for looking into it! I am fine with close it and there is a workaround.
Could you explain why this issue only happen on VM not on bare metal?

I am not sure why, I guess it is a harder race condition on metal ?

Thanks, I will close this bug.