linux-service-triage

Diagnose Linux service failures by analyzing logs, systemd/PM2 status, and permissions.

Updated Aug 23, 2026

Search Tags:#logs #linux #nginx #dns #systemd #pm2 #service-triage

Ready to run

npx skills add https://github.com/chadyi-king/mission-control-workspace --skill linux-service-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: linux-service-triage
Source: https://github.com/chadyi-king/mission-control-workspace/tree/main/skills/linux-service-triage
Command: npx skills add https://github.com/chadyi-king/mission-control-workspace --skill linux-service-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses Linux service issues by collecting relevant logs, status outputs, and permissions to identify root causes and streamline fixes.

Core Features & Use Cases

Evidence gathering: Collects systemd/PM2 status, journal logs, and permission checks to build an actionable triage plan.
Failure classification: Distinguishes between config errors, permission issues, port conflicts, and upstream failures.
Safe fix suggestions: Proposes minimal, verifiable commands to restart services and verify health after changes.

Quick Start

Run the triage workflow against the affected Linux service and apply the recommended minimal fixes, then verify the service is listening on the expected port and DNS/Nginx configurations are sane.

Frequently Asked Questions about linux-service-triage

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

FAQPage Schema

How do I diagnose why a Linux service is failing to start?▼

To diagnose Linux service failures, you need to analyze systemd or PM2 status outputs alongside journal logs to identify root causes like config errors, permission issues, or port conflicts. This process builds an actionable triage plan.

How do I find the root cause of an Nginx proxy or DNS failure on Linux?▼

Finding the root cause of an Nginx proxy or DNS failure involves collecting journal logs and checking service configurations to distinguish between upstream failures and misconfigurations. This classification streamlines the identification of exact issues.

What is the best way to safely restart a failed Linux service after a crash?▼

The best way to safely restart a failed Linux service is to apply minimal, verifiable commands proposed by a triage workflow, then verify the service is listening on the expected port and that configurations are sane.

Can I use PM2 logs to troubleshoot Node.js service issues on Linux?▼

Yes, you can use PM2 logs to troubleshoot Node.js service issues on Linux by gathering PM2 status outputs and logs. This helps classify failures and propose safe, minimal fixes to restore service health.

Why does my Linux service fail after a configuration change?▼

Linux service failures after a configuration change often stem from config errors, permission issues, or port conflicts. Analyzing systemd status and journal logs identifies the specific misconfiguration causing the startup failure.

Does this triage process work for both systemd and PM2 managed services?▼

Yes, this triage process works for both systemd and PM2 managed services by collecting relevant status outputs, journal logs, and permission checks to classify failures and propose safe restart and verification plans across Linux environments.