You are not logged in.
Pages: 1
First time I've noticed this problem. Eight or nine minutes after I booted, ntpd hadn't set the time on my computer.
[root@alarmpi ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
clock1.albyny.i .INIT. 16 u - 64 0 0.000 0.000 0.000
ponderosa.piney .INIT. 16 u - 64 0 0.000 0.000 0.000
a1.hotfile.com .INIT. 16 u - 64 0 0.000 0.000 0.000
host2.kingrst.c .INIT. 16 u - 64 0 0.000 0.000 0.000
Don't think it's a network problem because I was connected via SSH, and it looks like ntpd found some servers from pool.ntp.org.
Seconds after I restarted the service, the clock was back to normal.
systemctl restart ntpd
Any idea what caused this and how to prevent it in the future?
Offline
Moving to Other Architectures...
Offline
Pages: 1