xymonping is very buggy. Try doing your xymonping using more than one host, ie /usr/lib/xymon/xymonping 172.30.1.2 172.30.1.3 172.30.1.4 etc. What you will see is some strange results, same results you are seeing on the web pages.

My advice, (as well as Xymon's advice when you compile it) don't use xymonping. All its really good for is testing to see that a host is up or not. Its response times aren't dependable.

Michael Beatty

On 05/03/2013 01:57 PM, Sergey wrote:

Hello.

I attempted to use xymonping instead of fping. A part of xymonserver.cfg:

#FPING="/usr/sbin/fping" # Path and options for the ping program. FPING="/usr/lib/xymon/xymonping" # Path and options for the ping program.

A strange behavior was found: connection time of xymonping is very big.

172.30.1.2 is alive (0.64 ms) - this is fping 172.30.1.2 is alive (40 ms) - this is xymonping

But it is only on web page and in rrd (graph in attachment). Connection time is same when command line of xymon host (Linux) is used:

$ /usr/sbin/fping -Ae 172.30.1.2 172.30.1.2 is alive (0.63 ms)

$ /usr/lib/xymon/xymonping 172.30.1.2 172.30.1.2 is alive (0.70 ms)

Any ideas ?

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon