CentOS Stream 9 – Common Problem 244 – Diagnosis and Fix

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

Clock jumps after WAN flap

Environment & Reproduction

chronyd makestep aggressive while NTP servers were unreachable.

Root Cause Analysis

Default makestep allows large step after recovery, breaking TLS.

Quick Triage

chronyc tracking shows large System time correction.

Step-by-Step Diagnosis

Run: chronyc tracking; chronyc sources -v; journalctl -u chronyd.

Solution – Primary Fix

Set makestep 1.0 3 in /etc/chrony.conf and restart chronyd.

Solution – Alternative Approaches

Use slewonly via chronyc to limit corrections post-boot.

Verification & Acceptance Criteria

chronyc tracking offset stays within milliseconds during outages.

Rollback Plan

Restore original makestep setting and restart chronyd.

Prevention & Hardening

Deploy at least three local stratum-2 sources for redundancy.

Related Errors & Cross-Refs

Pairs with TLS certificate not yet valid and Kerberos clock skew.

Related tutorial: View the step-by-step tutorial for centos-stream-9.

View all centos-stream-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

chrony.conf(5) and chronyc(1).