Ubuntu 22.04 LTS Time Drift Because NTP Sync Is Inactive

📖 ~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 time drifts, causing TLS, cron, and distributed system authentication failures.

Environment & Reproduction

Appears on Ubuntu 22.04 LTS where systemd-timesyncd is disabled or blocked by network policy.

Root Cause Analysis

NTP client inactive or unable to reach configured time servers.

Quick Triage

Check whether NTP synchronization is enabled and server reachability works.

Step-by-Step Diagnosis

Inspect timesyncd service logs and source server selection behavior.

Solution – Primary Fix

Enable NTP sync and restart timesyncd with valid upstream servers.

Solution – Alternative Approaches

Deploy chrony for environments requiring advanced drift controls and local stratum hierarchy.

Verification & Acceptance Criteria

timedatectl reports synchronized clock and offset remains within acceptable SLA.

Rollback Plan

Restore prior NTP config if new upstream servers are unreachable.

Prevention & Hardening

Monitor NTP sync health and alert on drift thresholds across fleet nodes.

Related Errors & Cross-Refs

Related to certificate validity errors and Kerberos timestamp skew problems.

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

View all Ubuntu 22.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

See timedatectl and systemd-timesyncd man pages with Ubuntu time sync docs.