Stuck CLOSED sockets / sshd / zombies...
John Baldwin
jhb at freebsd.org
Thu Apr 3 20:17:14 UTC 2014
On Thursday, April 03, 2014 3:38:39 pm Karl Pielorz wrote:
>
> --On 3 April 2014 12:32:16 -0400 John Baldwin <jhb at 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
More information about the freebsd-hackers
mailing list