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
