[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: receiving memory corruption when trying to run monit

From: Jan-Henrik Haukeland
Subject: Re: receiving memory corruption when trying to run monit
Date: Wed, 10 Jan 2007 00:32:42 +0100

Are you using the latest version of monit, that is, 4.8.2?

Best regards
Jan-Henrik Haukeland

On 9. jan. 2007, at 23.35, Adam Greene wrote:

I installed monit from source on CentOS.

-bash-3.00# uname -a
Linux <node name> 2.6.9-42.0.2.EL.xs148xenU #1 SMP Sun Oct 15 08:31:21 EDT 2006 i686 athlon i386 GNU/Linux

If the config file doesn't contain any monitoring checks, it boots up just fine. However, if I quit it, I see this:

-bash-3.00# pwd
-bash-3.00# ls
includes  monitrc
-bash-3.00# monit
Starting monit daemon with http interface at [*:8135]
-bash-3.00# monit quit
monit daemon with pid [30556] killed
*** glibc detected *** double free or corruption (!prev): 0x090e7448 ***

now if I put a basic cron check in the config file, it won't even will fail with this:

-bash-3.00# pwd
-bash-3.00# ls
includes  monitrc
-bash-3.00# monit
Segmentation fault

I've tried recompiling with:
export MALLOC_CHECK_=0

but no luck. I'm totally stumped! Does anyone have any ideas on how to proceed?


ps.  The config file in question:

set daemon     120
set logfile syslog facility log_daemon
set mailserver
set alert      address@hidden
set mail-format { from: address@hidden }
set httpd port 8135

To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]