I did a downgrade as proposed and can confirm that the problem goes away then.
We are running our own ntp server on bionic. Maybe you could verify the problem by running your own ntp server. The problem with check_ntp_time also occurs when querying localhost.
The following commented out ntp-server option with "kod" enabled leads to "Offset unknown".
restrict -4 default notrap nomodify nopeer noquery limited
#restrict -4 default kod notrap nomodify nopeer noquery limited
Hello Paride,
thanks for your analysis.
I did a downgrade as proposed and can confirm that the problem goes away then.
We are running our own ntp server on bionic. Maybe you could verify the problem by running your own ntp server. The problem with check_ntp_time also occurs when querying localhost.
The following commented out ntp-server option with "kod" enabled leads to "Offset unknown".
restrict -4 default notrap nomodify nopeer noquery limited
#restrict -4 default kod notrap nomodify nopeer noquery limited
The following post suspects that check_ntp_time is not handling kod correctly. /serverfault. com/a/947963
https:/
Thanks,
Christoph