[Top][All Lists]

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

Re: [monit] monit fails mysteriously on refresh after upgrade from Debia

From: Martin Pala
Subject: Re: [monit] monit fails mysteriously on refresh after upgrade from Debian etch to lenny
Date: Thu, 26 Feb 2009 22:30:47 +0100
User-agent: Thunderbird (X11/20090105)

Jenny Hopkins wrote:
2009/2/25 Martin Pala <address@hidden>:
To fix the problem you will need to recompile:

1.) get the source here:

2.) install bison, flex, libssl-dev

3.) untar monit source distribution

4.) compile:


Then the "make install" can deploy the monit binary to /usr/local/bin or you
can copy it wherever you want. I think debian package tweaks the
configuration file name ... the default for monit is monitrc


What I hope willl be a final question about this!
A friend has grabbed the patch from cvs for the divide by 0 memory
bug, and compiled it into the current debian lenny package for me.
This seems to have eliminated the problem, and i have monit running
once again :-)

However, as soon as I try and actually add any processes to monitor
into my monitrc file, I get an error about process engines.
I note that
 Use process engine = False
is set.
Please could you tell me if to get this value to True, it has to be
part of the compile, or a line i would set in a config file somewhere?


there could be two reasons:

1.) (less likely) monit was compiled without resource monitoring support like this:
./configure --without-resource

2.) (more likely) the initialization of resource monitoring failed ... some platforms (including linux) require root privileges to be able to for example check per-process memory usage. Monit will continue, but disables the resource monitoring which is stated by "Use process engine = False"

=> are you running monit as root or non-root?

If you'll start monit with the -vI option, you can see whether the resource monitoring initialization failed (it can be displayed ... the message will apear most probably before the output with the configuration near the monit startup line or bellow the configuration output and will most probably look like this:

system statistic error -- cannot initialize the process tree => process resource monitoring disabled


reply via email to

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