08-07-2020, 11:16 AM
(08-07-2020, 09:01 AM)spaetz Wrote: I guess, we could be seeing:I was having this problem as well. Ran the code you suggested and got the following output:
https://bugs.debian.org/cgi-bin/bugrepor...bug=940840
We are using chrony as time sync daemon instead of the systemd ntp one. And the Debian bug then experiences similar hangs with the sstemd-time-wait-sync service running (which does not work with chronyd):
> systemd-time-wait-sync.service start running
Hm, this service is not enabled by default and I'm guessing it prevents
time-sync.target to be reached, blocking all subsequent services.
The man page says:
Code:> systemd-time-wait-sync is a system service that delays the start of units that depend on time-sync.target
> until the system time has been synchronized with an accurate time source by systemd-timesyncd.service.
So, any timer that waits until the time is synchronized is on hold. And the apt-daily-upgrade.timer is one of those, I guess.
UPDATE: I don't experience the hangs myself. Could somebody who does check with
```systemctl status systemd-time-wait-sync.service```
to see if this service is somehow enabled on their mobian device?
● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: disabled)
Active: activating (start) since Fri 2020-08-07 08:12:27 MST; 2h 0min ago
Docs: manystemd-time-wait-sync.service(8)
Main PID: 1488 (systemd-time-wa)
Tasks: 1 (limit: 1990)
Memory: 1.0M
CGroup: /system.slice/systemd-time-wait-sync.service
└─1488 /lib/systemd/systemd-time-wait-sync
Aug 07 08:12:28 mobian systemd-time-wait-sync[1488]: adjtime state 5 status 40 time Fri 2020-08-07 15:12:27.709948 UTC
Warning: journal has been rotated since unit was started, output may be incomplete.
Looks like it is enabled on my device.