Re: monit 5.5 check program

[Jan-Henrik Haukeland]

Because Monit runs in cycles, program timeout is more a hint than an absolute 
value. The program will be killed if it is still running when Monit does the 
check again > 900 seconds later, though it might not be exactly 900 seconds on 
the mark. This depends on your poll-cycle length.

During the time when the program stops and Monit collects its status the 
program will be in a defunct state, but as soon as Monit collects the status 
the program is removed from the process table an no longer in a defunct state. 
This, and how Monit checks a program status is described more in detail here 
http://mmonit.com/monit/documentation/monit.html#program_status_testing


On Jun 8, 2013, at 12:15 AM, Amit Khivesara <address@hidden> wrote:

> Hi,
> 
> I want a long running program to timeout in monit.
> 
> check program try with path "all.sh"
> 
> works and the program is killed in 600 seconds.
> 
> Now with monit 5.5 if I use the syntax:
> 
> check program try with path "all.sh"  with timeout 900 seconds
> 
> Then monit does not kill the program and the process ends up being defunct.
> 
> Using monit -v to print out the service list, indicates the timeout of 900 
> seconds has been accepted.
> I tried various syntax but that did not seem to help.
> 
> Anyone seen this issue?
> 
> 
> -- 
> khivi
> 
> address@hidden
> +1 646 233 3549 (office)
> khivi4304 (skype)
> 
> 
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general