Re: monit deadlocks

[Jan-Henrik Haukeland]

Which version of monit are you using? Earlier 4.x version (or was it  
3.x?) had some problems with thread locking in some special cases. If  
you are not using the latest 4.6 release try to upgrade to this  
version and see if that solve the problem. If not, could you please  
provide us with a longer trace (the stack address is not much help)  
and maybe elaborate more around the problem (log output) and provide  
us with your monitrc file.

Regards


On 19. okt. 2005, at 20.00, Eli Yukelzon wrote:

> Good day.
>
> I've been using monit for administating my server for quite a while,
> and i've been very pleased with it's performance.
> Lately though I've came across a reoccuring event which will probably
> cause me to switch away from using monit...
> Monit daemon get's stuck. It enters some deadlock, according to  
> strace:
>
> # strace -f -F -p 21284
> Process 21284 attached - interrupt to quit
> futex(0xb7e42800, FUTEX_WAIT, 2, NULL <unfinished ...>
> Process 21284 detached
> # monit summary
> monit: cannot read status from the monit daemon
>
> after killall -9 monit
> it restarts from inittab just fine.
> the problem is - becuase of this deadlock, it stops monitoring the  
> services!
>
> Any ideas?
>
> --
> 2B OR NOT 2B = FF
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general

--
Jan-Henrik Haukeland
Mobil +47 97141255