monit not catching failed ping test

"Fant, Andrew (NIH/NIDA) [E]" <[email protected]>
Newsgroups gmane.comp.monitoring.monit.general
Message-ID <[email protected]>
Good morning.
     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



Remote Host 'host2_ping'

  status                       OK

  monitoring status            Monitored

  monitoring mode              active

  on reboot                    start

  ping response time           -

  data collected               Fri, 08 Mar 2019 10:41:33

But:



host1% ping host2

PING host2.example.org (192.168.1.2) 56(84) bytes of data.

From host1.example.org (192.168.1.1) icmp_seq=1 Destination Host Unreachable

From host1.example.org (192.168.1.1) icmp_seq=2 Destination Host Unreachable

From host1.example.org (192.168.1.1) icmp_seq=3 Destination Host Unreachable

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?

Thank you

--
Andrew Fant                      |            Systems Administrator
[email protected]       |      Lei Shi Lab , NIH/NIDA/IRP
(443)740-2849                   |

-- 
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.