monit checks the service in intervals given by the "set daemon <x>" settings. If the interval between checks is long or the check is blocked by some service timeout/action, then the interval can be longer.
Please can you check the "set daemon" settings and run monit in debug mode?:
1.) stop monit
2.) monit -vI
On 8 Mar 2019, at 16:49, Fant, Andrew (NIH/NIDA) [E] <address@hidden
-- To unsubscribe:https://lists.nongnu.org/mailman/listinfo/monit-general I have a small monitoring setup with m/monit 3.7.2, using monit 5.25.2 as the agent. There are a couple of systems that I cannot install monit on that I still need to be aware of any downtime, so I have added them as ping checks in the monitrc on the host where I installed m/monit. Yesterday, one of those remote systems went down, but monit and m/monit didn’t report an alert for it and still have its status as OK. Using anonymized information, the entry in the monitrc on host1 is: CHECK HOST host2_ping with ADDRESS 192.168.1.2 IF FAILED ping THEN ALERT And from the command line on host1: host1% monit status host2_ping Monit 5.25.2 uptime: 48d 19h 8m monitoring status Monitored data collected Fri, 08 Mar 2019 10:41:33 Clearly there is a disconnect between the OS-provided ping utility and what monit is seeing. I’m sure that it’s probably a simple error in configuration, but I am not seeing what I did wrong. Can someone please set me on the correct path? Andrew Fant | Systems Administrator