From owner-freebsd-current@FreeBSD.ORG Tue Sep 19 13:48:20 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBD6216A4B3 for ; Tue, 19 Sep 2006 13:48:20 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7583643D6E for ; Tue, 19 Sep 2006 13:48:19 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 13209 invoked from network); 19 Sep 2006 13:51:25 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 19 Sep 2006 13:51:25 -0000 Message-ID: <450FF522.60909@freebsd.org> Date: Tue, 19 Sep 2006 15:48:18 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Ian FREISLICH References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Connections locking up with today's -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 13:48:20 -0000 Ian FREISLICH wrote: > Hi > > Anyone noticed that today's current has connections jamming like below: > > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp4 0 33028 196.7.162.25.22 196.7.147.230.3569 ESTABLISHED > > Or > > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp4 0 846 41.204.193.40.783 196.7.147.20.4131 LAST_ACK > tcp4 0 2707 41.204.193.40.783 196.7.147.136.3009 LAST_ACK > tcp4 0 650 41.204.193.40.783 196.7.147.18.2159 LAST_ACK > tcp4 0 587 41.204.193.40.783 196.7.147.20.3710 LAST_ACK > tcp4 0 587 41.204.193.40.783 196.7.147.18.2155 LAST_ACK > > It's odd because with the top one, I can still log out and the shell > disappears, except for the sshd process, which if I kill it terminates > the connection. > > In the second case, those LAST_ACK connections have been around for > about 2 hours. > > Heavy (well, not so heavy) traffic seems to trigger this on long > standing connections. For instance, 'tail -f /var/log/spamd.log' > on a busy spamassassin process will do it. Do you have an em(4) interface running at 100Mbit? -- Andre