How to Fix System Clock Synchronization Issues on Linux

Fixing System Clock Synchronization Issues on Linux

An out-of-sync system clock on your Breeze causes certificate validation failures, authentication errors, log timestamp mismatches, and cron job timing problems. Keeping accurate time is essential for production servers.

Check Current Time Status

timedatectl status
date
hwclock --show

Look for discrepancies between system time, hardware clock, and whether NTP synchronization is active.

Enable NTP Synchronization

Modern Linux distributions use systemd-timesyncd or chrony for time synchronization:

# Enable systemd-timesyncd
sudo timedatectl set-ntp true
sudo systemctl restart systemd-timesyncd
timedatectl timesync-status

Using Chrony (Recommended)

Chrony is more accurate and handles intermittent connectivity better:

sudo apt install chrony
sudo systemctl enable --now chrony

Verify synchronization:

chronyc tracking
chronyc sources -v

Force Immediate Sync

If the clock is significantly off, force a step correction:

sudo chronyc makestep

Set the Correct Timezone

timedatectl list-timezones | grep America
sudo timedatectl set-timezone America/New_York

Common Issues

• Firewall blocking NTP -- ensure UDP port 123 is open outbound
• Virtualization drift -- VPS clocks can drift faster than physical servers; use chrony with a lower polling interval
• Conflicting services -- do not run both timesyncd and chrony simultaneously

After fixing synchronization, verify with timedatectl that "System clock synchronized: yes" is displayed.