[Top][All Lists]

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

Re: Monit running start program multiple times

From: Martin Pala
Subject: Re: Monit running start program multiple times
Date: Mon, 4 Aug 2014 14:28:36 +0200


the start program waits for the program to start (show up in the process 
table). If the pidfile based monitoring is used, it depends on the pidfile 
content => if pidfile is not updated, Monit won't find the process.

Some process management frameworks (such as Upstart on RHEL 6.x) have problems 
if stop is called and before it finished (even when process is stopped 
already), start is called - then the pidfile is not created/updated. In such 
case it's better to add standalone "restart program" to Monit configuration 
(supported since Monit 5.7), which does atomic restart (from Monit point of 
view) instead of stop+start.


On 01 Aug 2014, at 12:38, Marcus Ilgner <address@hidden> wrote:

> Hi all,
> I'm just getting acquainted with Monit and fighting with some strange
> behaviour while monitoring a running program.
> Running the "start program" command manually, it returns 0 but monit
> always reports "failed to start" in the log file - and also starts the
> program a *lot* of times, spamming the machine.
> Taking a procmatch-based approach, it correctly detects if the app is
> already running, but it also takes a few seconds to change its process
> name - could that be the source of the problem? I already tried
> specifying "with timeout 60" but that didn't help
> All the best
> Marcus
> --
> To unsubscribe:

reply via email to

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