Service 'systemd-timesyncd' timeout while starting

G

Gecko

Active Member
Apr 10, 2018
18
1
43
45
Colorado
I'm having trouble with the timesyncd service. It doesn't want to start.

Code: 
# systemctl start systemd-timesyncd

Job for systemd-timesyncd.service failed because a timeout was exceeded.


From /var/log/syslog:
Code: 
Apr 28 10:35:14 proxmox04 systemd[1]: Starting Network Service...
Apr 28 10:35:16 proxmox04 systemd[1]: systemd-timesyncd.service: Start operation timed out. Terminating.
Apr 28 10:35:16 proxmox04 systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=15/TERM
Apr 28 10:35:16 proxmox04 systemd[1]: systemd-timesyncd.service: Failed with result 'timeout'.
Apr 28 10:35:16 proxmox04 systemd[1]: Failed to start Network Time Synchronization.
Apr 28 10:35:16 proxmox04 systemd[1]: systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Apr 28 10:35:16 proxmox04 systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 2.
Apr 28 10:35:16 proxmox04 systemd[1]: Stopped Network Time Synchronization.

I did some reading on the net and someone said that timesyncd relies upon networkd. Well, networkd isn't running and appears to be disabled. I don't recall disabling it. Is this normal for networkd to be disabled?

Code: 
# systemctl status systemd-networkd

● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; vendor preset: enabled)
   Active: activating (start) since Tue 2020-04-28 10:38:14 EDT; 1min 12s ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 8642 ((networkd))
    Tasks: 1 (limit: 4915)
   Memory: 452.0K
   CGroup: /system.slice/systemd-networkd.service
           └─8642 (networkd)
 
Code: 
# systemctl status systemd-timesyncd

● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
           └─disable-with-time-daemon.conf
   Active: activating (start) since Wed 2020-04-29 07:08:39 EDT; 1min 19s ago
     Docs: man:systemd-timesyncd.service(8)
 Main PID: 25241 ((imesyncd))
    Tasks: 1 (limit: 4915)
   Memory: 720.0K
   CGroup: /system.slice/systemd-timesyncd.service
           └─25241 (imesyncd)
 
The last log entries are missing, try with journalctl -u systemd-timesyncd.service to get more information on that service.
 
Code: 
-- Logs begin at Thu 2020-04-02 13:57:53 EDT, end at Wed 2020-04-29 10:20:37 EDT. --
Apr 19 20:18:23 proxmox04 systemd-timesyncd[5287]: Timed out waiting for reply from 12.167.151.1:123 (1.debian.pool.ntp.org).
Apr 19 20:18:34 proxmox04 systemd-timesyncd[5287]: Timed out waiting for reply from 3.217.79.242:123 (1.debian.pool.ntp.org).
Apr 19 20:18:44 proxmox04 systemd-timesyncd[5287]: Timed out waiting for reply from 206.55.191.142:123 (1.debian.pool.ntp.org).
Apr 19 20:53:39 proxmox04 systemd-timesyncd[5287]: Synchronized to time server for the first time 64.22.253.155:123 (0.debian.pool.ntp.org
Apr 28 09:05:16 proxmox04 systemd[1]: Stopping Network Time Synchronization...
Apr 28 09:05:16 proxmox04 systemd[1]: systemd-timesyncd.service: Succeeded.
Apr 28 09:05:16 proxmox04 systemd[1]: Stopped Network Time Synchronization.
Apr 28 09:05:16 proxmox04 systemd[1]: Starting Network Time Synchronization...
Apr 28 09:06:46 proxmox04 systemd[1]: systemd-timesyncd.service: Start operation timed out. Terminating.
Apr 28 09:06:46 proxmox04 systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=15/TERM
Apr 28 09:06:46 proxmox04 systemd[1]: systemd-timesyncd.service: Failed with result 'timeout'.
Apr 28 09:06:46 proxmox04 systemd[1]: Failed to start Network Time Synchronization.
Apr 28 09:06:46 proxmox04 systemd[1]: systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Apr 28 09:06:46 proxmox04 systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 1.

...skipping lines...

Apr 29 10:19:41 proxmox04 systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 949.
Apr 29 10:19:41 proxmox04 systemd[1]: Stopped Network Time Synchronization.
Apr 29 10:19:41 proxmox04 systemd[1]: Starting Network Time Synchronization...
Apr 29 10:21:11 proxmox04 systemd[1]: systemd-timesyncd.service: Start operation timed out. Terminating.
Apr 29 10:21:11 proxmox04 systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=15/TERM
Apr 29 10:21:11 proxmox04 systemd[1]: systemd-timesyncd.service: Failed with result 'timeout'.
Apr 29 10:21:11 proxmox04 systemd[1]: Failed to start Network Time Synchronization.
Apr 29 10:21:11 proxmox04 systemd[1]: systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), scheduling restart.

I gathered my system's update history and nothing lines up with April 19th or April 28th:
Code: 
Start-Date: 2020-02-08  
Commandline: apt-get dist-upgrade
Install: <trimmed>
End-Date: 2020-02-08  

Start-Date: 2020-02-09  
Commandline: apt install ethtool
Install: ethtool:amd64 (1:4.19-1)
End-Date: 2020-02-09 

Start-Date: 2020-02-24  
Commandline: apt install ifupdown2
Install: ifupdown2:amd64 (2.0.1-1+pve4), python-argcomplete:amd64 (1.8.1-1, automatic)
Remove: ifupdown:amd64 (0.8.35+pve1), ifenslave:amd64 (2.9)
End-Date: 2020-02-24  

Start-Date: 2020-02-26  
Commandline: apt install parted
Install: libparted2:amd64 (3.2-25, automatic), parted:amd64 (3.2-25)
End-Date: 2020-02-26
 
If you try to start the service with debug it might give more information. But it looks like the timesyncd can't update its time.
sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-timesyncd
Code: 
sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-timesyncd
 
Code: 
# SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-timesyncd

Failed to get link NTP servers: No data available
Bus bus-api-timesync: changing state UNSET → OPENING
Bus bus-api-timesync: changing state OPENING → AUTHENTICATING
Added new server 72.49.13.172.
Added new server 0.debian.pool.ntp.org.
Added new server 1.debian.pool.ntp.org.
Added new server 2.debian.pool.ntp.org.
Added new server 3.debian.pool.ntp.org.
systemd-timesyncd running as pid 10334
Selected server 72.49.13.172.
Resolving 72.49.13.172...
Bus bus-api-timesync: changing state AUTHENTICATING → HELLO
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName cookie=2 reply_cookie=0 signature=su error-name=n/a error-message=n/a
Resolved address 72.49.13.172:123 for 72.49.13.172.
Selected address 72.49.13.172:123 of server 72.49.13.172.
Connecting to time server 72.49.13.172:123 (72.49.13.172).
Sent NTP request to 72.49.13.172:123 (72.49.13.172).
Got message type=method_return sender=org.freedesktop.DBus destination=:1.282916 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a
Bus bus-api-timesync: changing state HELLO → RUNNING
Got message type=signal sender=org.freedesktop.DBus.Local destination=n/a path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.Local member=Connected cookie=4294967295 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Got message type=signal sender=org.freedesktop.DBus destination=:1.282916 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Got message type=signal sender=org.freedesktop.DBus destination=:1.282916 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=3 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Got message type=method_return sender=org.freedesktop.DBus destination=:1.282916 path=n/a interface=n/a member=n/a cookie=4 reply_cookie=2 signature=u error-name=n/a error-message=n/a
Successfully acquired requested service name.
NTP response:
  leap         : 0
  version      : 4
  mode         : 4
  stratum      : 2
  precision    : 0.000002 sec (-19)
  root distance: 0.057655 sec
  reference    : n/a
  origin       : 1588248274.964
  receive      : 1588248274.988
  transmit     : 1588248274.988
  dest         : 1588248274.969
  offset       : +0.021 sec
  delay        : +0.005 sec
  packet count : 1
  jitter       : 0.000
  poll interval: 64
  adjust (slew): +0.021 sec
  status       : 24577 sync
  time now     : 1588248274.973
  constant     : 2
  offset       : +0.021 sec
  freq offset  : +8883226 (+135 ppm)
interval/delta/delay/jitter/drift 64s/+0.021s/0.005s/0.000s/+135ppm
Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/timesync1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=3 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Synchronized to time server for the first time 72.49.13.172:123 (72.49.13.172).
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back