NTP - chrony

from Leap 15.1, chrony has been promoted for Time Synchronization with NTP (cfr https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha-ntp.html)
But I found also the command time “timedatectl status” indicating:

Network time on: no
NTP synchronized: no
 RTC in local TZ: no

Running “systemctl status chronyd”, this shows:

Active: active (running) since...
Apr 03 16:34:36 vmi107108 systemd[1]: Starting NTP client/server...
Apr 03 16:34:36 vmi107108 systemd[1]: Started NTP client/server.

Does this means that the NPT client/server is not always active? Or is the information from timedatectl misleading?

Many thanks to clarify!

AFAIK the timedatectl should be like that because the old ntpd daemon is not running. It was replaced by chrony with it’s systemd service. A machine should never run both at the same time

The output shows ‘starting’ and started’ but timedatectl output should also show information, did you actually setup some time servers?

Did you see output after it’s started as in selecting a source to sync to?

timedatectl status
      Local time: Fri 2020-04-03 10:46:10 CDT
  Universal time: Fri 2020-04-03 15:46:10 UTC
        RTC time: Fri 2020-04-03 15:46:09
       Time zone: America/Chicago (CDT, -0500)
 Network time on: no
NTP synchronized: yes
 RTC in local TZ: no <== this is because RTC is set to UTC

systemctl status chronyd

Active: active (running) since Fri 2020-04-03 10:45:06 CDT; 1min 20s ago
Apr 03 10:45:13 hostname chronyd[939]: Selected source

it shows status of systemd-timesyncd.service. It does not know about or care of any other daemon that implements NTP protocol.