From owner-freebsd-net@FreeBSD.ORG  Sat Jun 28 04:14:57 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 4CCD3106564A
	for <net@freebsd.org>; Sat, 28 Jun 2008 04:14:57 +0000 (UTC)
	(envelope-from silby@silby.com)
Received: from relay03.pair.com (relay03.pair.com [209.68.5.17])
	by mx1.freebsd.org (Postfix) with SMTP id A32258FC17
	for <net@freebsd.org>; Sat, 28 Jun 2008 04:14:56 +0000 (UTC)
	(envelope-from silby@silby.com)
Received: (qmail 99142 invoked from network); 28 Jun 2008 03:48:13 -0000
Received: from unknown (HELO localhost) (unknown)
	by unknown with SMTP; 28 Jun 2008 03:48:13 -0000
X-pair-Authenticated: 209.68.2.70
Date: Fri, 27 Jun 2008 22:48:12 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
In-Reply-To: <5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc>
Message-ID: <20080627224640.J20899@odysseus.silby.com>
References: <486283B0.3060805@transip.nl>
	<5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Ali Niknam <freebsd-net@transip.nl>, 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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jun 2008 04:14:57 -0000


On Thu, 26 Jun 2008, Eygene Ryabinkin wrote:

> 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?

IIRC, the problem we found then had some interesting root causes, but the 
important point was the FreeBSD 7-prerelease was returning a different 
errno than FreeBSD 6 (and before) had been returning, which caused Apache 
to leak the FD.  I wouldn't be at all surprised if there was a switched 
errno in some other error path that's causing similar problems.

-Mike