From owner-freebsd-stable@FreeBSD.ORG Wed Mar 19 11:56:19 2014 Return-Path: Delivered-To: freebsd-stable@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 912A1424 for ; Wed, 19 Mar 2014 11:56:19 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [67.212.89.78]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5AC0BBB0 for ; Wed, 19 Mar 2014 11:56:19 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) by mail.bsdinfo.com.br (Postfix) with ESMTP id 80388139C4 for ; Wed, 19 Mar 2014 11:52:11 -0300 (BRT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bsdinfo.com.br; h=content-type:content-type:in-reply-to:references:subject :subject:to:mime-version:user-agent:from:from:date:date :message-id; s=dkim; t=1395240730; x=1396104731; bh=mhMor5GrLXWf bMrOzj//e9GkxNvlbXptSU3RmZJ2dpw=; b=O/2da3MtrhmtH8V6YKl98BSGjAJg AomC6quVWvpIumq1ygGpWjQcaCMoadXt5rBTqNHK7JW+eusy2d8RrPr+Iey9mBjf 9tabv4WzmiJxMipl/2C7G9Ae8F3vkTntVO50BhOskWN5B9OhPA9Azn7EPye6u4iB 9GXipQ/5Gn4Mdiw= X-Virus-Scanned: amavisd-new at mail.bsdinfo.com.br Received: from mail.bsdinfo.com.br ([127.0.0.1]) by mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyINby5-IurJ for ; Wed, 19 Mar 2014 11:52:10 -0300 (BRT) Received: from MacBook-de-Gondim-2.local (unknown [186.193.54.69]) by mail.bsdinfo.com.br (Postfix) with ESMTPSA id C5C9C139C3 for ; Wed, 19 Mar 2014 11:52:09 -0300 (BRT) Message-ID: <53298445.90706@bsdinfo.com.br> Date: Wed, 19 Mar 2014 08:49:25 -0300 From: Marcelo Gondim User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: FreeBSD Stable Mailing List Subject: Re: sshd with zombie process on FreeBSD 10.0-STABLE References: <53016D97.5030909@bsdinfo.com.br> <53066B59.5000709@yandex.ru> <531A6C66.2010101@bsdinfo.com.br> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 11:56:19 -0000 Em 11/03/14 05:45, Alexander Yerenkow escreveu: > 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 :) Changed to shand the problem happened again. Definitely something changed in sshd since version 10.0that is causing this problem. My server never had zombie processes and now they sprout out of nowhere. :( > > > 2014-03-08 3:03 GMT+02:00 Marcelo Gondim >: > > Em 20/02/14 17:53, Andrey V. Elsukov escreveu: > > On 17.02.2014 06:01, Marcelo Gondim wrote: > > Hi all, > > I have noticed zombie processes on the system after a few lost > connections on ssh. > > # ps afx > [...] > 8045 - Is 0:00.01 sshd: unknown [priv] (sshd) > 8046 - Z 0:00.01 > 8054 - IW 0:00.00 sshd: unknown [pam] (sshd) > 28146 - Is 0:00.01 sshd: unknown [priv] (sshd) > 28147 - Z 0:00.01 > 28155 - IW 0:00.00 sshd: unknown [pam] (sshd) > 43320 - Is 0:00.01 sshd: unknown [priv] (sshd) > 43321 - Z 0:00.01 > 43322 - IW 0:00.00 sshd: unknown [pam] (sshd) > 73413 - Is 0:00.01 sshd: unknown [priv] (sshd) > 73414 - Z 0:00.01 > 73430 - IW 0:00.00 sshd: unknown [pam] (sshd) > [...] > > Processes do not die with kill-9. > Anyone else noticed this? > > Hi, > > I use autossh and usually my system has several tens of sshd's > zombies > after few days uptime. > > 11.0-CURRENT #6 r262183 > > New system update and the problem with zombie sshd processes continue. > I noticed that this happens more often when the system has many > remote access via ssh. This problem has been happening to me since > the FreeBSD 10.0R. > > # uname -a > FreeBSD bart.xxxxx.com.br 10.0-STABLE > FreeBSD 10.0-STABLE #5 r262657: Tue Mar 4 14:53:08 BRT 2014 > root@bart.xxxxx.com.br:/usr/obj/usr/src/sys/GONDIM10 amd64 >