NTP daemon counts for 2 minutes on shutdowm

English Applications
1

doing a reboot - the NTP counts to stop for 2 minutes.

Did not do this on 15.2 - this was an update 15.2 to 15.3

Any idea why?

2

I am not seeing that. For me, Leap 15.3 shutdowns are reasonably fast.

On the other hand, I did a clean install from the DVD installer. Maybe it is different with an online upgrade.

3

my workaround is to “systemctl stop ntpd” before the reboot

4

Hmm. “ntpd” is not running here, and in fact not on the system at all. Rather, it is using “chronyd”.

5

Chrony stops in 0.000294 seconds:

**3400G:~ #** journalctl -b 0 --directory /mnt/@/var/log/journal/ -u chronyd.service -o short-monotonic  
-- Logs begin at Sun 2021-05-30 08:52:20 CEST, end at Thu 2021-06-03 06:58:22 CEST. -- 
   13.883691] Leap-15-3 systemd[1]: Starting NTP client/server... 
   13.896209] Leap-15-3 chronyd[1685]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 
   13.896909] Leap-15-3 chronyd[1685]: Frequency -0.044 +/- 2.517 ppm read from /var/lib/chrony/drift 
   13.921150] Leap-15-3 systemd[1]: Started NTP client/server. 
   25.206973] Leap-15-3 chronyd[1685]: Selected source 94.130.49.186 
   25.207249] Leap-15-3 chronyd[1685]: **System clock wrong by 1.869085 seconds, adjustment started**
   25.207283] Leap-15-3 chronyd[1685]: **System clock was stepped by 1.869085 seconds**
  284.001705] Leap-15-3 chronyd[1685]: Selected source 84.16.73.33 
 2407.**690802**] Leap-15-3 systemd[1]: Stopping NTP client/server... 
 2407.691017] Leap-15-3 systemd[1]: chronyd.service: Succeeded. 
 2407.**691096**] Leap-15-3 systemd[1]: Stopped NTP client/server. 
**3400G:~ #**