Date: Mon, 07 Apr 2014 12:12:03 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Stuck CLOSED sockets / sshd / zombies... Message-ID: <2C5B099DE2229F0E8D82D8C8@Mail-PC.tdx.co.uk> In-Reply-To: <201404041613.09808.jhb@freebsd.org> References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk> <201404031614.40951.jhb@freebsd.org> <18B08A7E8585B0C4A89A05E6@study64.tdx.co.uk> <201404041613.09808.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 04 April 2014 16:13 -0400 John Baldwin <jhb@freebsd.org> wrote: > Ugh, ok. Is this easy to reproduce? Ok, yes - I can reproduce this now. I scanned the new host I setup with our security scanning software. This generated a number of sshd caught in 'urdlck' - and a large number of sockets that end up as 'CLOSE_WAIT' I'm guessing given time these will finally move to 'CLOSED' (it was scanned hours ago and there's still 50+ in CLOSE_WAIT state). As I said originally this can't be the only cause - but it is a cause. So now I can reproduce it - what next? Regards, -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2C5B099DE2229F0E8D82D8C8>