check_ntp_time
Posted: Sat Dec 31, 2016 6:00 am
Hi,
Appears the latest stable version of check_ntp_time has an issue with the upcoming leap second, all my servers running this version of check_ntp_time has as of a few hours ago started reporting as follows:-
sending request to peer 0
response from peer 0: offset 0.0008511543274
sending request to peer 0
response from peer 0: offset 0.0007092952728
sending request to peer 0
response from peer 0: offset 0.0007601976395
sending request to peer 0
response from peer 0: offset 0.0007613897324
discarding peer id 0: flags=1
overall average offset: 0
NTP CRITICAL: Offset unknown
It seems related to this in the system
Dec 31 02:18:10 ntpd[1356]: kernel reports leap second insertion scheduled
Any ideas?
Appears the latest stable version of check_ntp_time has an issue with the upcoming leap second, all my servers running this version of check_ntp_time has as of a few hours ago started reporting as follows:-
sending request to peer 0
response from peer 0: offset 0.0008511543274
sending request to peer 0
response from peer 0: offset 0.0007092952728
sending request to peer 0
response from peer 0: offset 0.0007601976395
sending request to peer 0
response from peer 0: offset 0.0007613897324
discarding peer id 0: flags=1
overall average offset: 0
NTP CRITICAL: Offset unknown
It seems related to this in the system
Dec 31 02:18:10 ntpd[1356]: kernel reports leap second insertion scheduled
Any ideas?