[cobalt-users] Re: Stuck Connections

[flash22@xxxxxxx]

On Mon, 1 Oct 2001, Gerald Waugh wrote:

> But, if you can find the stuck proceses with "netstat -tupan"
> tcp        0      0 216.175.178.43:21       216.175.178.40:63385   WAIT
> 15465/proftpd: admi
> Shows that processes 15465 is stuck in wait.
> now issue "kill 15465

Neat port number -/

Ok, as an aside here, having connections repeatedly get stuck in FIN_WAIT
is often a sign of a poorly configured firewall on the clients end,
happens when they go nuts and block all kinds of ICMP traffic and
inadvertantly make it impossible for the client machine to finish telling
the server that it is closing the connection. The server than ends up
waiting around for quite a while before it decides it's not gonna get any
data, not gonna get an error, not gonna get a reset, and finally decides
to assume a closed socket....it can take half a day for it to give up

gsh