Re: unidentified output from fping
On Wed, 1 Apr 2009, Alain wrote: > I looked at fping.monitor from the latest distribution (mon-1.2.0) and > see there's been a number of changes since the version I was using > (0.99.2-13). Sure enough using this latest version of fping.monitor > resolved them problem. However, I'm still curious what exactly the old > fping.monitor saw that the new one doesn't? Any ideas? the adjustment was to handle some extra icmp messages from routers which indicate that a host was unreachable, rather than relying on just the timeout. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
unidentified output from fping
Hello, Firstly, many thanks for mon, it's really really great! Have a small curiosity. I converted two OSS Xen machines to Citrix XenServer for a client, they've been getting alerts from mon similar to: Summary output: unusual errors Group : ping-servers Service : ping Time noticed : Tue Mar 31 12:47:50 2009 Secs until next alert : Members : sls-xen1 sls-xen2 sls-xen3 sls-xen4 Detailed text (if any) follows: --- start time: Tue Mar 31 12:47:18 2009 end time : Tue Mar 31 12:47:19 2009 duration : 1 seconds -- unusual errors -- unidentified output from fping: [sls-xen4 : duplicate for [0], 84 bytes, 0.67 ms] -- reachable hosts rtt -- sls-xen1 0.53 ms sls-xen2 0.17 ms sls-xen3 0.38 ms sls-xen4 0.63 ms What's weird is that we get these alerts for xen1 and xen4 (Citrix XenServer) but not for xen2 and xen3 (OSS Xen) and didn't get the alerts for xen1 and xen4 prior to last night when they were OSS Xen. I'd like to see what output fping.monitor is complaining about. When I run fping.monitor manually (e.g. "./fping.monitor sls-xen4"), it shows normal output. I've also tried fping with various options and don't see any problems either. I looked at fping.monitor from the latest distribution (mon-1.2.0) and see there's been a number of changes since the version I was using (0.99.2-13). Sure enough using this latest version of fping.monitor resolved them problem. However, I'm still curious what exactly the old fping.monitor saw that the new one doesn't? Any ideas? Many thanks, Alain ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: unidentified output from fping
On Tue, 5 Apr 2005, Hans Fugal wrote: I just discovered mon. There's a few words to describe mon. Epiphany, nirvana, elation to name a few. So thanks a million for all the hard work. wow, that's over the top! I'm getting the following alert from an fping.monitor service: ... -- unusual errors -- unidentified output from fping: [172.16.60.10 : duplicate for [0], 84 bytes, 326 +ms] which version of fping? i think the newer versions might have updated their output, and fping.monitor doesn't understand the newer messages. i'll see if i can change fping.monitor to understand the new output. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
unidentified output from fping
I just discovered mon. There's a few words to describe mon. Epiphany,
nirvana, elation to name a few. So thanks a million for all the hard
work.
Now for the question:
I'm getting the following alert from an fping.monitor service:
...
--
unusual errors
--
unidentified output from fping: [172.16.60.10 : duplicate for [0], 84 bytes, 326
+ms]
...
When I run fping.monitor by hand I get nothing like that:
[EMAIL PROTECTED]:/usr/lib/mon/mon.d$ ./fping.monitor 172.16.57.10 172.16.57.11
>
start time: Tue Apr 5 16:23:51 2005
end time : Tue Apr 5 16:23:51 2005
duration : 0 seconds
--
reachable hosts rtt
--
172.16.57.10 3.14 ms
172.16.57.11 2.65 ms
172.16.57.12 2.79 ms
172.16.59.13 2.27 ms
172.16.57.14 2.71 ms
172.16.60.10 94.90 ms
172.16.61.10 50.50 ms
10.101.1.7 52.10 ms
172.16.62.10 142.00 ms
Here's the interesting part of /etc/mon/mon.cf:
hostgroup annexes 172.16.57.10 172.16.57.11 172.16.57.12 172.16.59.13
172.16.57.14 172.16.60.10 172.16.62.10 172.16.61.10 10.101.1.7
watch annexes
service ping
depend routers:ping
interval 5m
monitor fping.monitor
period wd {Mon-Fri} hr {9am-5pm}
alert mail.alert fugalh
alertevery 2h
Any ideas?
--
De gustibus non disputandum est.
___
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
