LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   Kill TCP FIN_WAIT2 (https://www.linuxquestions.org/questions/linux-server-73/kill-tcp-fin_wait2-917556/)

azfar 12-07-2011 07:03 AM
Kill TCP FIN_WAIT2
 
Is there a way to kill these hung sessions I have to kill them in order to mount my NFS shares. I tried tcpkill and cutter both didnt helped me. I cant restart the server or even restart the network service.

NETSTAT
Code:
tcp        0      0 10.76.0.1:1019          10.76.0.4:nfs          FIN_WAIT2
TCPDUMP
Code:
10:24:13.621468 IP 10.76.0.1.55301 > 10.76.0.4.nfs: Flags [S], seq 3296458520, win 5840, options [mss 1460,sackOK,TS val 433297913 ecr 0,nop,wscale 5], length 0
10:24:13.621523 IP 10.76.0.4.nfs > 10.76.0.1.55301: Flags [S.], seq 1142351758, ack 3296458521, win 5792, options [mss 1460,sackOK,TS val 1538792 ecr 433297913,nop,wscale 5], length 0
10:24:13.621600 IP 10.76.0.4.nfs > 10.76.0.1.55301: Flags [S.], seq 1142351758, ack 3296458521, win 5792, options [mss 1460,sackOK,TS val 1538792 ecr 433297913,nop,wscale 5], length 0
10:24:13.622001 IP 10.76.0.1.55301 > 10.76.0.4.nfs: Flags [.], ack 1, win 183, options [nop,nop,TS val 433297913 ecr 1538792], length 0
10:24:13.622265 IP 10.76.0.1.1077097113 > 10.76.0.4.nfs: 40 null
10:24:13.622278 IP 10.76.0.4.nfs > 10.76.0.1.55301: Flags [.], ack 45, win 181, options [nop,nop,TS val 1538792 ecr 433297914], length 0
10:24:13.622413 IP 10.76.0.4.nfs > 10.76.0.1.55301: Flags [.], ack 45, win 181, options [nop,nop,TS val 1538792 ecr 433297914], length 0
10:24:13.622461 IP 10.76.0.4.nfs > 10.76.0.1.1077097113: reply ok 24 null
10:24:13.623973 IP 10.76.0.4.nfs > 10.76.0.1.1077097113: reply ok 24 null
10:24:13.623976 IP 10.76.0.1.55301 > 10.76.0.4.nfs: Flags [.], ack 29, win 183, options [nop,nop,TS val 433297914 ecr 1538792], length 0
10:24:13.623987 IP 10.76.0.1.55301 > 10.76.0.4.nfs: Flags [F.], seq 45, ack 29, win 183, options [nop,nop,TS val 433297914 ecr 1538792], length 0
10:24:13.624018 IP 10.76.0.4.nfs > 10.76.0.1.55301: Flags [F.], seq 29, ack 46, win 181, options [nop,nop,TS val 1538792 ecr 433297914], length 0
10:24:13.624182 IP 10.76.0.4.nfs > 10.76.0.1.55301: Flags [F.], seq 29, ack 46, win 181, options [nop,nop,TS val 1538792 ecr 433297914], length 0
10:24:13.624510 IP 10.76.0.1.55301 > 10.76.0.4.nfs: Flags [.], ack 30, win 183, options [nop,nop,TS val 433297914 ecr 1538792], length 0

anomie 12-09-2011 10:59 AM
AFAIK, a connection in FIN_WAIT2 status is not "killable". This state normally happens when an app fails to properly tear down its TCP connection.

Curious: what sequence of events is leading you to that?

azfar 12-16-2011 03:29 AM
OK i restarted the machine and then use the 'intr' option in my mounts. Now I can use the tcpkill or other utilities to forcefully kill it.


All times are GMT -5. The time now is 02:14 PM.