You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to constantly reporting a score of -0.1, but on https://www.ntppool.org/scores/62.2.85.186 the recentmedian score is
fine with ~20, the legacy score shows quite often different values. This
is an IP address which has a long history of often being difficult to
reach from the previous monitoring system. It seems that some of my ISPs
transit carriers are doing some filtering / DDoS protection. This can be
seen with around half of the scores in "testing" being negativ.
Could it be, that the score in the json output still does use "old" (or
even stale) data? The IP 62.2.85.186 had a too low score since 13th
March 2023, so before the new monitoring system went into operation.
And the reply from NTPman:
That realy looks old data, the timestamps are 1679120256 and 1679120034 in the json, which means 18th of March.
The text was updated successfully, but these errors were encountered:
As mention in the community thread https://community.ntppool.org/t/score-logs-json-not-showing-most-recent-data/2822
I am using the Nagios check from https://github.com/mj/nagios-ntp-pool
to check the scores of my servers. It does use this URL:
https://www.pool.ntp.org/scores/62.2.85.186/json?limit=1
It seems to constantly reporting a score of -0.1, but on
https://www.ntppool.org/scores/62.2.85.186 the recentmedian score is
fine with ~20, the legacy score shows quite often different values. This
is an IP address which has a long history of often being difficult to
reach from the previous monitoring system. It seems that some of my ISPs
transit carriers are doing some filtering / DDoS protection. This can be
seen with around half of the scores in "testing" being negativ.
Another server (https://www.ntppool.org/scores/62.12.173.11) is just
fine and also the json looks good with reporting a score of 20:
https://www.pool.ntp.org/scores/62.12.173.11/json?limit=1
Could it be, that the score in the json output still does use "old" (or
even stale) data? The IP 62.2.85.186 had a too low score since 13th
March 2023, so before the new monitoring system went into operation.
And the reply from NTPman:
That realy looks old data, the timestamps are 1679120256 and 1679120034 in the json, which means 18th of March.
The text was updated successfully, but these errors were encountered: