RHEL : How to deal with “CLOSE_WAIT” and “TIME_WAIT” connection

Linux How to Document

CLOSE_WAIT is the state for the TCP connection after the remote side has requested a shut down(FIN), and the TCP connection is waiting for the local application to close the socket. There is no timeout for a thread in CLOSE_WAIT state. So need to find out why the receiving application is not doing a proper close() call on the socket


For Example look at the following netstat output:
# netstat -a | grep dcd
      *.dcd               *.*                0      0     0      0 LISTEN
support.dcd         troppus.774           5840      0 10124      0 CLOSE_WAIT
support.dcd         troppus.638           5840      0 10124      0 CLOSE_WAIT
support.dcd         troppus.818           5840      0 10124      0 CLOSE_WAIT
support.dcd         troppus.782           5840      0 10124      0 CLOSE_WAIT
From the about output , you can see several connection are in CLOSE_WAIT  State.


Connection Flow for TCP Connection that leads to CLOSE_WAIT State


How do we Close the CLOSE_WAIT connections?

As of now , there is no reasonable way to clear these connections without doing network restart or server reboot.

::: What is TIME_WAIT Connection?

TIME-WAIT – represents waiting for enough time to pass to be sure the remote TCP received the acknowledgment of its connection termination request. The Connections enter into TIME_WAIT status only during the condition when too many clients connections are established in too short period of time and each clients disconnect the connection quickly
Red Hat Enterprise Linux set this value as 60 seconds in the code level. It’s not changeable, so we don’t have an option on the command line.

How do we Reduce the TIME_WAIT Sockets?

Below Two related parameter could help us to reduce TIME_WAIT sockets, but you have to you have to tune them only on expert advice who knows your environment better.
tcp_tw_recycle – BOOLEAN  – 
 Enable fast recycling TIME-WAIT sockets. Default value is 0. Enabling this option is not recommended since this causes problems when working with NAT(Network Address Translation).
tcp_tw_reuse – BOOLEAN
 Allow to reuse TIME-WAIT sockets for new connections when it is safe from protocol viewpoint. Default value is 0.

How do we activate it?

 Add following lines into /etc/sysctl.conf.
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_tw_reuse = 1
After adding that options, please execute the following command to apply the above changes.
#sysctl -p


I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

You may also like...

1 Response

  1. September 17, 2015

    […] Read – How to deal with “CLOSE_WAIT” and “TIME_WAIT” connection in RHEL […]

What is in your mind, about this post ? Leave a Reply

  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us