offline-power-fault-diagnosis

Correlate iBMC, OS, and system logs to diagnose server power hardware failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill resolves the ambiguity in server power failure analysis by providing a structured, evidence-based methodology to trace unexpected shutdowns, PSU hardware faults, and voltage anomalies to their physical root causes.

Core Features & Use Cases

  • Multi-Source Correlation: Automatically aligns iBMC hardware logs, OS messages, and InfoCollect data to build a precise fault timeline.
  • Physical Root Cause Localization: Moves beyond generic error messages to identify specific faulty components like PSU modules, VRM units, or external PDU issues.
  • Use Case: When a server experiences an unexpected power loss, use this skill to determine if the failure was caused by a failing PSU hardware component, a thermal protection trip, or an external power supply interruption.

Quick Start

Use the offline-power-fault-diagnosis skill to analyze the server logs located in the /tmp/logs directory and generate a root cause report.

Frequently Asked Questions about offline-power-fault-diagnosis

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

FAQPage Schema
How do I diagnose server power hardware failures using iBMC and system logs?

Diagnose server power hardware failures by correlating iBMC, OS, and system logs to identify physical root causes. This structured log analysis reconstructs fault propagation chains and validates evidence against hardware sensor data to pinpoint specific faulty components.

What is the best way to find the root cause of unexpected server power loss?

Finding the root cause of unexpected server power loss requires multi-source correlation of iBMC hardware logs, OS messages, and InfoCollect data. This approach builds a precise fault timeline to determine if a failing PSU, thermal trip, or external PDU caused the shutdown.

Why do my PSU module faults and voltage irregularities show generic errors?

PSU module faults and voltage irregularities show generic errors because standard logs lack physical context. Physical root cause localization moves beyond generic messages to identify specific faulty components like PSU modules or VRM units by validating evidence against hardware sensor data.

Can I analyze server hardware logs for PSU redundancy failures offline?

Yes, you can analyze server hardware logs for PSU redundancy failures offline by pointing the skill to the log directory. It processes the collected iBMC, OS, and InfoCollect data to generate a root cause report without requiring a live connection to the server.

How do I reconstruct a fault propagation chain for voltage anomalies?

Reconstruct a fault propagation chain for voltage anomalies by aligning iBMC hardware logs, OS messages, and system logs into a precise timeline. This structured log analysis validates the sequence of events against hardware sensor data to localize the physical root cause.