Ntpd not updating
NTP is pointing to a Cisco router set as NTP master.
I see ntp packets hit the router and it xmit's valid time to the esxi host address. The Cisco is set to peer with org and is getting correct time, though it shows as being stratum 4.
My PI 3Bs are my first set of computer (tiny or not) that use systemd by default (and, its a classic case of once I learned all the answers they changed all the questions! My clocks have been stable all day, have not drifted, but I don't know yet whether there is a conflict or whether there is a bug, or both. The dreadful timesyncd-systemd service tries to step the clock with ntp servers at boot time, exactly what ntpdate did. So now for me:$ service systemd-timesyncd status ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled) Active: inactive (dead) Docs: man:systemd-timesyncd.service(8) $ timedatectl Local time: Wed 2016-05-25 CEST Universal time: Tue 2016-05-24 UTC RTC time: n/a Time zone: Europe/Paris (CEST, 0200) NTP enabled: no NTP synchronized: yes RTC in local TZ: no DST active: yes ... I have a cron job on the machine that has my refclock to check and restart the daemon if it's gone. is not no connection, it means "not synced for the first time yet".
$ service ntp status ● ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp) Active: active (running) since Tue 2016-05-24 CEST; 7h ago Process: 1295 Exec Start=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ntp.service └─1379 /usr/sbin/ntpd -p /var/run/-g -u 12 $ sudo dpkg -l | grep ntp ii ntp 1:4.2.6.p5 dfsg-7 deb8u1 armhf Network Time Protocol daemon and utility programs (and no ntpdate) Roughly it is stable, I have sometimes ntpd go poof, it's not specific to the Pi, that's a debian (linux? NTP on RP 3 Jessie - I cannot get to work ntpq -p always shows refid as ". For those of you running multiple NTP *servers*, why not leave one server be the master, and others sync to it on the LAN?
So if you have a port forwarding rule in your router, you have to dedicate 1 server as the "master".
For those of you running multiple NTP *servers*, why not leave one server be the master, and others sync to it on the LAN?
However, you can try to check your Internet connection (e.g.
My next step has to be to try and load Wheezy on my PI3 - but I do this reluctantly This seems to have worked for me - at least now the time is not wandering off after reboot But the out put from timedatectl Local time: Sun 2016-05-29 HKT Universal time: Sun 2016-05-29 UTC RTC time: n/a Time zone: Asia/Hong_Kong (HKT, 0800) NTP enabled: no NTP synchronized: yes RTC in local TZ: no DST active: n/a Shows NTP not enabled - should I be worried about this? 123/udp must be allowed to flow out and IN: servers make unsolicited connections to each other. It should be automatic, and it should be reliable... I participated in the sinking of another thread about ntp recently (But that wasn't really my fault, nor ntp's I think) I have one Pi 3 I use as my lab mouse, it is up to date with the stable distro.Yes, an email; and the guys replied, it was 1990 all over again I also have on my network a USB radio-driven clock source, it's not super accurate but it's impervious to Internet weather conditions.However, when I restart the computer it is incorrect again (two minutes fast).It seems that NTP is updating the software clock but not the hardware clock.