Date: Thu, 3 Apr 2014 16:14:40 -0400 From: John Baldwin <jhb@freebsd.org> To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: Stuck CLOSED sockets / sshd / zombies... Message-ID: <201404031614.40951.jhb@freebsd.org> In-Reply-To: <4B53DEF2407E2EC90A8DDF9D@study64.tdx.co.uk> References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk> <201404031232.16465.jhb@freebsd.org> <4B53DEF2407E2EC90A8DDF9D@study64.tdx.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, April 03, 2014 3:38:39 pm Karl Pielorz wrote: > > --On 3 April 2014 12:32:16 -0400 John Baldwin <jhb@freebsd.org> wrote: > > >> " > >> USER CMD PID FD MOUNT INUM MODE SZ|DV R/W > >> root sshd 4346 8* local stream fffff80002e55c30 <-> > >> fffff80002e552d0 ... > >> root sshd 4344 4* local stream fffff80002e552d0 <-> > >> fffff80002e55c30 " > > > > Right, so it's just blocked on a UNIX domain socket from the parent > > waiting for the parent to tell it to do something. The root issue is the > > parent (as I feared). Is 4344 threaded (procstat -t?) > > " > # procstat -t 4344 > PID TID COMM TDNAME CPU PRI STATE WCHAN > 4344 100068 sshd - 0 120 sleep urdlck > " That's really odd. A single threaded program has no business even trying to grab a lock. Is your sshd even linked against libthr via ldd? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404031614.40951.jhb>