My problem looks similar to the on reported in the Home Assistant bug
tracker.
raek@mizar:~$ systemctl status systemd-time-wait-sync
... *SNIP* ...
└─508 /lib/systemd/systemd-time-wait-sync
raek@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@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@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@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937238
Title:
systemd-time-wait-sync.service stuck in "activating" state after boot,
blocks timers from starting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937238/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
