After upgrade to v4 NTP not syncing

[k5map]

I have a Pi Zero running Pi-Star v3 for over a year without any issues... yesterday I upgraded to Pi-Star v4 and have rebooted the PiZ multiple times but ntp time is not syncing. I stopped the ntp service and attempted to run "sudo ntpdate pool.ntp.org" but get "sudo: ntpdate: command not found". I also checked to make sure the service was running:

Code: Select all

pi-star@pi-star(ro):~$ service ntp status
● ntp.service - Network Time Service
   Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-04-14 19:38:21 CDT; 17h ago
     Docs: man:ntpd(8)
  Process: 720 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, status=0/SUCCESS)
 Main PID: 765 (ntpd)
   Memory: 1.2M
   CGroup: /system.slice/ntp.service
           └─765 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 110:117

Apr 15 12:57:15 pi-star ntpd[765]: Soliciting pool server 208.76.53.137
Apr 15 12:57:30 pi-star ntpd[765]: Soliciting pool server 108.61.73.243
Apr 15 12:57:45 pi-star ntpd[765]: Soliciting pool server 2001:4998:58:183a::1001
Apr 15 12:57:48 pi-star ntpd[765]: Soliciting pool server 198.255.68.106
Apr 15 12:58:22 pi-star ntpd[765]: Soliciting pool server 72.30.35.89
Apr 15 12:58:35 pi-star ntpd[765]: Soliciting pool server 44.190.6.254
Apr 15 12:58:52 pi-star ntpd[765]: Soliciting pool server 2600:3c02:e000:bc::230
Apr 15 12:58:53 pi-star ntpd[765]: Soliciting pool server 208.75.88.4
Apr 15 12:59:29 pi-star ntpd[765]: Soliciting pool server 162.159.200.123
Apr 15 12:59:41 pi-star ntpd[765]: Soliciting pool server 163.237.218.19
pi-star@pi-star(ro):~$

As I read this, it is attempting to sync with ntp servers. I can also ping the servers on the list.

SO... I'm at a loss to determine why ntp is not working. Anyone have any ideas?

[k5map]

KE7FNS,

Thanks... I don't have this problem with my other Pi-Star (its running v3) so do you think they left the ntpdate package out of v4?

Also, even though I don't have the ntpdate package installed, do you agree ntp is attempting to sync? When I look in the ntp.conf file, it does have the pool servers listed.

[k5map]

I was using this to monitor ntp syncing

Code: Select all

pi-star@pi-star(ro):~$ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.debian.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.002
 1.debian.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.002
 2.debian.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.002
 3.debian.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.002
pi-star@pi-star(ro):~$ 

Much thanks for the timedatectl command... wasn't aware of that. But running it confirms my PiZ is not syncing so the search for a solution continues.

Code: Select all

pi-star@pi-star(ro):~$ timedatectl
               Local time: Wed 2020-04-15 18:12:04 CDT
           Universal time: Wed 2020-04-15 23:12:04 UTC
                 RTC time: n/a
                Time zone: America/Chicago (CDT, -0500)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no
pi-star@pi-star(ro):~$ 

[AF6VN]

I'm not sure you can fully trust that, plus it takes a while for ntp to do its thing and get sync'd. It doesn't happen immediately.

Tell me about it... I have a few Beaglebones and R-Pis lying around, and periodically I'll boot them in order to do "sudo apt update; sudo apt upgrade" sequences... And too many time have had the "update" step fail with "repository validity time in the future"... I have to wait for the time sync to complete and redo the command.