Date: Wed, 19 Mar 2014 09:01:48 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Marcelo Gondim <gondim@bsdinfo.com.br> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: sshd with zombie process on FreeBSD 10.0-STABLE - workaround Message-ID: <CAN6yY1uucfkdXxkCF30w1Q9vffRpDLxM90Sz1XVbdn5W69vQMg@mail.gmail.com> In-Reply-To: <532994EA.9090300@bsdinfo.com.br> References: <53016D97.5030909@bsdinfo.com.br> <53066B59.5000709@yandex.ru> <531A6C66.2010101@bsdinfo.com.br> <CAPJF9wnVOYjTXB0A1wyzwvCj-Tvx_u2uYLW72-wDuz-QZpwT4w@mail.gmail.com> <53298445.90706@bsdinfo.com.br> <532994EA.9090300@bsdinfo.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 19, 2014 at 6:00 AM, Marcelo Gondim <gondim@bsdinfo.com.br>wrote:
> Hi all,
>
> While the solution does not appear, did the script below and put it in
> crontab to automatically delete zombie sshd processes.
>
> the_walking_dead.sh:
>
> #!/bin/sh
> kill -9 `ps afx|grep sshd|grep unknown|awk '{print $1}'`
>
>
> Put this in /etc/crontab:
>
> 00 1 * * * root the_walking_dead.sh
>
>
If 'kill -9' works, the process is not really a zombie. It simply still has
a socket open and is waiting for it to be closed before exiting.
You might takes a look at network sockets with sockstat(1) and see if you
can get any indication of why these sockets are not being closed. It may be
that the issue is not sshd but some other issue in the OS leaving sockets
open.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uucfkdXxkCF30w1Q9vffRpDLxM90Sz1XVbdn5W69vQMg>