LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

CLOSE & CLOSE_WAIT

To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: CLOSE & CLOSE_WAIT
From: "Michael McConnell" <michaelm@xxxxxxxxxxx>
Date: Fri, 28 Sep 2001 14:11:48 -0700
I'm running an application with a bit of a bug in it. If you establish a TCP connection to it, and do not send a session command, the string "bye," to this application it leaves some funny states displayed by netstat. (note: saying bye isn't always an option)
 
tcp        0      0 127.0.0.1:9000          127.0.0.1:1679          CLOSE_WAIT 
tcp        0      0 127.0.0.1:9000          127.0.0.1:1635          CLOSE      
(there are about 2000 of them listed, fortunately I have 16000 descriptors to play with... so I have a couple days to fix this)
I can understand netstat -an displaying descriptors in a CLOSE_WAIT, but in a CLOSE state? I've seen many of these listed in a close state for upwards of 2 days...
 
Can anyone tell me the kernel timeout value of a CLOSE, or is there one?
Can I adjust these values via proc?
Is this a 2.2 Kernel bug?
 
I've set
echo 1800 > /proc/sys/net/ipv4/tcp_keepalive_time
 
 
 
 
<Prev in Thread] Current Thread [Next in Thread>
  • CLOSE & CLOSE_WAIT, Michael McConnell <=