I also can't seem to make it sync, see my test below. Tests:
# Set the date to somewhere in the past sudo date -s 'Tue Sep 3 12:00:00 JST 2019' # Set the hwclock to the same wrong date sudo hwclock --systohc Then I launched (open)ntpd manually in verbose mode: sudo /gnu/store/j4abi03pc4b0gfs2mlbzyd6g9bjqphyc-openntpd-6.2p3/sbin/ntpd -f /gnu/store/v2cqcxliivrcn1rlz78p6mg21k7pxyrx-ntpd.conf -d -s -v adjtimex returns frequency of 27.512100ppm listening on 127.0.0.1 listening on ::1 ntp engine ready constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca no constraint reply from 172.217.31.132 received in time, next query 900s no constraint reply from 172.217.31.132 received in time, next query 900s no constraint reply from 2001:470:142:3::a received in time, next query 900s no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s constraint: failed to load constraint ca constraint: failed to load constraint ca no constraint reply from 172.217.31.132 received in time, next query 900s no constraint reply from 172.217.31.132 received in time, next query 900s no constraint reply from 172.217.31.132 received in time, next query 900s no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s constraint: failed to load constraint ca no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s constraint: failed to load constraint ca no constraint reply from 209.51.188.148 received in time, next query 900s no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s no reply received in time, skipping initial time setting constraint: failed to load constraint ca constraint: failed to load constraint ca no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s no constraint reply from 172.217.31.132 received in time, next query 900s constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca constraint: failed to load constraint ca no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s no constraint reply from 172.217.31.132 received in time, next query 900s no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s no constraint reply from 172.217.31.132 received in time, next query 900s no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s no constraint reply from 172.217.31.132 received in time, next query 900s no constraint reply from 2404:6800:4004:818::2004 received in time, next query 900s cat /gnu/store/v2cqcxliivrcn1rlz78p6mg21k7pxyrx-ntpd.conf listen on 127.0.0.1 listen on ::1 constraints from "https://www.google.com/"; constraints from "https://www.google.com/"; sensor udcf0 correction 70000 constraints from "https://www.google.com/"; server 0.guix.pool.ntp.org server 1.guix.pool.ntp.org server 2.guix.pool.ntp.org server 3.guix.pool.ntp.org constraints from "https://www.google.com/"; constraints from "https://www.google.com/"; constraint from www.gnu.org Many tens of minutes later my date is still stuck in the past (despite using the "-s" flag, which is supposed to set the time immediately rather than slowly at startup). Am I missing something? Maxim
