According to traceroute xymonnet ping to host.example.com failed at 19:11:15, but the notification was sent at 19:20:37. The alert is configured to send notification immediately.

Also, xymonnetagain should start doing ping test immediately as it is configured with interval 1m. But the next green status was not until 19:25:49. Where should I see the log for xymonnetagain did ping test ~ 5 times during this gap? xymonnet is default to interval 5m

I am using xymon 4.3.10 on linux.

Here are the relevant excerpts from various log files

root at xymon { ~ }$ grep host.example.com /var/log/xymon/notifications.log.1 Sat Jan 19 19:20:37 2013 host.examplecom.conn (192.168.128.203) support at example.com[215] 1358641237 500

root at xymon { ~ }$ cat histlogs/host_example_com/conn/Sat_Jan_19_19\:20\:25_2013 red <!-- [flags:ordAstLe] --> Sat Jan 19 19:11:15 2013 conn NOT ok

Service conn on host.example.com is not OK : Host does not respond to ping

System unreachable for 1 poll periods (0 seconds)

&red 192.168.128.203 is unreachable Traceroute results: traceroute to 192.168.128.203 (192.168.128.203), 30 hops max, 60 byte packets 1 svcs-01.example.com (192.168.7.67) 0.510 ms 0.592 ms 0.697 ms 2 192.168.13.106 (192.168.13.106) 0.320 ms 0.341 ms 0.378 ms 3 core-02.example.com (192.168.13.101) 1.104 ms 1.092 ms 1.072 ms 4 * * * 5 * * * 6 * * * ..... 30 * * *

Status unchanged in 0.00 minutes Message received from 192.168.0.53

root at xymon { ~ }$ cat histlogs/host_example_com/conn/Sat_Jan_19_19\:25\:49_2013 green <!-- [flags:OrdAstLe] --> Sat Jan 19 19:25:49 2013 conn ok

Service conn on host.example.com is OK (up)

&green 192.168.128.203 is alive (35.3 ms)

Status unchanged in 0.00 minutes Message received from 192.168.0.53

-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?