Greetings all;
In an attempt to reduce the load on my time servers and to mitigate the
jumps in system time that can play heck with timing errors of a running
LinuxCNc session, I have installed an ntp client on a raspbian buster,
and I think I have told it to listen to iburst from this machine. All
my other machine are setup similar and appear to be working ok.
But the pi with an identical config is still not synching.
2 working machine symply say ok when asked for status, old wheezy
installs.
A gene@shop:~$ sudo /etc/init.d/ntp status
[ ok ] NTP server is running.
Which is typical when its all synched
but the pi is reporting:
pi@rpi4:/var/log/ntpstats $ sudo /etc//init.d/ntp status
● ntp.service - Network Time Service
Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2020-03-14 20:17:25 EDT; 57min ago
Docs: man:ntpd(8)
Process: 16957 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited,
status=0/SUCCESS)
Main PID: 16963 (ntpd)
Tasks: 2 (limit: 4033)
Memory: 936.0K
CGroup: /system.slice/ntp.service
└─16963 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 114:122
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: leapsecond file
('/usr/share/zoneinfo/leap-seconds.list'): loaded,
expire=2020-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: Listen and drop on 0
v6wildcard [::]:123
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: Listen and drop on 1
v4wildcard 0.0.0.0:123
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: Listen normally on 2 lo
127.0.0.1:123
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: Listen normally on 3 eth0
192.168.71.13:123
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: Listen normally on 4 lo
[::1]:123
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: Listening on routing socket
on fd #21 for interface updates
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: Listen for broadcasts to
192.168.71.255 on interface #3 eth0
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: kernel reports TIME_ERROR:
0x2041: Clock Unsynchronized
Mar 14 20:17:25 rpi4.coyote.den ntpd[16963]: kernel reports TIME_ERROR:
0x2041: Clock Unsynchronized
What is wrong with my /etc/ntp.conf on the pi that is causing this
apparent failure?
Looking for ntp.conf diffs a grep -v '#' reports for a working machines
ntp.conf:
driftfile /var/lib/ntp/ntp.drift
statsdir /var/log/ntpstats/
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
server 192.168.71.3 iburst
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery
restrict 127.0.0.1
restrict ::1
disable auth
broadcastclient
while that same inverted grep on the pi reports:
driftfile /var/lib/ntp/ntp.drift
leapfile /usr/share/zoneinfo/leap-seconds.list
statsdir /var/log/ntpstats/
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
server coyote.coyote.den iburst
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
restrict 127.0.0.1
restrict ::1
restrict source notrap nomodify noquery <-different, # it no change
broadcast 192.168.71.255
disable auth
broadcastclient
Thanks everybody.
Cheers, Gene Heskett