Re: Deadlock problems with 'kill PID' on CURRENT

From: Martin Blapp <mb_at_imp.ch>
Date: Mon, 15 Nov 2004 18:03:36 +0100 (CET)
Hi,

> I had this problem too BTW, but it didn't prevent DDB.  Once named or
> rndc got stuck, trying to kill them was Really Bad(TM).  Both use
> libpthread.  The programs were stuck in "runnable" state according to
> CTRL-T (siginfo).
>
> No, I haven't looked closer.  That system was built about when the last
> round of libpthread turmoil was happening.

Now if you say it. I had to kill named manually since it has lost his
ARGV:

Instead of

bind        5068  0.0  1.4 30108 28440  ??  Ss   11:51AM  14:54.01 /usr/sbin/named -u bind -t /var/named

I just had this at the time the box crashed:

bind        5068  0.0  1.4 30108 28440  ??  Ss   11:51AM  14:54.01 [/usr/sbin/named]

or

bind        5068  0.0  1.4 30108 28440  ??  Ss   11:51AM  14:54.01 [named]

after recovery from the crash, now everything is ok again.

Martin
Received on Mon Nov 15 2004 - 16:03:58 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:22 UTC