π ~1 min read
Table of contents
Symptom & Impact
Time drift causes authentication failures, certificate issues, and distributed job instability.
Environment & Reproduction
Common on isolated networks with unreachable NTP sources.
timedatectl
chronyc tracking
Root Cause Analysis
chronyd cannot reach or trust configured servers due to firewall, DNS, or bad source list.
Quick Triage
Validate service state and configured source list.
systemctl status chronyd
grep -E '^(server|pool)' /etc/chrony.conf
Step-by-Step Diagnosis
Inspect source reachability and service logs.
chronyc sources -v
firewall-cmd --list-services
journalctl -u chronyd -n 100

Solution – Primary Fix
Set valid NTP servers, ensure UDP 123 access, and restart chronyd.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
sudo sed -i 's/^pool /#pool /' /etc/chrony.conf
echo 'server time.example.net iburst' | sudo tee -a /etc/chrony.conf
sudo systemctl restart chronyd

Solution – Alternative Approaches
Use local stratum server for disconnected environments.
Verification & Acceptance Criteria
System reports synchronized clock and stable offset.
timedatectl status
chronyc tracking
Rollback Plan
Revert chrony.conf from backup and restart service.
Prevention & Hardening
Monitor drift thresholds and alert when synchronization state changes.
Related Errors & Cross-Refs
Related to Kerberos skew errors and TLS handshake validity failures.
Related tutorial: View the step-by-step tutorial for rhel-10.
View all rhel-10 tutorials on the Tutorials Hub β
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Chrony administration guidance for RHEL and enterprise timekeeping.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today β we respond within one business day.