Re: [monit-dev] gc.c: assertion failed

[Martin Pala]

Hi,

thanks for report, the problem is fixed now.

The issue can happen when unmonitor or timeout action was triggered.

We'll release monit-5.0.3 this week.

Thanks,
Martin


On May 24, 2009, at 8:12 PM, Michael Shigorin wrote:

>         Hello,
> I've been presented with the following bugreport (in Russian[1]):
>
> check file syslogd_bin with path /sbin/syslogd
>         group syslogd
>         include /etc/monitrc.d/templates/rootbin
>
> check file syslog_file with path /var/log/syslog/messages
>         group syslogd
> 	if timestamp > 65 minutes then alert        # Have you seen "--  
> MARK --"?
>         if failed permission 640  then unmonitor
>         if failed uid root        then unmonitor
>         if failed gid adm         then unmonitor
>
> address@hidden monit.d]# monit -Iv
> ...
> 'syslog_file' uid check succeeded [current uid=0]
> 'syslog_file' gid test failed for /var/log/syslog/messages --  
> current gid is 502
> GID failed notification is sent to root at office.etersoft.ru
> Monitoring disabled -- service syslogd
> Monitoring disabled -- service syslog_file
> monit: gc.c:167: gc_event: Assertion `pthread_mutex_destroy(&(*e)- 
> >mutex) == 0' failed.
> Aborted
>
> I asked the person to actually check log file's permissions
> but failed check seems like no real reason to abort for me.
>
> It's 5.0.2 built with gcc-4.4.0.  Are there any additional
> details I should ask him for?
>
> [1] https://bugzilla.altlinux.org/show_bug.cgi?id=20158
>
> --
> ---- WBR, Michael Shigorin <address@hidden>
>  ------ Linux.Kiev http://www.linux.kiev.ua/
>
>
> _______________________________________________
> monit-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/monit-dev