Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Oct 1999 12:53:27 +1000 (EST)
From:      Rowan Crowe <rowan@sensation.net.au>
To:        freebsd-isp@freebsd.org
Subject:   TCP connections stuck in "CLOSING" state
Message-ID:  <Pine.BSF.4.01.9910051245490.5467-100000@velvet.sensation.net.au>

next in thread | raw e-mail | index | archive | help
Hi all,

I have a minor(?) problem with TCP sockets apparently not closing properly
on my Squid machine, when I do a netstat there are several of these
showing:

tcp        0      0  proxy3.4884            207.239.35.80.http     CLOSING
tcp        0      0  proxy3.4790            207.239.35.80.http     CLOSING
tcp        0      0  proxy3.4342            207.211.106.40.http    CLOSING
tcp        0      0  proxy3.3957            ny450cd5vip.doub.http  CLOSING
tcp        0      0  proxy3.3318            members7a.tripod.http  CLOSING
tcp        0      0  proxy3.2129            193.60.34.1.http       CLOSING
tcp        0      0  proxy3.4116            res5.geocities.c.http  CLOSING
tcp        0      0  proxy3.2947            thecounter.com.http    CLOSING
tcp        0      0  proxy3.4370            ballard-4.real.c.http  CLOSING
tcp        0      0  proxy3.1741            dl1.yahoo.com.http     CLOSING
tcp        0      0  proxy3.4485            www.raysweb.net.http   CLOSING
tcp        0      0  proxy3.2268            girl-friend.com.http   CLOSING
tcp        0      0  proxy3.4741            windoms.sitek.ne.http  CLOSING
tcp        0      0  proxy3.2189            207.211.106.90.http    CLOSING
tcp        0      0  proxy3.2927            194.217.188.2.http     CLOSING
tcp        0      0  proxy3.2662            www.icq.com.http       CLOSING
tcp        0      0  proxy3.2211            dl3.download.com.http  CLOSING
tcp        0      0  proxy3.1988            38.15.24.93.http       CLOSING
tcp        0      0  proxy3.3972            208.147.89.138.http    CLOSING
tcp        0      0  proxy3.3949            208.147.89.157.http    CLOSING
tcp        0      0  proxy3.4265            216.32.116.201.http    CLOSING

Some of these have been here for weeks. Restarting Squid doesn't change
anything. I seem to recall something in the FAQ about connections stuck in
the FIN_WAIT1 state, but what about CLOSING?

Is the only way to "fix" this to reboot or is it possible for the
superuser to kill off specific sockets? (this was a handy feature in
MS-DOS's KA9Q!). This machine no longer handles any critical routing or
dialin functionality but I'd still prefer not to have to reboot it for
something small like this.

The machine runs 3.2-RELEASE and has been up for 88 days. I don't remember
seeing this when it was running 2.2.5-RELEASE, which is why I'm posting
this message into a FreeBSD specific mailing list. Squid version is
2.2.STABLE3 if that makes any difference.

Any ideas appreciated... thanks. :)

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9910051245490.5467-100000>