[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "for X cycles" has no effect
From: |
Martin Pala |
Subject: |
Re: "for X cycles" has no effect |
Date: |
Sat, 22 Oct 2016 11:29:49 +0200 |
The action is executed on state change only. If you need to execute it each
cycle the error remains, you can use the repeat option ... the "EXEC" action
description in monit manual:
https://mmonit.com/monit/documentation/monit.html#ACTION
> On 21 Oct 2016, at 00:21, address@hidden wrote:
>
> When I disable logging and change the CPU test to:
>
> "if cpu > 1% for 3 cycles then exec "/usr/bin/logger 'cpu usage exceeded 1%'"
>
> I get the log message after it fails 3 consecutive times. If it then fails a
> 4th consecutive time, there is no log message. There is not another log
> message until the first time it fails after it succeeds, even though it has
> not failed 3 consecutive times at that point.
>
> Is this the expected behavior with Monit 5.19.0?
>
>
>
>
>
- Re: "for X cycles" has no effect, (continued)
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/07
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/10
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/13
- Re: "for X cycles" has no effect, Martin Pala, 2016/10/17
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/17
- Re: "for X cycles" has no effect, Martin Pala, 2016/10/17
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/18
- Re: "for X cycles" has no effect, Martin Pala, 2016/10/19
Re: "for X cycles" has no effect, jobhunts02, 2016/10/20
- Re: "for X cycles" has no effect,
Martin Pala <=