From owner-freebsd-current Thu Nov 4 13:22:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 68C8815210 for ; Thu, 4 Nov 1999 13:22:09 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id NAA21840; Thu, 4 Nov 1999 13:46:01 -0800 (PST) Date: Thu, 4 Nov 1999 13:46:01 -0800 (PST) From: Alfred Perlstein To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG Subject: Re: TCP sockets stuck in the CLOSING state In-Reply-To: <199911042000.NAA91632@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? me too! 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