Of course the solution is to use fping. Henrik has previously stated that fping is preferred over xymonping <<a href="http://lists.xymon.com/archive/2012-January/033738.html">http://lists.xymon.com/archive/2012-January/033738.html</a>>, and the fping.sh script used when building will warn that "it is not yet fully stable".<div>
<br></div><div>I've just now installed fping (and configured Xymon to use it) and my graphs are now showing much more reasonable values than before.</div><div><br></div><div>Nevertheless, it's not obvious in any documentation that xymonping will give bad data. The caveats on its use suggest (to me) that it can miss some replies when large numbers of hosts are probed, but in practice it gives bad data even when the number of hosts is two.</div>
<div><br></div><div>J</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 9 January 2013 10:39, Jeremy Laidman <span dir="ltr"><<a href="mailto:jlaidman@rebel-it.com.au" target="_blank">jlaidman@rebel-it.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yup, I get this too, tested with v4.3.10 and v4.3.4. It also shows up when I ping the localhost address repeatedly:<div>
<br></div><div><div>sudo ./xymon-4.3.4/xymonnet/xymonping 127.0.0.1 127.0.0.1 127.0.0.1 127.0.0.1 127.0.0.1</div>
<div>127.0.0.1 is alive (20 ms)</div><div>127.0.0.1 is alive (0.02 ms)</div><div>127.0.0.1 is alive (24 ms)</div><div>127.0.0.1 is alive (0.02 ms)</div><div>127.0.0.1 is alive (0.02 ms)</div></div><div><br></div><div>The 20ms and 24ms entries are wrong, and they change as I adjust the max-pps values, by a factor of 5.</div>
<div><br></div><div>None of my conn graphs seems to be completely flatlined, but I have noticed that DNS test times are usually less than conn test times, which is a bit odd, but might be unrelated. Hmm, now that I look at them, it seems all of my graphs but one are hovering close to either 24ms or 48ms. The host that is the exception, with a conn graph that looks correct, happens to be the last entry if I sort all host IP addresses.</div>
<div><br></div><div>J</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On 9 January 2013 05:49, Michael Beatty <span dir="ltr"><<a href="mailto:Michael.Beatty@sherwin.com" target="_blank">Michael.Beatty@sherwin.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div bgcolor="#FFFFFF" text="#000000">
<tt>Using Xymon 4.3.7<br>
OS Linux SuSE<br>
<br>
I've been struggling to understand why certain hosts are almost
always reporting the exact same ping response time. I've
determined, that xymonping isn't working, it is reporting
incorrect data for half of the hosts tested.<br>
<br>
I start by pinging 6 hosts, one at a time, everything is correct<br>
<i>[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.22<br>
X.X.X.22 is alive (0.06 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.70<br>
X.X.X.70 is alive (0.56 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.138<br>
X.X.X.138 is alive (826 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137<br>
X.X.X.137 is alive (980 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.201<br>
X.X.X.201 is alive (0.75 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.202<br>
X.X.X.202 is alive (0.66 ms)<br>
</i><br>
<br>
Then, put them in the same command, the first, second, and fifth
values are wrong<br>
<i>[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.70
X.X.X.22 X.X.X.138 X.X.X.137 X.X.X.201 X.X.X.202<br>
X.X.X.70 is alive (40 ms)<br>
X.X.X.22 is alive (20 ms)<br>
X.X.X.138 is alive (1307 ms)<br>
X.X.X.137 is alive (1738 ms)<br>
X.X.X.201 is alive (20 ms)<br>
X.X.X.202 is alive (0.64 ms)</i><br>
<br>
<br>
Switch the order of the pings, the first, second, and fifth value
are exactly the same as the first time, and still wrong<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.201
X.X.X.202 X.X.X.137 X.X.X.138 X.X.X.70 X.X.X.22<br>
X.X.X.201 is alive (40 ms)<br>
X.X.X.202 is alive (20 ms)<br>
X.X.X.137 is alive (1598 ms)<br>
X.X.X.138 is alive (2069 ms)<br>
X.X.X.70 is alive (20 ms)<br>
X.X.X.22 is alive (0.04 ms)<br>
[xymon@mxbscs tmp]$ <br>
<br>
Switch the order again, now the third, fourth, and fifth values
are wrong.<br>
<i>[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137
X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22<br>
X.X.X.137 is alive (1537 ms)<br>
X.X.X.138 is alive (2016 ms)<br>
X.X.X.201 is alive (40 ms)<br>
X.X.X.202 is alive (20 ms)<br>
X.X.X.70 is alive (20 ms)<br>
X.X.X.22 is alive (0.06 ms)</i><br>
<br>
<br>
Another thing I have noticed is that by altering the max-pps
value, you get completely different results.<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137
X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=1<br>
X.X.X.137 is alive (2000 ms)<br>
X.X.X.138 is alive (1000 ms)<br>
X.X.X.201 is alive (2000 ms)<br>
X.X.X.202 is alive (1000 ms)<br>
X.X.X.70 is alive (1000 ms)<br>
X.X.X.22 is alive (0.06 ms)<br>
<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137
X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=5<br>
X.X.X.137 is alive (1500 ms)<br>
X.X.X.138 is alive (1479 ms)<br>
X.X.X.201 is alive (400 ms)<br>
X.X.X.202 is alive (200 ms)<br>
X.X.X.70 is alive (200 ms)<br>
X.X.X.22 is alive (0.06 ms)<br>
<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137
X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=25<br>
X.X.X.137 is alive (765 ms)<br>
X.X.X.138 is alive (896 ms)<br>
X.X.X.201 is alive (80 ms)<br>
X.X.X.202 is alive (40 ms)<br>
X.X.X.70 is alive (40 ms)<br>
X.X.X.22 is alive (0.04 ms)<br>
<br>
<br>
</tt><tt>It doesn't appear to be a problem with my configuration. </tt><tt>I
checked the <a href="http://www.xymon.com" target="_blank">www.xymon.com</a> demo site, and there seems to be the
same issue there. </tt><tt>The signature of the bad data is easy
to see in the graphs as good data has and diverse line, where as
bad data is a generally flat line. </tt><br>
<tt>These hosts look good:<br>
<a href="http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=pto.linuxbog.dk&SERVICE=conn" target="_blank">http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=pto.linuxbog.dk&SERVICE=conn</a><br>
<a href="http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=dali.hswn.dk&SERVICE=conn" target="_blank">http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=dali.hswn.dk&SERVICE=conn</a><br>
<br>
These hosts look bad:<br>
<a href="http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=blixen.hswn.dk&SERVICE=conn" target="_blank">http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=blixen.hswn.dk&SERVICE=conn</a><br>
<a href="http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=wifi.hswn.dk&SERVICE=conn" target="_blank">http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=wifi.hswn.dk&SERVICE=conn</a><span><font color="#888888"><br>
<br>
<br>
<br>
</font></span></tt><span><font color="#888888">
<pre cols="72">--
Michael Beatty
</pre>
</font></span></div>
<br></div></div>_______________________________________________<br>
Xymon mailing list<br>
<a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a><br>
<a href="http://lists.xymon.com/mailman/listinfo/xymon" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>