[PROBLEM] Wrong date/time

[TheOldPresbyope]

@Sehnsucht 

This seems like a red flag:

Code:

  Status: "Idle."

Compare that to the same line in Tim's output.


What do you get in response to timedatectl? On my systems, which synchronized successfully, I see something like the following

Code:

pi@m833p3lcd:~ $ timedatectl
              Local time: Tue 2023-06-13 16:29:40 EDT
          Universal time: Tue 2023-06-13 20:29:40 UTC
                RTC time: n/a
               Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
             NTP service: active
         RTC in local TZ: no

where the clock is reported to be synchronized and the NTP service is active.

Searching the InterWeb™, I found a similar problem reported by a Ubuntu user somewhere in the world. It was suggested by respondents that the system may be taking too long to find and synchronize with an authoritative time server. As distributed, the default timeout in moOde (e.g., RaspberryPiOS) is 5s. That should be plenty of time for most setups but apparently there are edge cases.

It was suggested to edit the /etc/systemd/timesyncd.conf file to uncomment the #RootDistanceMaxSec=5 line and increase the timeout value from 5 to, say, 15.

It can't hurt to try; you can always change it back it if doesn't work.

Regards,
Kent