Re: about monit.conf

[Martin Pala]

Can you try monit 4.9? It should fix the issue.

Thanks,
Martin

Atsushi Tamae wrote:
> Hello,
> 
> I know about monit did not know about previous status.
> But I can not understatnd why monit can restart stopped service,
> then mail us " Monit alert tacacs at Fri, 02 Mar 2007 18:18:23 +0900 on 
> test.test.jp: 'tacacs' failed to start."
> But tacacs process successfully started. I want to know why monit report to 
> "fail to start".
> Please let me know.
> 
> Thanks
> Atsushi Tamae
> 
>               
> 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