kern/71184: tcp-sessions hangs on FIN_WAIT_2 state
Pavel Gulchouck
gul at gul.kiev.ua
Tue Aug 31 01:50:24 PDT 2004
>Number: 71184
>Category: kern
>Synopsis: tcp-sessions hangs on FIN_WAIT_2 state
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Aug 31 08:50:23 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Pavel Gulchouck
>Release: FreeBSD 5.3-BETA2 i386
>Organization:
>Environment:
System: FreeBSD cheetah.itpark.com.ua 5.3-BETA2 FreeBSD 5.3-BETA2 #0: Mon Aug 30 23:16:37 EEST 2004 root at cheetah.itpark.com.ua:/usr/obj/usr/src/sys/CUST-DBG i386
>Description:
netstat shows tcp-sessions in the FIN_WAIT_2 state for several days, its
quantity grows with uptime and its does not disappear by timeout. Packets
sends on this sessions with no responds (shows by tcpdump). Here's an
example:
root at cheetah;~>netstat -na | grep FIN_WAIT
tcp4 0 0 193.109.240.9.65053 193.109.240.4.3128 FIN_WAIT_2
tcp4 0 0 193.109.240.9.53877 193.109.241.14.80 FIN_WAIT_2
tcp4 0 0 193.109.240.51.59997 218.36.147.216.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.53426 219.78.239.150.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.52094 221.217.51.76.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.64677 201.129.34.53.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.59761 68.160.224.228.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.61273 67.17.7.10.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.53997 201.130.132.40.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.51541 192.117.121.119.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.50182 218.239.123.122.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.50852 218.80.94.186.113 FIN_WAIT_2
tcp4 0 0 193.109.240.51.25 61.32.51.122.4037 FIN_WAIT_2
root at cheetah;~>tcpdump -i fxp0 host 61.32.51.122
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes
10:28:55.361886 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 3922185006 win 0
10:28:55.362072 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 65535
10:33:40.361292 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 0
10:33:40.361839 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 65535
10:38:25.403144 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 0
10:38:25.403322 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 65535
10:43:10.414956 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 0
10:43:10.415099 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 65535
10:47:55.436833 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 0
10:47:55.437094 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 65535
10:52:40.458684 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 0
10:52:40.458793 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 65535
10:57:25.460519 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 0
10:57:25.460806 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 65535
11:02:10.472346 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 0
11:02:10.472635 IP relay2.itpark.com.ua.smtp > 61.32.51.122.4037: . ack 1 win 65535
I can give addition information (sysctl -a net.inet.tcp, dmesg) if needed.
The same problem exists on 5.2.1-RELEASE-p9.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list