system-resource-diagnosis

Diagnoses Linux resource failures by analyzing limits, IPC resources, inotify handles, and kernel logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves complex Linux system resource bottlenecks by identifying the root cause of failures like process limit exhaustion, memory leaks, IPC resource depletion, and kernel-level errors.

Core Features & Use Cases

  • Automated Resource Analysis: Collects and correlates system metrics, ulimit configurations, and kernel logs to pinpoint the source of resource contention.
  • Scenario-Based Diagnosis: Provides specialized diagnostic paths for common issues including fork failures, stack overflows, IPC resource exhaustion, and inotify handle limits.
  • Use Case: When a production service reports "Resource temporarily unavailable" or "Segmentation fault," this Skill analyzes the system state to determine if the issue stems from misconfigured limits, resource leaks, or kernel-level restrictions.

Quick Start

Use the system-resource-diagnosis skill to analyze the system state for the last hour to identify the cause of recent fork failures.

Frequently Asked Questions about system-resource-diagnosis

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

FAQPage Schema
How do I diagnose Linux system resource failures causing process exhaustion or fork errors?

To diagnose Linux system resource exhaustion, this Skill analyzes process limits, IPC resources, inotify handles, and kernel logs to pinpoint root causes of fork errors. It correlates system-wide metrics to identify resource contention.

What causes a "Resource temporarily unavailable" error and how is it analyzed?

A "Resource temporarily unavailable" error is analyzed by checking ulimit configurations and system state to determine if it stems from misconfigured limits or resource leaks. The Skill provides specialized diagnostic paths for such production failures.

Do I need root access to troubleshoot kernel logs and IPC resource depletion?

Yes, you need root-level access to troubleshoot kernel logs and IPC resource depletion. Root permissions are required to execute diagnostic scripts and parse system-wide resource metrics effectively.

Can I identify the cause of memory allocation errors and stack overflows from kernel logs?

Yes, you can identify memory allocation errors and stack overflows by parsing kernel logs. The Skill targets scenarios involving memory leaks and kernel-level restrictions to resolve complex Linux system bottlenecks.

What is the best way to analyze inotify handle limits during a service outage?

The best way to analyze inotify handle limits is by collecting and correlating automated system metrics. This Skill examines inotify handles alongside IPC resources to identify if kernel-level restrictions cause outages.