śr., 22 maj 2019 o 17:32 Giovanni Biscuolo <[email protected]> napisał(a): Hi Giovanni, > Hi Adam, > > Adam Mazurkiewicz <[email protected]> writes: > > [...] > > > I expected that it would sync system time, but it did not. I have > > still been getting the time of my computer BIOS in a terminal, not the > > synced one. > > If system clock is too late (or too far in the future) ntpd will not > update it > > «Normally, ntpd exits if the offset exceeds the sanity limit, which is > 1000 s by default. » [1] > > Is this your case? I had CEST set in BIOS instead of UTC. Guixsd added 2 hours so the offset was exceeded. So this was a reason. I think.
> > > Also in Xfce DE Clock. I have no idea how to debug it and > > fix. > > To debug you should check "sudo tac /var/log/messages | grep ntpd | > less" messages Now time is successfuly updating but still some error messages remains: May 24 18:43:16 localhost shepherd[1]: Service ntpd has been started. May 24 18:43:16 localhost ntpd[303]: ntpd [email protected] Mon Mar 18 23:20:45 UTC 2019 (1): Starting May 24 18:43:16 localhost ntpd[303]: Command line: /gnu/store/c7lsm0nkrdkp1rapg6qkrr6121d1g2nh-ntp-4.2.8p13/bin/ntpd -n -c /gnu/store/1l1yf5dss8r9pqxklaax32s6bkah09c6-ntpd.conf -u ntpd May 24 18:43:16 localhost ntpd[303]: proto: precision = 0.075 usec (-24) May 24 18:43:16 localhost ntpd[303]: baseday_set_day: invalid day (25556), UNIX epoch substituted May 24 18:43:16 localhost ntpd[303]: basedate set to 1970-01-01 May 24 18:43:16 localhost ntpd[303]: gps base set to 1980-01-05 (week 0) May 24 18:43:16 localhost ntpd[303]: restrict default: KOD does nothing without LIMITED. May 24 18:43:16 localhost ntpd[303]: restrict ::: KOD does nothing without LIMITED. May 24 18:43:17 localhost ntpd[303]: Listen and drop on 0 v6wildcard [::]:123 May 24 18:43:17 localhost ntpd[303]: Listen and drop on 1 v4wildcard 0.0.0.0:123 May 24 18:43:17 localhost ntpd[303]: Listen normally on 2 lo 127.0.0.1:123 May 24 18:43:18 localhost ntpd[303]: Listen normally on 3 lo [::1]:123 May 24 18:43:18 localhost ntpd[303]: Listening on routing socket on fd #20 for interface updates May 24 18:43:18 localhost ntpd[303]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized May 24 18:43:18 localhost ntpd[303]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized May 24 18:43:23 localhost ntpd[303]: Listen normally on 4 enp2s0 192.168.2.100:123 May 24 18:43:23 localhost ntpd[303]: Listen normally on 5 enp2s0 [fe80::9a7d:7c36:3981:569d%2]:123 May 24 18:40:50 localhost ntpd[303]: receive: Unexpected origin timestamp 0xe0929e76.87709e83 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe0929d12.2dc3cf7a s@s ~$ And I had to wait for the update about 5 minutes. But anyway at least this situation is not bad. > > > Any help will be appreciated. > > Set your clock (via date command or some GUI) and then "sudo hwclock > --systohc" to update your BIOS clock. I did so and it updated BIOS time successfuly. > > Last but not least: check your hardware clock setting are preserved > between reboots, if not you should change it's battery (if it's not > broken). > > HTH! Gio' > > > [1] http://doc.ntp.org/4.1.0/ntpd.htm > > > -- > Giovanni Biscuolo > > Xelera IT Infrastructures Thanks, Giovanni
