[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting
Rasmus Bondesson
1937238 at bugs.launchpad.net
Mon Jul 26 21:06:46 UTC 2021
My problem looks similar to the on reported in the Home Assistant bug
tracker.
raek at mizar:~$ systemctl status systemd-time-wait-sync
... *SNIP* ...
└─508 /lib/systemd/systemd-time-wait-sync
raek at mizar:~$ sudo lsof -nPp 508
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
... *SNIP* ...
systemd-t 508 root 0r CHR 1,3 0t0 6 /dev/null
systemd-t 508 root 1u unix 0xffff99d964ad0c00 0t0 16894 type=STREAM
systemd-t 508 root 2u unix 0xffff99d964ad0c00 0t0 16894 type=STREAM
systemd-t 508 root 3u a_inode 0,14 0 11428 [eventpoll]
systemd-t 508 root 4u a_inode 0,14 0 11428 [signalfd]
systemd-t 508 root 5r a_inode 0,14 0 11428 inotify
systemd-t 508 root 6u a_inode 0,14 0 11428 [timerfd]
raek at mizar:~$ sudo strace -ttTp 508
strace: Process 508 attached
22:59:52.923972 gettid() = 508 <0.000023>
22:59:52.925523 epoll_wait(3,
raek at mizar:~$ sudo cat /proc/508/fdinfo/5
pos: 0
flags: 02004000
mnt_id: 15
inotify wd:1 ino:17b sdev:18 mask:100 ignored_mask:0 fhandle-bytes:8 fhandle-type:1 f_handle:ac95aa8d7b010000
raek at mizar:~$ sudo cat /proc/508/mountinfo | grep :15
39 34 0:33 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:15 - cgroup cgroup rw,memory
The mountinfo lines look different for me than for tmm1 (see previously
linked home assistant ticket).
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1937238
Title:
systemd-time-wait-sync.service stuck in "activating" state after boot,
blocks timers from starting
Status in systemd package in Ubuntu:
Incomplete
Bug description:
When I start my server running Ubuntu 20.04 the systemd-time-wait-
sync.service is stuck in "activating" state. I noticed this because
none of the systemd timer units triggered, because all the timers
depend on systemd-time-wait-sync.service. Running "systemctl restart
systemd-time-wait-sync.service" manually works around the problem.
Some logs and command outputs:
raek at mizar:~$ lsb_release -rd
Description: Ubuntu 20.04.2 LTS
Release: 20.04
raek at mizar:~$ systemctl | grep systemd-time-wait-sync.service
systemd-time-wait-sync.service loaded activating start start Wait Until Kernel Time Synchronized
raek at mizar:~$ systemctl status systemd-time-wait-sync.service
● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled)
Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago
Docs: man:systemd-time-wait-sync.service(8)
Main PID: 514 (systemd-time-wa)
Tasks: 1 (limit: 9415)
Memory: 972.0K
CGroup: /system.slice/systemd-time-wait-sync.service
└─514 /lib/systemd/systemd-time-wait-sync
Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 time Thu 2021-07-22 09:06:52.216338 UTC
Warning: journal has been rotated since unit was started, output may be incomplete.
raek at mizar:~$ journalctl -b -u systemd-time-wait-sync.service
-- Logs begin at Wed 2020-07-08 16:34:13 CEST, end at Thu 2021-07-22 11:36:44 CEST. --
Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 time Thu 2021-07-22 09:06:52.216338 UTC
raek at mizar:~$ dpkg -S /lib/systemd/system/systemd-time-wait-sync.service
systemd: /lib/systemd/system/systemd-time-wait-sync.service
raek at mizar:~$ apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.11
Candidate: 245.4-4ubuntu3.11
Version table:
*** 245.4-4ubuntu3.11 500
500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status
245.4-4ubuntu3.10 500
500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
245.4-4ubuntu3.8 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
245.4-4ubuntu3 500
500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937238/+subscriptions
More information about the foundations-bugs
mailing list