From owner-freebsd-net@FreeBSD.ORG Fri Jun 27 19:57:54 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E1A110656D4 for ; Fri, 27 Jun 2008 19:57:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id C0EE58FC15 for ; Fri, 27 Jun 2008 19:57:52 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 19FB346C92; Fri, 27 Jun 2008 15:57:52 -0400 (EDT) Date: Fri, 27 Jun 2008 20:57:52 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Paul In-Reply-To: <4864E0FE.40708@gtcomm.net> Message-ID: <20080627205708.S40819@fledge.watson.org> References: <486283B0.3060805@transip.nl> <5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc> <48648D70.50304@transip.nl> <4864E0FE.40708@gtcomm.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Ali Niknam , net@freebsd.org Subject: Re: FreeBSD 7.0: sockets stuck in CLOSED state... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 19:57:54 -0000 On Fri, 27 Jun 2008, Paul wrote: > I have the same 'problem' if that helps any.. Sockets stuck for over a month > in CLOSED and they have a * for the port on the source IP. tcp4 0 0 > 67.1.1.1.* 67.1.1.2.1261 CLOSED 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #6: > Thu Apr 17 18:11:49 EDT 2008 amd64 Doesn't seem to cause any issues though. If you use "sockstat" to list the sockets open in processes, do any match the entry in netstat? If so, which? If you shut down that program, does the entry disappear from netstat? Robert N M Watson Computer Laboratory University of Cambridge > > > > Eygene Ryabinkin wrote: >> Ali, good day. >> >> Fri, Jun 27, 2008 at 08:49:20AM +0200, Ali Niknam wrote: >> >>>> Just a quick "me too" message: I also used to see this on my 7.x >>>> machines. This was with Apache servers in the proxy setup: one >>>> >>> I'm wondering: where these 32 bit, or 64 bit machines? >>> >> >> amd64. >> >> >>>> I had already tried to debug this situation and Mike Silbersack >>>> helped me with patching the kernel. At that days his patches (that >>>> went into 7.x) helped, but with higher request rate to the Apache, >>>> they seem to be back again. I can try to setup the testbed and >>>> verify if I will still be able to reproduce them. Will it be needed? >>>> >>>> >>> Well, if your machine was indeed 64 bit, I for one would be very >>> interested in knowing if it also appears in 32 bit. >>> >> >> Have no i386 machines to test on, sorry. Moreover, I can not yet >> reproduce the problem on my amd64, but I am continuing experiments. >> > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >