Debian 12 NTP Sync Not Active and Clock Drift Increases

📖 ~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

Time-sensitive services fail intermittently due to mounting clock drift.

Environment & Reproduction

Observed after hypervisor pauses, firewall changes, or disabled time services.

Root Cause Analysis

NTP client is misconfigured, blocked, or not running, so drift accumulates.

Quick Triage

Check current offset, sync status, and active time source selection.

Step-by-Step Diagnosis

Inspect time daemon logs and network reachability to configured peers.

Solution – Primary Fix

Re-enable and configure approved NTP service, then verify stable synchronization.

Solution – Alternative Approaches

Switch to chrony for environments with variable latency or intermittent links.

Verification & Acceptance Criteria

Offset remains within policy and synchronized state persists over time.

Rollback Plan

Revert recent daemon or firewall changes if synchronization degrades further.

Prevention & Hardening

Standardize time sources and alert on sustained drift across fleet nodes.

Related Errors & Cross-Refs

Closely related to apt release-validity and certificate timestamp failures.

Related tutorial: View the step-by-step tutorial for Debian 12.

View all Debian 12 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Debian time synchronization and chrony/systemd-timesyncd references.