Stuck CLOSED sockets / sshd / zombies...

Karl Pielorz kpielorz_lst at tdx.co.uk
Mon Apr 7 11:12:12 UTC 2014



--On 04 April 2014 16:13 -0400 John Baldwin <jhb at 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



More information about the freebsd-hackers mailing list