Time Drift and NTP Synchronization Problems

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

System clock drifts; TLS, package signatures, and scheduled jobs fail unpredictably.

Environment & Reproduction

Seen on VMs with unstable host clock, blocked NTP egress, or conflicting time daemons.

Root Cause Analysis

NTP cannot reach sources, incorrect timezone/hardware clock settings, or daemon conflicts (`chrony` vs `systemd-timesyncd`).

Quick Triage

Confirm only one time synchronization service is active.

Step-by-Step Diagnosis

Run `timedatectl status`, inspect `systemctl status systemd-timesyncd` or `chronyd`, and check firewall/NTP reachability.

Solution – Primary Fix

Enable preferred NTP daemon, configure reachable servers, and force synchronization; ensure UTC hardware clock on servers.

Solution – Alternative Approaches

Use internal stratum sources in restricted networks and tune polling intervals for VM workloads.

Verification & Acceptance Criteria

Clock offset remains low; `timedatectl` reports synchronized status and TLS errors disappear.

Rollback Plan

Restore prior NTP config and disable recently introduced conflicting time services.

Prevention & Hardening

Monitor clock drift and enforce baseline NTP settings across all Ubuntu nodes.

Related Errors & Cross-Refs

Certificate not yet valid/expired, apt signature time errors, and cron scheduling anomalies.

Related tutorial: View the step-by-step tutorial for Ubuntu 26.04 LTS.

View all Ubuntu 26.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu time synchronization docs and chrony/systemd-timesyncd manuals.