linux-server-troubleshooting

Diagnose Linux server evidence bundles and host-level failures with evidence-backed root-cause analysis.

1|Updated Jan 18, 2024
One-click install
npx skills add https://github.com/brockners/ciscolive --skill linux-server-troubleshooting-brockners
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linux-server-troubleshooting
Source: https://github.com/brockners/ciscolive/tree/main/CLUS26/EXP9/skills/linux-server-troubleshooting
Command: npx skills add https://github.com/brockners/ciscolive --skill linux-server-troubleshooting-brockners

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Diagnosing Linux server failures from collected evidence bundles, sosreports, and log archives is slow and error-prone, especially when host issues masquerade as Kubernetes or application problems. This Skill applies a structured, evidence-driven troubleshooting methodology to find root causes without jumping to conclusions. ## Core Features & Use Cases - Evidence Bundle Analysis: Ingests tarballs, sosreports, syslog/journalctl/dmesg logs, systemd state, and command outputs while preserving original artifacts as read-only. - Hypothesis-Driven Diagnosis: Maintains competing hypotheses with supporting and refuting evidence, timelines, and confidence levels across kernel, storage, network, resource, security, and container runtime domains. - Kubernetes Node Correlation: Correlates kubelet, containerd, CNI, and node lease evidence to determine whether host issues cause cluster symptoms. - Use Case: Given a sosreport from a node where pods keep evicting, the Skill identifies an OOM condition tied to a specific cgroup, builds the timeline, and cites exact log lines as evidence. ## Quick Start Use the linux-server-troubleshooting skill to analyze the evidence bundle in data/ and produce an evidence-backed root-cause analysis with a timeline and next actions.

Frequently Asked Questions about linux-server-troubleshooting

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

FAQPage Schema
How do I troubleshoot a Linux server from a sosreport or log bundle?▼

Extract the archive into scratch space, inventory logs and command outputs, then run broad keyword searches for errors, OOM, panics, and disk issues before forming hypotheses. The Skill guides this workflow and produces an evidence-backed root-cause analysis with a timeline.

How to find the root cause of OOM kills on a Linux host?▼

Identify the victim process, cgroup or container, allocation context, node memory, and swap state from kernel logs, then correlate with kubelet eviction messages and application restarts. The Skill's resource pressure lens walks through exactly this correlation.

Can this analyze Kubernetes node problems from host logs?▼

Yes, it correlates kubelet, containerd, CNI, and node lease evidence with host DNS, NTP, firewall, and certificate state to determine whether the Linux host causes cluster symptoms. For pure Kubernetes object state, it defers to a Kubernetes troubleshooting workflow.

Does it run live commands on my production server?▼

No, it prefers offline analysis of collected evidence and read-only tooling like rg, tar, jq, and journalctl --file. Live commands are used only when explicitly requested, and it avoids recommending disruptive actions like restarts or reboots without supporting evidence.

What evidence formats does Linux server troubleshooting support?▼

It handles tarballs, sosreports, syslog/messages, journalctl files, kern.log, dmesg, systemctl output, unit files, JSON command output, container runtime logs, and network or storage command captures. Rotated and compressed logs are unpacked into scratch space for analysis.