Apache connections in FIN_WAIT_2 on Multinet 5.1

Jim

2007-02-02 13:12:18 UTC

On Feb 1, 9:36 pm, Alan Winston - SSRL Central Computing

Post by Alan Winston - SSRL Central Computing
Multinetters --
Multinet 5.1 A-X, VMS 8.3 on DS20E. Don't yet have this week's kernel update
installed.
We're having all kinds of problems with SWS version 2, and seem to have a lot
more SWS processes kicking around than we saw under 1.3. Even when the system
is lightly loaded, Multinet shows a bunch of connections in FIN_WAIT_2 state,
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 72.64.217.78(62712) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 72.64.217.78(62711) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 69.181.166.138(2516) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 69.181.166.138(2515) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 198.129.218.50(59350) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 192.26.251.2(46594) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 192.26.251.2(46593) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.34.133(3662) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.34.133(3661) TIME_WAIT
TCP 0 0 SSRL.SLAC.STANFO(SMTP) SSRL.SLAC.STAN(4171) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.216.14(41657) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.216.14(41656) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STAN(993) 134.79.33.47(2170) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 141.212.45.230(2543) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(4763) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(4759) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(4749) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(4747) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(4733) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(4698) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(4697) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(3266) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(3260) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.19.76(3024) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.34.28(3536) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 150.147.14.186(52060) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 150.147.14.186(52058) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.81.54(2682) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.32.40(2206) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 206.211.159.15(4307) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 134.79.32.136(4006) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 128.163.152.45(3404) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 203.59.9.48(60495) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 128.163.152.45(2800) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 160.45.35.91(4610) FIN_WAIT_2
TCP 0 0 SSRL.SLAC.STANFOR(WWW) 160.45.35.91(4611) FIN_WAIT_2
(and this is pretty consistent whenever we look at it, at least today.)
Is this normal? Is this okay? Can someone explain it to me?

Maybe this will help with some of the explanation...

FIN_WAIT_2 state indicates that your host sent a TCP FIN(ish) request
to the client system signifying that it has completed sending all data
(the local server application has closed the socket). The TCP suite on
the client has ACK(knowledged) back to MultiNet that the FIN request
has been received. However, MultiNet has not received a FIN request
from the client TCP. It expects one and is waiting. The client side
application hasn't yet done it's part in completing the closing
negotiations - perhaps it didn't receive all the data that it
expected? Perhaps there was some network problem? Perhaps the client
application is just misbehaving (maybe the user aborted the request
and the browser doesn't nicely close the socket)?