Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Apr 2014 19:51:35 +0400
From:      Lev Serebryakov <lev@FreeBSD.org>
To:        Karl Pielorz <kpielorz_lst@tdx.co.uk>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Stuck CLOSED sockets / sshd / zombies...
Message-ID:  <112395541.20140412195135@serebryakov.spb.ru>
In-Reply-To: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk>
References:  <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <lev@FreeBSD.org>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?112395541.20140412195135>