From owner-freebsd-current@FreeBSD.ORG  Tue Sep 19 13:37:11 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 2CF5B16A415
	for <freebsd-current@freebsd.org>; Tue, 19 Sep 2006 13:37:11 +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 B58C043D45
	for <freebsd-current@freebsd.org>; Tue, 19 Sep 2006 13:37:07 +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 1GPfma-0008hC-VG
	for freebsd-current@freebsd.org; Tue, 19 Sep 2006 15:37:04 +0200
To: freebsd-current@freebsd.org
From: Ian FREISLICH <if@hetzner.co.za>
X-Attribution: BOFH
Date: Tue, 19 Sep 2006 15:37:04 +0200
Message-Id: <E1GPfma-0008hC-VG@hetzner.co.za>
Subject: 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 13:37:11 -0000

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.

Ian

--
Ian Freislich