I tested systemd 245.4-4ubuntu3.12 just now. It worked immediately on
three boots!
raek@mizar:~$ apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.12
Candidate: 245.4-4ubuntu3.12
Version table:
*** 245.4-4ubuntu3.12 400
400 http://archive.ubuntu.com/ubuntu
Dan: I just added the PPA, upgraded the packages and did 3 reboots. In
all cases "systemctl" showed "starting" when I logged in and then
"started" some seconds later. So it seems like the problem is solved!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
My problem looks similar to the on reported in the Home Assistant bug
tracker.
raek@mizar:~$ systemctl status systemd-time-wait-sync
... *SNIP* ...
└─508
One more boot. This time I checked the timestamp of the
/run/systemd/timesync/synchronized file (and did not run any timedatectl
commands):
raek@mizar:~$ ls -la /run/systemd/timesync
total 0
drwxr-xr-x 2 systemd-timesync systemd-timesync 60 Jul 26 22:51 .
drwxr-xr-x 24 root root
I found these two bug tickets that could be relevant:
https://github.com/home-assistant/operating-system/issues/896
https://github.com/systemd/systemd/issues/8683
I should also add that this seems to happen on the majority of boots for
me, but not every boot. So there is some amount of
Here is the output from the journal from a boot where time-wait-
sync.service "stuck". (I removed some line relating to syncthing and to
a private IRC bot I run.) After boot I logged in, checked "journalctl"
and saw that time-wait-sync.service was "activating" and then ran
"timedatectl status" and
This is my contents of /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the
Hmm. The systemd-timesyncd package is installed and systemd-
timesyncd.service is enabled.
raek@mizar:~/code/raek-totp-token/firmware$ apt-cache policy systemd-timesyncd
systemd-timesyncd:
Installed: 245.4-4ubuntu3.11
Candidate: 245.4-4ubuntu3.11
Version table:
*** 245.4-4ubuntu3.11 500
This started happen to me in January of February. This is easy for me to
reproduce since it happens at every boot. I would be happy to provide
more information or run more tests if needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
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
10 matches
Mail list logo
