From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 2 15:58:21 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 6DE23D80 for ; Wed, 2 Apr 2014 15:58:21 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45C0D262 for ; Wed, 2 Apr 2014 15:58:21 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CAD1FB924; Wed, 2 Apr 2014 11:58:19 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: Stuck CLOSED sockets / sshd / zombies... Date: Wed, 2 Apr 2014 11:30:39 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk> In-Reply-To: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201404021130.39478.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 02 Apr 2014 11:58:19 -0400 (EDT) Cc: Karl Pielorz X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2014 15:58:21 -0000 On Wednesday, April 02, 2014 10:30:06 am Karl Pielorz wrote: > > Hi All, > > This issue started in -xen (subject: *Stuck sshd in urdlck), moved to > -stable (subject: sshd with zombie process on FreeBSD 10.0-STABLE), and > -net (subject: Server sockets staying in CLOSED for extended), but seems to > have died a death in all of them. > > It's affecting a number of people - predominately with sshd. > > Does anyone know how I can troubleshoot this further, what the cause / fix > is, or if it's already actually fixed? > > " > # ps ax | grep 4344 > ps axl | grep 4344 > 0 4344 895 0 20 0 84868 6944 urdlck Is - 0:00.01 sshd: unknown > [priv] (sshd) Can you get 'procstat -k 4344' to see where this process is stuck? > 22 4345 4344 0 20 0 0 0 - Z - 0:00.00 > 0 4346 4344 0 21 0 84868 6952 sbwait I - 0:00.00 sshd: unknown > [pam] (sshd) 'procstat -f' and 'procstat -k' for this process might also be useful. -- John Baldwin