Re: [monit] monitoring status not monitored

[David Bristow]

We're not using that timeout setting.

On Thu, Jan 14, 2010 at 1:39 AM, Martin Pala <address@hidden> wrote:
> Yes, the "timeout" statement can disable monitoring in case of too many 
> restart errors:
>
>  if <x> restarts within <y> cycles then timeout
>
> If you need to continue monitoring regardless of restart failures, just 
> remove this statement from service configuration.
>
> Regards,
> Martin
>
>
> On Jan 13, 2010, at 11:34 PM, David Bristow wrote:
>
>> A while ago, we had a service in the following state:
>>
>> Process 'backgroundrb'
>> status                            not monitored
>> monitoring status                 not monitored
>> data collected                    Fri Nov 13 03:03:43 2009
>>
>> We don't think the service had been stopped (monit stop backgroundrb).
>> Is there any situation where monit would get into this state, maybe
>> after trying to restart backgroundrb too many times?
>>
>> --
>> 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>