[Top][All Lists]

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

Re: Monit starting out without monitoring

From: Martin Pala
Subject: Re: Monit starting out without monitoring
Date: Tue, 19 Apr 2016 12:46:47 +0200


the monitoring state is saved persistent across monit restarts - saved to a 
state file. The default state file path is ~/.monit.state, you can customize it 
using "set statefile <path>" statement in monit configuration file. If you need 
to reset the state after each machine reboot, either do "monit monitor all" in 
the monit startup script or place the statefile to some volatile filesystem 
(for example /tmp is often mounted using tmpfs/ramdisk).


> On 19 Apr 2016, at 09:22, Ani A <address@hidden> wrote:
> Hello,
> I built Monit 5.17.1 version from source, and running on Ubuntu 14.04,
> My config is like:
> set daemon 30
>  with start delay 90
> set httpd port 2812 and
>    use address localhost
>    allow localhost
>    allow admin:passwd
> check process myproc with pidfile /var/run/
>   start program = "/etc/init.d/myproc start"
>   stop program = "/etc/init.d/myproc stop"
>   if 4 restarts within 10 cycles then exec "/opt/my/"
> The script is invoked if the process restarts 4 times in 300 
> seconds,
> In the script, I also do "monit unmonitor all".
> After the process halts, if I manually try to bring up service, monit
> will start out
> with monitoring disabled!
> How can I force monit to start with monitoring enabled ?
> I tried to add this in my init.d service script, but I will have to
> wait for 90 seconds
> for the CLI to get enabled!
> --
> Regards,
> A. Aniruddha
> --
> To unsubscribe:

reply via email to

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