Re: AssertException: at xmalloc.c:110 aborting..

[Jan-Henrik Haukeland]

It's probably easier to try and reproduce the exception, but just in  
case, could you allow monit to dump core (e.g. ulimit -c 1000000)  
load the core file in gdb and execute bt to get the backtrace and  
send it to us?

On 31. aug. 2005, at 23.33, Chris McKenzie wrote:

> Hi everyone.
>
> I've been playing with monit for a bit now, and have it monitoring  
> a perl based daemon I wrote. I've got a monit rc for that process  
> that alos performs a file check on the daemon's config file for  
> changes since the last poll, and restarts the process.
>
> What I'm finding is monit will restart the process fine, but throws  
> a fatal exception and never recovers as a result.
>
> I'm using Monit 4.5.1 for Linux (RedHat Enterprise 3.0), after the  
> file change occurs (which I perform manually) monit will attempt  
> the process restart and exit with dump the following:
>
> AssertException: at xmalloc.c:110 aborting..
>
> Here's the log:
>
> Aug 31 11:50:16 chrisclub monit[19298]: Starting monit HTTP server  
> at [localhost:2812]
> Aug 31 11:50:16 chrisclub monit[19298]: monit HTTP server started
> Aug 31 11:50:16 chrisclub monit: monit startup succeeded
> Aug 31 11:52:16 chrisclub monit[19298]: 'proc1_updater_config'  
> checksum was changed for /etc/proc1/config
> Aug 31 11:52:16 chrisclub monit[19298]: 'proc1_updater_config'  
> trying to restart
> Aug 31 11:52:16 chrisclub monit[19298]: 'proc1' stop: /etc/init.d/ 
> proc1
> Aug 31 11:52:17 chrisclub proc1: proc1.pl shutdown succeeded
> Aug 31 11:52:18 chrisclub monit[19298]: 'proc1' start: /etc/init.d/ 
> proc1
> Aug 31 11:52:18 chrisclub monit[19298]: AssertException: at  
> xmalloc.c:110 aborting..
> Aug 31 11:52:19 chrisclub proc1: proc1.pl startup succeeded
>
> Here's my rc entry:
>
> check process proc1
>   with pidfile /var/run/proc1.pid
>   start program = "/etc/init.d/proc1 start"
>   stop  program = "/etc/init.d/proc1 stop"
>   if 3 restarts within 3 cycles then timeout
>   depends on proc1_updater_config
>
> check file proc1_updater_config path /etc/proc1/config
>   if changed sha1 checksum
>      then restart
>
> I've also tried setting the check file to exec instead of restart  
> for "/etc/init.d/proc1 restart" with no luck.
>
> If I remove the file check and test killing proc1, monit will  
> restart it fine. With the file check, it dies.
>
> Any ideas or work arounds?! Thanks!
>
>
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general

--
Jan-Henrik Haukeland
Mobil +47 97141255