From owner-freebsd-stable@FreeBSD.ORG  Tue Mar 18 18:25:07 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 47683B60
 for <freebsd-stable@freebsd.org>; Tue, 18 Mar 2014 18:25:07 +0000 (UTC)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id D70F9A37
 for <freebsd-stable@freebsd.org>; Tue, 18 Mar 2014 18:25:06 +0000 (UTC)
Received: from study64.tdx.co.uk (study64.tdx.co.uk [62.13.130.231])
 (authenticated bits=0)
 by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s2IIOtbg023412
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Tue, 18 Mar 2014 18:24:56 GMT
Date: Tue, 18 Mar 2014 18:24:55 +0000
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: Alexander Yerenkow <yerenkow@gmail.com>,
 Marcelo Gondim <gondim@bsdinfo.com.br>
Subject: Re: sshd with zombie process on FreeBSD 10.0-STABLE
Message-ID: <93D37B2C8EC71EC12EE855D5@study64.tdx.co.uk>
In-Reply-To: <CAPJF9wnVOYjTXB0A1wyzwvCj-Tvx_u2uYLW72-wDuz-QZpwT4w@mail.gmail.com>
References: <53016D97.5030909@bsdinfo.com.br> <53066B59.5000709@yandex.ru>
 <531A6C66.2010101@bsdinfo.com.br>
 <CAPJF9wnVOYjTXB0A1wyzwvCj-Tvx_u2uYLW72-wDuz-QZpwT4w@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Mar 2014 18:25:07 -0000



--On 11 March 2014 10:45:18 +0200 Alexander Yerenkow <yerenkow@gmail.com> 
wrote:

> Could you try to change shell to simple "sh" and see if this helps?
> This could be due to non-atomic work with history file when multiple
> clients log off, causing csh produce large broken history files.
> This is not 100% your case, but you could at least try :)

Hi,

I also have a system that has this problem:

FreeBSD 10.0-STABLE FreeBSD 10.0-STABLE #0 r261289M: Thu Jan 30 13:33:35 
UTC 2014     xxxxxxxxx:/usr/src/sys/amd64/compile/GENERIC  amd64

The sshd processes lock in 'urdlck' - I set this box up a while ago as 
10.0-R - installed subversion, and updated to 10.0-S (r261289). It's been 
left 40+ days since then.

Very little usage - but I have over 120 'stuck' sshd daemons.

I initially posted to the freebsd-xen list (this box is running under Xen) 
as we've a number of other FBSD10 boxes that don't have the issue (but 
these get more usage, and frequent restarts). It now looks like it's not a 
Xen issue - but a FBSD10 issue...

I've left the machine 'as-is' with all these zombies / stuck sshd's - if 
anyone wants me to run anything against / on it?

I can't see that this has been fixed in a newer -stable?

Cheers,

-Karl