From owner-freebsd-current@FreeBSD.ORG  Tue Sep 19 14:04:41 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 C06D916A881;
	Tue, 19 Sep 2006 14:04:41 +0000 (UTC)
	(envelope-from if@hetzner.co.za)
Received: from hetzner.co.za (office.cpt2.host-h.net [196.7.147.230])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 58C2943D45;
	Tue, 19 Sep 2006 14:04:32 +0000 (GMT)
	(envelope-from if@hetzner.co.za)
Received: from localhost ([127.0.0.1])
	by hetzner.co.za with esmtp (Exim 4.62 (FreeBSD))
	(envelope-from <if@hetzner.co.za>)
	id 1GPgD4-0008mf-Tc; Tue, 19 Sep 2006 16:04:26 +0200
To: Andre Oppermann <andre@freebsd.org>
From: Ian FREISLICH <if@hetzner.co.za>
In-Reply-To: Message from Andre Oppermann <andre@freebsd.org> 
	of "Tue, 19 Sep 2006 15:48:18 +0200." <450FF522.60909@freebsd.org> 
X-Attribution: BOFH
Date: Tue, 19 Sep 2006 16:04:26 +0200
Message-Id: <E1GPgD4-0008mf-Tc@hetzner.co.za>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2006 14:04:42 -0000

Andre Oppermann wrote:
> 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     ESTABLIS
HED
> > 
> > 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?

I should also say, it just jams one or two connections.  Other
connections to the server still function, and I can make new
connections even with the few locked up connections.

Ian

--
Ian Freislich