Public bug reported:
when calling timedatectl in Ubuntu Core 18 the tool reports the status of the
systemd-timesyncd.service ...
sadly it does report it wrongly (the tool reports it inactive while the
service is actually running):
ogra@pi4:~$ timedatectl
Local time: Wed 2020-07-01 10:52:48 UTC
Universal time: Wed 2020-07-01 10:52:48 UTC
RTC time: n/a
Time zone: n/a (UTC, +0000)
System clock synchronized: yes
systemd-timesyncd.service active: no
RTC in local TZ: no
ogra@pi4:~$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled;
vendor preset: enabled)
Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 779 (systemd-timesyn)
Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/systemd-timesyncd.service
└─779 /lib/systemd/systemd-timesyncd
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1885901
Title:
timedatectl reports wrong status for timesyncd in core18
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
New
Status in systemd source package in Focal:
New
Status in systemd source package in Groovy:
New
Bug description:
when calling timedatectl in Ubuntu Core 18 the tool reports the status of the
systemd-timesyncd.service ...
sadly it does report it wrongly (the tool reports it inactive while
the service is actually running):
ogra@pi4:~$ timedatectl
Local time: Wed 2020-07-01 10:52:48 UTC
Universal time: Wed 2020-07-01 10:52:48 UTC
RTC time: n/a
Time zone: n/a (UTC, +0000)
System clock synchronized: yes
systemd-timesyncd.service active: no
RTC in local TZ: no
ogra@pi4:~$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled;
vendor preset: enabled)
Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 779 (systemd-timesyn)
Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/systemd-timesyncd.service
└─779 /lib/systemd/systemd-timesyncd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
