I noticed that one of my servers drifted 5 minutes into the future.
Four minutes and a half, to be precise.
Turned out, it never had a time sync thing enabled. Weird, should I do that manually? I cannot recall me enabling this on some other machine. Yet, all other machines have it enabled.
timedatectl
Local time: Wed 2025-08-13 10:05:08 EEST
Universal time: Wed 2025-08-13 07:05:08 UTC
RTC time: Wed 2025-08-13 07:05:08
Time zone: Europe/Kyiv (EEST, +0300)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
systemctl status systemd-timesyncd
○ systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disabled; preset: enabled)
Active: inactive (dead)
Docs: man:systemd-timesyncd.service(8)
All it took, is just:
sudo systemctl enable --now systemd-timesyncd
And now it lives in the present:
Created symlink '/etc/systemd/system/dbus-org.freedesktop.timesync1.service' → '/usr/lib/systemd/system/systemd-timesyncd.service'.
Created symlink '/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service' → '/usr/lib/systemd/system/systemd-timesyncd.service'.
timedatectl status
Local time: Wed 2025-08-13 10:03:26 EEST
Universal time: Wed 2025-08-13 07:03:26 UTC
RTC time: Wed 2025-08-13 07:03:26
Time zone: Europe/Kyiv (EEST, +0300)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
I wonder whether it influenced anything. This server being living in the future.
E.g. how would it resolve syncthing conflicts? Its files are always newer, right?