Date: Tue, 28 Sep 1999 16:16:06 -0700 (PDT) From: rob@ideal.net.au To: freebsd-gnats-submit@freebsd.org Subject: kern/14026: Many network connections get left in the 'CLOSING' state Message-ID: <19990928231606.BEF2114FA5@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 14026 >Category: kern >Synopsis: Many network connections get left in the 'CLOSING' state >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 28 16:20:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Rob Wise >Release: FreeBSD 3.2-STABLE from July 1999 >Organization: >Environment: FreeBSD proton.ideal.net.au 3.2-STABLE FreeBSD 3.2-STABLE #2: Thu Jul 15 11:04:40 EST 1999 rob@proton.ideal.net.au:/usr/src/sys/compile/PROTON i386 >Description: The machine displaying this problem is running squid and 2 fairly busy websites which have large files on them. I'm not sure if file size is related. After the machine has been up and running for a while many connections are visible in netstat which are stuck in the 'CLOSING' state. For example: tcp 0 0 proxy1.syd.8080 port19.syd.2197 CLOSING tcp 0 0 proxy1.syd.8080 port56.cam.1779 CLOSING These connections can't be cleared by shutting down either the squid or apache daemons. The machine must be restarted to clear them. The machine has 512MB of ram, a PII350 processor, Adaptec 2940UW scsi controller, and a Netgear 10/100 nic using the de0 driver. Tcp extensions are turned off too. >How-To-Repeat: The stuck connections gradually start appearing during normal usage on the machine. >Fix: Unknown. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990928231606.BEF2114FA5>