Re: mysterious stuck connections

From: Dan Kegel (dank@alumni.caltech.edu)
Date: Thu May 18 2000 - 18:46:53 EST


> [dank@krunch dev]$ netstat -a | grep 4276
> Proto Recv-Q Send-Q Local Address Foreign Address State
> tcp 72 0 masqhost:5210 masqhost:4276 ESTABLISHED
> tcp 0 0 masqhost:4276 masqhost:5210 ESTABLISHED
>
> That means the kernel is waiting for the server process to read 72 bytes
> (probably the first 72 bytes after the connection is established).
> This looks like a bug on my part.

This was indeed caused by my program not calling accept().

> [dank@krunch dev]$ netstat -a | grep 4292
> Proto Recv-Q Send-Q Local Address Foreign Address State
> tcp 0 72 masqhost:4292 masqhost:5210 ESTABLISHED
> tcp 0 0 masqhost:5210 masqhost:4292 SYN_RECV
>
> That means the server (port 5210) is waiting for the client to send an ACK, I think.
> I don't understand how this one could be my fault.

This one went away when I fixed the other one.
This was probably a connection that arrived after the backlog
queue had already filled up.

Sorry for the noise.

- Dan

-- 
Entia non sunt multiplicanda praeter necessitatem.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:16 EST