From owner-freebsd-isp Sun Nov 7 17: 3:23 1999 Delivered-To: freebsd-isp@freebsd.org Received: from velvet.sensation.net.au (tunnel0-velvet-brunswick.sensation.net.au [203.20.114.195]) by hub.freebsd.org (Postfix) with ESMTP id 851A914C26 for ; Sun, 7 Nov 1999 17:03:06 -0800 (PST) (envelope-from rowan@sensation.net.au) Received: from localhost (rowan@localhost) by velvet.sensation.net.au (8.8.8/8.8.8) with SMTP id MAA19338 for ; Mon, 8 Nov 1999 12:02:58 +1100 (EST) (envelope-from rowan@sensation.net.au) X-Authentication-Warning: velvet.sensation.net.au: rowan owned process doing -bs Date: Mon, 8 Nov 1999 12:02:55 +1100 (EST) From: Rowan Crowe To: freebsd-isp@freebsd.org Subject: sockets stuck in "CLOSING" state: 3.2-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I posted a message about this a while ago but I never received a response. I am still having problems with TCP sockets getting stuck in the "CLOSING" state. The machine is now up to 57 such sockets, and this number keeps rising since they never seem to die off. This machine's main function is proxying (Squid). My 2.x machine also running Squid has *zero* sockets stuck in the CLOSING state! Both are running the same version of Squid. I'm wondering if anyone else is seeing this behaviour, particularly only on a 3.x machine... before I upgraded the problem server from 2.2.5-RELEASE to 3.2-RELEASE I'd never seen this problem. Any suggestions (apart from "reboot it" ;-) ) or experiences appreciated. Cheers. -- Rowan Crowe http://www.rowan.sensation.net.au/ Sensation Internet Services http://www.sensation.net.au/ Melbourne, Australia Phone: +61-3-9388-9260 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message