Re: about monit.conf

[Kenneth]

Yes, that's why I have cron job to monitor monit and
restart it if necessary every day.

----- Original Message ----- 
From: "Atsushi Tamae" <address@hidden>
To: "This is the general mailing list for monit" <address@hidden>
Sent: Monday, March 05, 2007 9:59 AM
Subject: Re: about monit.conf


> Hello,
>
> The reason why we want to run monit as cron was
> I worried about monit daemon suddenly stop.
> To use monit for monitoring specific service did not want
> to stop. But we use monit as daemon mode, we have to care
> about monit daemon process instead of specific daemon.
>
> Somebody think about that ?
>
> Thanks
> Atsushi Tamae
>
> hans wrote:
> > I am still confused about running monit from crond.
> > If run monit every 5 minutes why no to change the poll time to 5
> > minutes and run it as demon.
> > Run monit from crond is not very cool because you loose a lot of
> > functions of monit that make monit great.
> > Please, someone tell me what its the goal of running monit from crond.
> > Regards Hans.
> >
> > On 3/2/07, Martin Pala <address@hidden> wrote:
> > > Also note that in this mode the "if 5 restarts within 5 cycles then
> > > timeout" has no effect for the same reason - it will work only in daemon
> > > mode.
> > >
> > > Martin
> > >
> > >
> > > Martin Pala wrote:
> > > > When you call monit from cron, then it will check the current services
> > > > state, start the failed processes, send the alarm and gracefuly exit.
> > > > When monit isn't running as daemon, it doesn't keep the state for the
> > > > previous cycle.
> > > >
> > > > When you want monit to send email for both events (failure in one 
> > > > cycle
> > > > and recovery in next cycle) then you should run monit in daemon mode
> > > > rather then from cron.
> > > >
> > > >
> > > > Martin
> > > >
> > > >
> > > >
> > > > Atsushi Tamae wrote:
> > > >> Hello,
> > > >>
> > > >> I install monit to redhat linux ES 4 with 
> > > >> monit-4.9-1.el4.rf.i386.rpm.
> > > >> %monit -V
> > > >> This is monit version 4.9
> > > >> Copyright (C) 2000-2007 by the monit project group. All Rights
> > > Reserved.
> > > >>
> > > >> And configured for monit as like follows:
> > > >>
> > > >> #check snmptrapd
> > > >> check process snmptrapd with pidfile /var/run/snmptrapd.pid
> > > >>    start program = "/etc/init.d/snmptrapd start"
> > > >>    stop program = "/etc/init.d/snmptrapd stop"
> > > >>    if failed port 162 type udp then restart
> > > >>    if 5 restarts within 5 cycles then timeout
> > > >> #check radiusd
> > > >> check process radiusd with pidfile /var/run/radiusd/radiusd.pid
> > > >>    start program = "/etc/init.d/radiusd start"
> > > >>    stop program = "/etc/init.d/radiusd stop"
> > > >>    if 5 restarts within 5 cycles then timeout
> > > >> #check tacacs server
> > > >> check process tacacs with pidfile /var/run/tac_plus.pid
> > > >>   start program = "/etc/init.d/tacacs start"
> > > >>   stop  program = "/etc/init.d/tacacs stop"
> > > >>   if 5 restarts within 5 cycles then timeout
> > > >>
> > > >>
> > > >> And I confiured to run monit in crontab like follows:
> > > >> */5     *       *       *       *       root monit validate
> > > >>
> > > >> And I shutdown some process like snmptrapd, to test monit.
> > > >> But I found monit mail as follows:
> > > >>
> > > >> 'snmptrapd' process is not running
> > > >> 'snmptrapd' trying to restart
> > > >> 'snmptrapd' start: /etc/init.d/snmptrapd
> > > >> 'snmptrapd' failed to start
> > > >>
> > > >> But snmpdtrapd process is already up when I saw this mail.
> > > >> Please let me know what should I do if I want to recieve mail
> > > result like 'snmptrapd' success to start.
> > > >> I mean not 'snmptrapd' failed to start.
> > > >>
> > > >> Thanks
> > > >> Atsushi Tamae
> > > >>
> > > >>
> > > >> --
> > > >> To unsubscribe:
> > > >> http://lists.nongnu.org/mailman/listinfo/monit-general
> > > >
> > > >
> > > >
> > > >
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general