Raspberry Pi ntp drifting a lot.
by rnturn from LinuxQuestions.org on (#6NT1Y)
I have two RPis on our LAN. All systems are running ntpd and using the NTP service (running on Slackware at 192.168.13.1) on the LAN as their server.
When I run the ansible command:
Code:ansible -i inv.ini all -a "{{ntpq_path}}/ntpq -p"("ntpq_path" is defined for each system in the inventory "inv.ini") all the system responses look "normal" -- offset down in low numbers. Except for the RPis. The offsets for those system is high. If I force the clocks on those systems using:
Code:ntpdate 192.168.13.1while running that Ansible command in a loop (every 60s), the I see no change in the offsets for those two systems. Running "date" on all the systems shows that the clocks seems to be pretty much in sync (within ~1s) so ntp is doing what it's supposed to be doing. The question is:
Why the big offsets?
Will they, eventually, become a problem?
TIA...
When I run the ansible command:
Code:ansible -i inv.ini all -a "{{ntpq_path}}/ntpq -p"("ntpq_path" is defined for each system in the inventory "inv.ini") all the system responses look "normal" -- offset down in low numbers. Except for the RPis. The offsets for those system is high. If I force the clocks on those systems using:
Code:ntpdate 192.168.13.1while running that Ansible command in a loop (every 60s), the I see no change in the offsets for those two systems. Running "date" on all the systems shows that the clocks seems to be pretty much in sync (within ~1s) so ntp is doing what it's supposed to be doing. The question is:
Why the big offsets?
Will they, eventually, become a problem?
TIA...