From owner-freebsd-net@FreeBSD.ORG Thu Nov 1 18:07:11 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7F5116A4D1 for ; Thu, 1 Nov 2007 18:07:11 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 7D47113C4AA for ; Thu, 1 Nov 2007 18:07:11 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id CB0761B10EEE; Thu, 1 Nov 2007 15:30:28 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 Received: from [10.1.1.3] (unknown [192.168.25.14]) by blah.sun-fish.com (Postfix) with ESMTP id 439501B10EEB for ; Thu, 1 Nov 2007 15:30:26 +0100 (CET) Message-ID: <4729E300.3060902@moneybookers.com> Date: Thu, 01 Nov 2007 16:30:24 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4658/Thu Nov 1 13:50:49 2007 on blah.cmotd.com X-Virus-Status: Clean Subject: FIN_WAIT_2 on FreeBSD 6.2-STABLE 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: Thu, 01 Nov 2007 18:07:11 -0000 Hi, I'm seeing strange problem with sockets in state FIN_WAIT_2. netstat -n |grep FIN_WAIT_2|wc -l shows 12234 lines, Those sockets never die and just grow more and more, when finally today I saw this in logs: postfix/smtp[6968]: connect to gmail-smtp-in.l.google.com[66.249.91.27]: Can't assign requested address (port 25) and this happens not only to postfix, but all clients & servers on this host. Even things that use only local connections throw out: connect: Can't assign requested address Shorty after I moved away almost everything from this server, there was a spontaneous reboot. I know what apache and some buggy clients can cause sockets to stay in state FIN_WAIT_2, but they should disappear after some timeout. Is there a point to go for 6.3-prerelease, or nothing like this was reported, respectively fixed between may 2007 and today? Migration to RELENG_7 is not option for me at this point as this host serves something like 6mbps of http traffic, and there is a report that sometimes hosts running releng_7 can't be reached .. 6.2-STABLE from May 9 - amd64 Thanks in advance.