investigate-service-issues

Diagnose systemd service failures by checking status and analyzing journal logs.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dmzoneill/skills --skill investigate-service-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate-service-issues
Source: https://github.com/dmzoneill/skills/tree/main/investigate-service-issues
Command: npx skills add https://github.com/dmzoneill/skills --skill investigate-service-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve issues when systemd services fail to run, ensuring system stability and uptime.

Core Features & Use Cases

  • Service Status Checks: Verifies if a service is active and enabled.
  • Log Analysis: Examines systemd journal logs and boot logs for errors.
  • Automated Restart: Optionally restarts failed services after investigation.
  • Use Case: When a critical application like 'aa-workflow-mcp' stops responding, this Skill can automatically check its status, review recent logs for clues, and attempt a restart if configured.

Quick Start

Investigate why the 'nginx' service is not running and check its logs from the last hour.

Frequently Asked Questions about investigate-service-issues

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

FAQPage Schema
How do I debug systemd service failures using journal logs?

Diagnosing systemd service failures involves checking service status with systemctl and analyzing journal logs with journalctl to find errors. This Skill automates reviewing those logs and boot issues to identify why a service stopped responding.

Why does my systemd service stop running and how can I check its status?

Systemd services often stop due to application crashes or configuration errors. You can check if a service is active and enabled using systemctl, which this Skill automates alongside log analysis to determine why the service stopped running.

Can I automatically restart a failed systemd service after investigating the logs?

Yes, you can automatically restart a failed systemd service after checking its logs. This Skill supports an optional auto-restart feature that attempts to recover services like 'aa-workflow-mcp' once it finishes analyzing the journal logs.

Do I need systemctl and journalctl installed to diagnose systemd service issues?

Yes, you need systemctl and journalctl installed to diagnose systemd service issues. This Skill requires both tools for operational analysis to check service status and examine systemd journal logs for error messages.

What is the best way to investigate systemd boot issues and service errors?

The best way to investigate systemd boot issues is to review the systemd journal and boot logs for errors. This Skill automates that process by checking service status and parsing journalctl output to diagnose why a critical application fails to run.