pI clock clock error

[baltika_no_9]

I'm still puzzling over this, I am not sure the NTP Server option in Openplotter is actually the culprit at all as that is intended to serve locally attached devices .

I'm sure you'll need to set up the AP before the NTP Server option becomes available as it serves devices connected that way. Why couldn't you set one up?

On further research I see that both NTP and systemd-timesyncd (replacement for NTP in newer Rasbian OS build) do not happily coexist with Openplotter network. If you install Openplotter network then it will remove either of those if they are installed.
Equally if you install either it removes Openplotter network. It looks like chrony is the preferred choice instead but I know nothing of it, need to dig a little I think.

As a matter of interest what do you see from the command

Code:

timedatectl status

Code:

pi@helvellyn:~ $ timedatectl status
               Local time: Sat 2023-06-10 08:55:32 BST
           Universal time: Sat 2023-06-10 07:55:32 UTC
                 RTC time: n/a
                Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
pi@helvellyn:~ $

---

Looking into chrony a bit more, assuming you have Openplotter Network installed then chrony should also be installed automatically. Here is what I see with this command:

Code:

sudo systemctl status chrony

Code:

pi@helvellyn:/etc/systemd $ sudo systemctl status chrony
● chrony.service - chrony, an NTP client/server
     Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2023-06-10 09:10:47 BST; 13min ago
       Docs: man:chronyd(8)
             man:chronyc(1)
             man:chrony.conf(5)
    Process: 3427 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
   Main PID: 3429 (chronyd)
      Tasks: 2 (limit: 779)
        CPU: 238ms
     CGroup: /system.slice/chrony.service
             ├─3429 /usr/sbin/chronyd -F 1
             └─3430 /usr/sbin/chronyd -F 1

Jun 10 09:10:46 helvellyn systemd[1]: Starting chrony, an NTP client/server...
Jun 10 09:10:47 helvellyn chronyd[3429]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCF>
Jun 10 09:10:47 helvellyn chronyd[3429]: Frequency 7.160 +/- 1.999 ppm read from /var/lib/chrony/chrony.drift
Jun 10 09:10:47 helvellyn chronyd[3429]: Using right/UTC timezone to obtain leap second data
Jun 10 09:10:47 helvellyn chronyd[3429]: Loaded seccomp filter
Jun 10 09:10:47 helvellyn systemd[1]: Started chrony, an NTP client/server.

And with

Code:

chronyc tracking

I get

Code:

pi@helvellyn:~ $ chronyc tracking
Reference ID    : 1DAF24B2 (rubidium.darksky.io)
Stratum         : 3
Ref time (UTC)  : Sat Jun 10 08:38:57 2023
System time     : 0.000058964 seconds slow of NTP time
Last offset     : -0.000052159 seconds
RMS offset      : 0.000210762 seconds
Frequency       : 6.018 ppm fast
Residual freq   : -0.016 ppm
Skew            : 0.410 ppm
Root delay      : 0.032903317 seconds
Root dispersion : 0.000678575 seconds
Update interval : 129.7 seconds
Leap status     : Normal
pi@helvellyn:~ $

So NTP appears to be working fine but of course my Pi is currently connected to the internet. Clearly if it wasn't then accessing web-based servers is not going to work.


Edit - if you enter the command sudo systemctl status chrony after booting up it will tell you how far off your system time is.