Date: Thu, 4 Nov 1999 13:46:01 -0800 (PST) From: Alfred Perlstein <bright@wintelcom.net> To: "Kenneth D. Merry" <ken@kdm.org> Cc: current@FreeBSD.ORG Subject: Re: TCP sockets stuck in the CLOSING state Message-ID: <Pine.BSF.4.05.9911041344580.12797-100000@fw.wintelcom.net> In-Reply-To: <199911042000.NAA91632@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 4 Nov 1999, Kenneth D. Merry wrote: > > Before I spend a lot of time hunting this down, I figured it might be worth > asking -- is there any particular reason why TCP sockets may be getting > stuck in the CLOSING state more often now? > > I upgraded a machine from -current as of about June 26th to -current as of > last Friday (October 29th), and I've got an ever increasing number of > sockets stuck in the CLOSING state: > > Active Internet connections > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp 0 0 myhost.1929 othermailserver1.auth CLOSING > tcp 0 0 myhost.1904 othermailserver1.auth CLOSING .... > tcp 0 0 myhost.1609 othermailserver1.auth CLOSING > > This didn't seem to happen with the previous version of -current. I looked > through the commitlogs for the TCP code, and I saw some timer changes, but > nothing that looked like it would obviously have this effect. > > Anyone have any ideas? <aol> me too! </aol> Needed to reboot to allow something to bind to the socket. Ie. happening to server side sockets. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9911041344580.12797-100000>