I have a pi3B+ with stretch. I am trying to sync its clock using a network master clock (a pc set as ntp server) through direct ethernet connection. I can't see my server synching the pi. I followed the instructions discussed here but while offline the pi cannot use my server (windows PC with w32tm running). The pi is in any case able to ping the server and viceversa, the UDP port is bidirectionally open on the server, the pi (running ntpq - pn) is able to even calculate the offset of its clock relative to the server... and this updates if I change the server time manually. Rebooting does not change anything (the pi fails to sync).

I have edited the /etc/ntp.conf file adding my server PC address adding the lines address x.x.x.x iburst fudge x.x.x.x stratum 1

any idea of why this does not work ?

  • Stretch does NOT use /etc/ntp.conf file it uses timesyncd – Milliways Mar 22 '19 at 11:36
  • 1
    I was about to post an answer, but then recalled this website that pretty much covers things for time synchronization. There are many ways to do this, this is one. You can read this if you do decide to install ntp, and this may also be helpful – Seamus Mar 22 '19 at 17:17
  • thanks I have tried both ways already (NTPD and timedatectl). as far as I understood NTPD is deprecated on raspbian stretch. Therefore I tried again timdetatectl. I edited the /etc/systemd/timesyncd.conf and added my server PC IP address at the line NTP=.... I rebooted and also used the command "sudo timedatectl set-ntp true" but neither worked. – livio Mar 27 '19 at 17:12
  • after running systemctl status systemd.timesyncd.service I can read the active status of the time-client is "inactive (dead)" , what does this mean ? – livio Apr 2 '19 at 9:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.