[Top][All Lists]

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

Re: [monit] Problem restarting a process

From: Martin Pala
Subject: Re: [monit] Problem restarting a process
Date: Sat, 30 Aug 2008 23:07:53 +0200


the difference between manual and default automatic mode is very simple and doesn't have any influence on monitoring capabilities. The manual mode just doesn't monitor the service until instructed to do so - when the monitoring is enabled, the functionality is the same.

You can run monit with the -v option to see detailed progress.


On Aug 28, 2008, at 11:18 AM, Arut Selvan wrote:

Hello Folks,
I am using monit version 3.2 on my Redhat 7.3 based system to monitor and restart processes.
when process plum  gets killed by user manually monit doesn't restart it sometimes ( 3 out of 10 times).
However, if I change the mode to active from manual, it seems to restart it always.
Now the problem is when I sent the fix for review someone pointed out that we use manual mode
by default in our project and also in active mode monitor won't monitor for the cpuusage/memusage criteria.
Is that assumption true? Please clarify ?
I would like to know if it is a bug in monit code. My organization would not allow me to upgrade to a newer
version of monit right now, so I need to fix the issue in the current version of monit itself.
Appreciate your suggestions.
check plum with pidfile /opt/cbz/var/run/
        start program = "/etc/init.d/plum start"
        stop program = "/etc/init.d/plum stop"
        cpuusage > 60.0 for 3 cycles restart
        memusage > 35.0 restart
        mode manual
bash-2.05a# monit -V
This is monit version 3.2
Copyright (C) 2000-2003 by Contributors to the monit codebase

Nothing says Labor Day like 500hp of American muscle
Visit today.
To unsubscribe:

reply via email to

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