time-sync-diagnosis

Diagnose Linux time synchronization failures by auditing services, network connectivity, and kernel clock sources.

3|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill time-sync-diagnosis-openeuler-mirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: time-sync-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/time-sync-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill time-sync-diagnosis-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, systemctl, ss, chronyc, ntpq, mtr, nc, and includes scripts (resource) components.

What problem does it solve?

This Skill resolves complex Linux time synchronization issues by automating the identification of service conflicts, network connectivity problems, and protocol-level failures.

Core Features & Use Cases

  • Multi-Stage Diagnosis: Executes a structured four-phase workflow covering service status, network path analysis, kernel clocksource auditing, and protocol consistency checks.
  • Automated Root Cause Analysis: Maps symptoms to specific failure scenarios like control plane conflicts, management channel restrictions, or kernel-level jitter.
  • Use Case: When a server experiences clock drift or NTP synchronization failure, this Skill automatically audits the chronyd/ntpd configuration, verifies UDP 123 connectivity, and checks for virtualization steal time to pinpoint the exact cause.

Quick Start

Run the time-sync-diagnosis skill to perform a full system audit and generate a root cause report for the current time synchronization failure.

Frequently Asked Questions about time-sync-diagnosis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Linux NTP clock drift and chronyd synchronization failures automatically?

To troubleshoot Linux clock drift, this Skill automates a four-phase audit of system services, network connectivity, kernel clocksources, and chronyd configuration to pinpoint the exact root cause.

Why does my Linux server fail to synchronize time after switching from ntpd to chronyd?

Linux time synchronization fails during service transitions due to control plane conflicts or management channel restrictions. This Skill audits protocol consistency and service status to identify the specific conflict.

Can I diagnose systemd-timesyncd and kernel clocksource issues in a virtualized environment?

Yes, you can diagnose virtualized environments. The Skill audits kernel clocksource stability and checks for virtualization steal time to detect protocol failures and kernel-level jitter.

What is the best way to verify UDP 123 connectivity for NTP synchronization troubleshooting?

The best way to verify UDP 123 connectivity is through automated network path analysis. This Skill uses standard tools like ss and mtr to validate management channels and network reachability.

Do I need to install specialized tools to perform a Linux time synchronization system audit?

You do not need specialized tools, but standard Linux diagnostic utilities like systemctl, chronyc, ntpq, ss, and bash are required to execute the comprehensive protocol and infrastructure analysis.

How to find the root cause of ntpq peers showing no reachability for remote NTP servers?

Finding the root cause of ntpq reachability issues requires auditing network paths and service configurations. This Skill maps the symptoms to failure scenarios like network restrictions or service conflicts.