Arch Linux

NginUS

Member

Registered: 2019-04-13

Posts: 10

[SOLVED] systemd.timesyncd & timedatectl startup issues

When I search the forums here for a solution I found one [0] that was similar, but the fix mentioned there [1] is already in place [2] on mine.

I followed the instructions on the Arch wiki [3], & it appears to be configured properly, with the exception of one thing:
When I try to see if it's alright, the output seems contradictory.

For example this part seems fine:

$ sudo timedatectl status
               Local time: Mon 2019-05-20 23:39:49 EDT
           Universal time: Tue 2019-05-21 03:39:49 UTC
                 RTC time: Tue 2019-05-21 03:39:50
                Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

But this part shows "Frequency=0":

$ timedatectl show-timesync --all
LinkNTPServers=
SystemNTPServers=clock.nyc.he.net
FallbackNTPServers=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.org
ServerName=clock.nyc.he.net
ServerAddress=209.51.161.238
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=1min 4s
NTPMessage={ Leap=0, Version=4, Mode=4, Stratum=1, Precision=-24, RootDelay=0, RootDispersion=1.098ms, Reference=CDMA, OriginateTimestamp=Mon 2019-05-20 23:39:39 EDT, ReceiveTimestamp=Mon 2019-05-20 23:39:39 EDT, TransmitTimestamp=Mon 2019-05-20 23:39:39 EDT, DestinationTimestamp=Mon 2019-05-20 23:39:39 EDT, Ignored=no PacketCount=2, Jitter=4.354ms }
Frequency=0

In order for that "Frequency=0" entry to properly reflect the config file I have to restart the systemd.timesyncd.service, after which I get this- which seems right:

$ timedatectl show-timesync --all
LinkNTPServers=
SystemNTPServers=clock.nyc.he.net
FallbackNTPServers=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.org
ServerName=clock.nyc.he.net
ServerAddress=209.51.161.238
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=1min 4s
NTPMessage={ Leap=0, Version=4, Mode=4, Stratum=1, Precision=-24, RootDelay=0, RootDispersion=1.373ms, Reference=CDMA, OriginateTimestamp=Mon 2019-05-20 23:40:28 EDT, ReceiveTimestamp=Mon 2019-05-20 23:40:29 EDT, TransmitTimestamp=Mon 2019-05-20 23:40:29 EDT, DestinationTimestamp=Mon 2019-05-20 23:40:29 EDT, Ignored=no PacketCount=1, Jitter=0 }
Frequency=-4822998

Not sure what to do here. Advice is appreciated.
Thanks in advance.

[0]
https://bbs.archlinux.org/viewtopic.php?id=233277

[1]
Set /var/lib/private/ to 700

[2]
https://files.catbox.moe/o101fx.png

[3]
https://wiki.archlinux.org/index.php/Systemd-timesyncd

Last edited by NginUS (2019-05-21 04:17:55)

NginUS

Member

Registered: 2019-04-13

Posts: 10

Re: [SOLVED] systemd.timesyncd & timedatectl startup issues

Apparently it was just a matter of waiting several minutes after startup. Will mark solved.