Hi,
the described problem is fixed in CVS already, we'll release
monit-5.0.3 tomorrow.
Workaround is to temporarily disable timeout and unmonitor statements
in monitrc:
#if <x> restarts within <y> cycles then timeout
#if <...> then unmonitor
Thanks,
Martin
On May 28, 2009, at 11:04 PM, James Le Cuirot wrote:
Hi guys,
I'm not entirely sure how to reproduce this but it's happened a few
times to me today already. If a service times out then Monit aborts
with the following error. Any subsequent attempts to start Monit will
give this error and I cannot successfully start it again until I
delete /var/lib/monit/monit.state.
monit: gc.c:167: gc_event: Assertion
`pthread_mutex_destroy(&(*e)->mutex) == 0' failed.
There's nothing particularly unusual about my setup. I'm running the
64-bit version of Ubuntu Hardy. I'm using Monit 5.0.2, which I built
from source. I have boat loads of experience in compiling from source
so I don't think I messed up there. I'm using M/Monit but I doubt
that's related. I first noticed this when trying the example MySQL
configuration posted on the Monit wiki.
The only other thing that's worth mentioning is that it's a quad core
machine and the system is registering 8 CPUs due to hyperthreading
being enabled by default on Hardy. The error looks concurrency-
related.
Regards,
James
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
