TCP TIME_WAIT sockets remain for over 60 seconds

Solution Verified - Updated -


  • TCP TIME_WAIT sockets remain for over 60 seconds
  • High CPU load results in TW reuse failure
  • RHEL is slow to clean out timewait state from old connections
  • Packet capture shows Challenge ACK sent to connection reuse after 1 minute instead of new SYN being accepted, why does RHEL send Challenge ACK?


  • Red Hat Enterprise Linux 7
  • TCP (Transmission Control Protocol) network connections in TIME_WAIT state
  • RHEL listening on TCP port where it is also the Active Closer (sends FIN first)
  • Reuse of the same IP and port tuple

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content