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

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
0 (0)
Article Rating (No Votes)
Rate this article
There are no attachments for this article.
There are no comments for this article. Be the first to post a comment.
Full Name
Email Address
Security Code Security Code
Related Articles RSS Feed
LVM: Rename root VG/LV
Viewed 962 times since Sat, Jun 2, 2018
Need to set up yum repository for locally-mounted DVD on Red Hat Enterprise Linux 7
Viewed 761 times since Mon, Oct 29, 2018
Jak wygenerować silne hasła jednorazowe w Linuksie?
Viewed 835 times since Thu, May 24, 2018
SSL HowTo: Decode CSR
Viewed 466 times since Mon, Feb 18, 2019
Super Grub2 Disk
Viewed 650 times since Wed, May 22, 2019
20 Practical Examples of RPM Commands in Linux rpm
Viewed 973 times since Mon, Feb 18, 2019
How to use yum command on CentOS/RHEL
Viewed 1042 times since Wed, Oct 17, 2018
Top 20 OpenSSH Server Best Security Practices - good article
Viewed 562 times since Mon, Oct 1, 2018
ZPOOL: Grow a zpool by adding new device(s)
Viewed 612 times since Sun, Jun 3, 2018
RHEL: Change system’s hostname
Viewed 983 times since Sun, May 27, 2018