Re: [monit] Subject: Disabling timing out to "not monitored"

[David Bristow]

If we're pretty sure that we don't have the "if <x> restarts within
<y> cycles then timeout" setting, and we grepped the logs to make sure
that the service hadn't been stopped, then I am not sure how this
could have happened, do you agree?

On Thu, Jan 28, 2010 at 3:15 PM, Martin Pala <address@hidden> wrote:
> Yes, both options are correct.
>
> When some user requests stop/unmonitor, it is logged in monit log => you can 
> find when it happened.
>
> The second option (timeout statement) is not enabled automatically - it 
> requires configuration: "if <x> restarts within <y> cycles then timeout" ... 
> if you have not added it to the service configuration, monit won't timeout 
> the service on restart failure.
>
> Regards,
> Martin
>
>
> On Jan 28, 2010, at 7:09 PM, David Bristow wrote:
>
>> We are using monit to make sure that certain services are running at all 
>> times.
>>
>> We came across a situation where a service being monitored by monit
>> gave the monit status: "not monitored". From our understanding there
>> are two ways for this to occur:
>> 1) Someone stops the service or "unmonitors" the service
>> 2) monit has difficulty starting a service, or keeping a service
>> running; IE: it tries a number of times and then "gives up" and stops
>> monitoring the service
>>
>> Can someone please confirm our understanding, and let me know how to
>> disable option #2. (timing out to state of "not monitored")
>>
>> Thank you very much for your help.
>>
>> --
>> David Bristow <address@hidden>
>>
>>
>> --
>> To unsubscribe:
>> http://lists.nongnu.org/mailman/listinfo/monit-general
>
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general
>



-- 
David Bristow <address@hidden>