Xymon Mailing List Archive search

xymonping overinflated response time

3 messages in this thread

list Terry Hurcombe · Mon, 2 Jul 2018 16:09:24 +0000 ·
Hello list.

I've noted that since moving some systems from xymon 4.3.17 to 4.3.28 that ping times seem hugely inflated and do not match the response times I see from the command line utilities.

4.3.28 reports 40.2ms vs 0.92ms  from 4.3.17. Is this a known issue?

Regards,

Terry.
This message is confidential and may contain privileged information. You should not disclose its contents to any other person. If you are not the intended recipient, please notify the sender named above immediately. It is expressly declared that this e-mail does not constitute nor form part of a contract or unilateral obligation. Opinions, conclusions and other information in this message that do not relate to the official business of brightsolid shall be understood as neither given nor endorsed by it.


This email has been checked for virus and other malicious content prior to leaving our network.
list John Thurston · Mon, 2 Jul 2018 12:11:30 -0800 ·
Mebe you are using a different 'ping' mechanism between the two versions.

Are you/ were you using fping?

--
    Do things because you should, not just because you can.

John Thurston    XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Department of Administration
State of Alaska
quoted from Terry Hurcombe

On 7/2/2018 8:09 AM, Terry Hurcombe wrote:
I’ve noted that since moving some systems from xymon 4.3.17 to 4.3.28 
that ping times seem hugely inflated and do not match the response times 
I see from the command line utilities.
list W.J.M. Nelis · Tue, 3 Jul 2018 08:48:16 +0200 ·
Hello Terry,

quoted from John Thurston

I’ve noted that since moving some systems from xymon 4.3.17 to 4.3.28 that ping times seem hugely inflated and do not match the response times I see from the command line utilities.


4.3.28 reports 40.2ms vs 0.92ms  from 4.3.17. Is this a known issue?


I've seen this type of behaviour in xymon when using the default ping of xymon. In that case, the reported ping times are (almost) multiples of 20 [ms]. I guess that there is some sort of scheduling within xymon, which is responsible for this behaviour.

Regards,
  Wim Nelis.