[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

Dan Streetman 1937238 at bugs.launchpad.net
Mon Jul 26 15:46:34 UTC 2021 

> Hmm. The systemd-timesyncd package is installed and systemd-
timesyncd.service is enabled.

can you attach journalctl output from a full boot reproducing the
problem? I used your exact ntp config and it works fine for me, though
the systemd-time-wait-sync.service does of course stay 'activating' for
a few seconds until time is actually synced.

** No longer affects: systemd (Ubuntu Focal)

** No longer affects: systemd (Ubuntu Groovy)

** No longer affects: systemd (Ubuntu Hirsute)

** No longer affects: systemd (Ubuntu Impish)

** 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 at 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 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

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
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