This is almost certainly because you don't have the systemd-timesyncd
package installed, or you don't have the systemd-timesyncd service
enabled.

On a very quick glance, it seems the systemd-time-wait-sync service
should have been bundled into the systemd-timesyncd package when it was
split from the main systemd package, however I'll have to look closer to
see if there is some reason it wasn't.

** Description changed:

+ [impact]
+ 
+ systemd-time-wait-sync service never completes when systemd-timesyncd
+ package is not installed
+ 
+ [test case]
+ 
+ remove the systemd-timesyncd package and enable the systemd-time-wait-
+ sync service, and reboot. Check status of the service to see it's stuck
+ in 'activating' state, e.g.:
+ 
+ ubuntu@lp1937238-f:~$ sudo 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 Fri 2021-07-23 15:32:12 UTC; 19s ago
+ 
+ [regression potential]
+ 
+ TBD
+ 
+ [scope]
+ 
+ this is needed in f and later
+ 
+ the systemd-timesyncd package was split out from the main systemd
+ package starting in focal, so this problem exists in f and later
+ 
+ the service doesn't exist in b, so this is not needed there
+ 
+ [original 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@mizar:~$ lsb_release -rd
  Description:    Ubuntu 20.04.2 LTS
  Release:        20.04
  
- 
  raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service
-   systemd-time-wait-sync.service                                              
                 loaded activating start     start Wait Until Kernel Time 
Synchronized                                          
- 
+   systemd-time-wait-sync.service                                              
                 loaded activating start     start Wait Until Kernel Time 
Synchronized
  
  raek@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
+      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@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@mizar:~$ dpkg -S /lib/systemd/system/systemd-time-wait-sync.service
  systemd: /lib/systemd/system/systemd-time-wait-sync.service
  
- 
  raek@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
+   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

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Groovy)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Impish)
   Importance: Undecided
       Status: New

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to