Hello Viktor, the next monit version (5.18) should fix the problem:
--8<-- Fixed: Issue #350: If the "check program" used a custom schedule (based on "every" statement), the exit value evaluation and check for program timeout was deferred until the next cycle, which matched the schedule. Monit now collects the exit value ASAP (i.e. next cycle) and kills the program if timed out. --8<-- Best regards, Martin > On 20 May 2016, at 00:38, SZÉPE Viktor <[email protected]> wrote: > > Hello! > > I am monitoring a server integrity script, and it is: > >> Program 'network_hop' Status failed > > It runs every 33 cycles. > Is there a *one-step* way to get it out of failed status ASAP? > > The only thing I've found is > monit unmonitor network_hop > monit monitor network_hop > > Thank you! > > > > SZÉPE Viktor > -- > +36-20-4242498 [email protected] skype: szepe.viktor > Budapest, III. kerület > > > > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
