Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timedatectl reports wrong status of systemd-timesyncd #2568

Open
sgolightly opened this Issue Mar 19, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@sgolightly
Copy link

sgolightly commented Mar 19, 2019

Issue Report

Bug

Container Linux Version

$ cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=2023.5.0
VERSION_ID=2023.5.0
BUILD_ID=2019-03-09-0138
PRETTY_NAME="Container Linux by CoreOS 2023.5.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Environment

Cluster of 170 EC2 instances

Expected Behavior

When systemd-timesyncd is active, timedatectl status should report it as active

Actual Behavior

timedatectl status reports systemd-timesyncd.service active: no

Reproduction Steps

$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: disabled)
   Active: active (running) since Fri 2019-03-15 17:48:26 UTC; 3 days ago
     Docs: man:systemd-timesyncd.service(8)
 Main PID: 923 (systemd-timesyn)
   Status: "Synchronized to time server 10.60.16.25:123 (10.60.16.25)."
    Tasks: 2 (limit: 131071)
   Memory: 4.3M
   CGroup: /system.slice/systemd-timesyncd.service
           └─923 /usr/lib/systemd/systemd-timesyncd

Mar 19 11:47:05 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Network configuration changed, trying to establish connection.
Mar 19 11:47:05 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Synchronized to time server 10.60.16.25:123 (10.60.16.25).
Mar 19 12:17:05 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Network configuration changed, trying to establish connection.
Mar 19 12:17:05 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Synchronized to time server 10.60.16.25:123 (10.60.16.25).
Mar 19 12:47:03 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Network configuration changed, trying to establish connection.
Mar 19 12:47:03 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Synchronized to time server 10.60.16.25:123 (10.60.16.25).
Mar 19 13:17:03 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Network configuration changed, trying to establish connection.
Mar 19 13:17:03 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Synchronized to time server 10.60.16.25:123 (10.60.16.25).
Mar 19 13:47:03 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Network configuration changed, trying to establish connection.
Mar 19 13:47:03 ip-10-29-10-144.us-west-2.compute.internal systemd-timesyncd[923]: Synchronized to time server 10.60.16.25:123 (10.60.16.25).
$ timedatectl status
                      Local time: Tue 2019-03-19 14:17:06 UTC
                  Universal time: Tue 2019-03-19 14:17:06 UTC
                        RTC time: Tue 2019-03-19 14:17:07
                       Time zone: UTC (UTC, +0000)
       System clock synchronized: yes
systemd-timesyncd.service active: no
                 RTC in local TZ: no
@dm0-

This comment has been minimized.

Copy link
Member

dm0- commented Mar 19, 2019

This appears to work correctly with systemd 241 which will be used in the stable channel in a month.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.