Re: restart failed

[Martin Pala]

The behavior is fixed now (in cvs) ... monit will retry the restart in 
next cycle until restart count treshold is reached even in the case that 
the stop method failed.

In any case, monit already sends the error notification in the case that 
the start/stop method failed - the event type is 'exec', thus when you 
have not omited the exec event type from the alert definition, you 
should get something like:

--8<--
Execution failed Service slapd

        Date:   Fri, 12 Aug 2005 23:48:23 +0200
        Action: alert
        Host:   unicorn

Your faithful employee,
monit

'slapd' failed to stop
--8<--


Martin



Pavel Urban wrote:
> Hello,
>
> we have separated 'alert' and 'timeout' notifications and thess lines in 
> monit.conf
>
> check process mta-dispatcher with pidfile 
> /usr/iplanet/mta-in1/msg-mta-in1/config/pidfile.imta_dispatch
>   start program  "/usr/iplanet/mta-in1/msg-mta-in1/imsimta start 
> dispatcher"
>   stop program  "/usr/iplanet/mta-in1/msg-mta-in1/imsimta stop dispatcher"
>   if 5 restarts within 5 cycles then timeout
>   if failed host 192.168.10.12 port 25 protocol smtp then restart
>
> It work ok, but today we've noticed that 'stop' method failed - and 
> isn't tried again. It is probably normal. BUT - no timeout occures and 
> therefore no 'timeout' notifications are sent, while the service is 
> effectively not running. Can this be accomplished somehow?
>
> Thanks!