I’m having ntp trouble again (thread from last time), but this time it seems to be confined to the
check_ntp_time plugin (or is it?).
This error came about when I noticed the time in “System > Monitoring Health > Process Info” was off by 10 hours exactly into the future (similar problem to last time). I did configure self-monitoring checks with this plugin, but it didn’t alert me of this, I just happened to manually check (even though
ntptime output had errors). I then proceeded to fix this by doing the same thing as last time:
- deleting respective rows in the DB
ntpdateto ntp server.
tinker panic 0in
- using multiple ntp servers in
After doing all of this, I got this error from
check_ntp_time (same error in Icingaweb2):
[icingaman@icinga2]# /usr/lib64/nagios/plugins/check_ntp_time -H 127.0.0.1 -v sending request to peer 0 response from peer 0: offset -3.147125244e-05 sending request to peer 0 response from peer 0: offset -2.765655518e-05 sending request to peer 0 response from peer 0: offset -2.682209015e-05 sending request to peer 0 response from peer 0: offset -2.586841583e-05 discarding peer 0: stratum=0 overall average offset: 0 NTP CRITICAL: Offset unknown|
ntp service is now fine and
ntptime show no errors:
[icingaman@icinga2 ~]$ ntptime ntp_gettime() returns code 0 (OK) time de975fad.8808fa48 Fri, May 4 2018 12:39:41.531, (.531387837), maximum error 2423516 us, estimated error 16 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset 0.000 us, frequency 9.344 ppm, interval 1 s, maximum error 2423516 us, estimated error 16 us, status 0x2001 (PLL,NANO), time constant 3, precision 0.001 us, tolerance 500 ppm,
date is also current.
This is not confined to one Icinga instance because I did the same routine mentioned above on all of my Icinga servers and have the same error on each of them.
What could possibly be the problem??? I’m thinking it might be a bug with the plugin itself but I’m not sure.