From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 12 15:52:20 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 239BEF71 for ; Sat, 12 Apr 2014 15:52:20 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id DD31014A2 for ; Sat, 12 Apr 2014 15:52:19 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:38fe:bc98:65e7:fb6b]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 342514AC1C; Sat, 12 Apr 2014 19:52:12 +0400 (MSK) Date: Sat, 12 Apr 2014 19:51:35 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <112395541.20140412195135@serebryakov.spb.ru> To: Karl Pielorz Subject: Re: Stuck CLOSED sockets / sshd / zombies... In-Reply-To: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk> References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2014 15:52:20 -0000 Hello, Karl. You wrote 2 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2014 =D0=B3., 18:30:06: KP> It's affecting a number of people - predominately with sshd. I've got problem like this with "transmission-daemon" from ports today. "netstat" shows 300+ CLOSED tcp sockets for more than hour, kernel complains about overflowed accept queue, and I was not able to kill "transmission-daemon", even reboot process doesn't help (it stuck for more than hour, again, and then I used power switch, what led to destruction of all mu UFS2 SUJ filesystems, which is different story. But, again, it started from stuck network daemon and 300+ CLOSED tcp4/tcp6 sockets. So, maybe, it is not sshd-specific. I'm using 10-STABLE r263965. --=20 // Black Lion AKA Lev Serebryakov