Mine too ...sumanratnam wrote: My Raspberry pi3 not updating time.
tried few recommendations from the forum as well as google.
Dougie, I'm telling you something changed very recently. I know how ntp works; and its not now. Something is different. All of my clocks are fine except the PI 3B (s) and only since last week.DougieLawson wrote:To be reliable you need a permanent connection to the internet.
give you some details of what NTP is doing.
I participated in the sinking of another thread about ntp recently (But that wasn't really my fault, nor ntp's I think)MarkHaysHarris777 wrote:Did /etc/ntp.conf get honked on a recent update?
Thanks for the reply. I have used a GPS receiver time source for several years... mostly reliable. Some of my problem is that I have avoided systemctl (timedatectl) and systemd until now... with Jessie Raspbian systemd is an issue for me too. 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!) aarge....epoch1970 wrote: (Perhaps you want to check if "timedatectl"does not report "NTP enabled" which would mean it competes with the ntpd daemon?)
(Also, I do not use pool.ntp.org servers. I've found fr.pool servers to be of unequal quality, so what I did a long time ago is lookup a list of public ntp servers and sent an email to a few admins asking the right to hookup to their servers. 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. Nowadays I believe a GPS module is even cheaper.)
Code: Select all
$ 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 00:29:57 CEST Universal time: Tue 2016-05-24 22:29:57 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 ... $ service ntp status ● ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp) Active: active (running) since Tue 2016-05-24 16:33:02 CEST; 7h ago Process: 1295 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ntp.service └─1379 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 107:112 $ 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)
This seems to have worked for me - at least now the time is not wandering off after rebootMarkHaysHarris777 wrote:1) stopped the ntpd with :
sudo systemctl stop ntp
2) rather than running ntpdate, ran ntpdate-debian:
3) started ntpd
sudo systemctl start ntp
sudo ntpq -p
Now, servers found, clocks synced, times right... now we'll see if the clocks drift, and whether they
sync-up on a boot-up later...
That's how my LAN runs. My internet facing server acts as the master NTP server for all my other Raspberries.epoch1970 wrote: For those of you running multiple NTP *servers*, why not leave one server be the master, and others sync to it on the LAN?
- "Master" server, say, stratum 3: server some.public.ntp.server
- "Secondary" server, stratum 4: server refclock-pi.lan