agentleFS
dmzoneilldmzoneill/skills/investigate-service-issues/SKILL.md

investigate-service-issues

Skill2 starsChanged 20 days agoApache-2.0View on GitHub

Debug systemd service failures - status, journal logs, boot issues, failed units. Optional auto-restart. Use when user says "service down", "check systemd", "investigate service", or "aa-workflow not running".

The file

Files
SKILL.md

Investigate Service Issues

Debug systemd service failures and investigate issues. Checks status, journal logs, boot-level issues, failed units. Optional auto-restart.

Inputs

InputTypeDefaultPurpose
service_namestring-Service to check (e.g., aa-workflow-mcp). Empty = all failed
sincestring1hLog time window (1h, 30m, 1d)
auto_restartboolfalseRestart failed services
check_all_failedbooltrueList all failed systemd units

Persona

Load devops persona (systemd tools: systemctl, journalctl).

Workflow

1. Bootstrap

  • persona_load("devops")

2. System Info

  • hostnamectl_status() — hostname, OS
  • timedatectl_status() — time sync (NTP)

3. Failed Units

  • systemctl_list_units(pattern="--failed") — all failed units
  • systemctl_list_unit_files(pattern="aa-workflow-*") — workflow units

4. Service-Specific (if service_name)

  • systemctl_is_active(unit="{service}.service")
  • systemctl_is_enabled(unit="{service}.service")
  • systemctl_status(unit="{service}.service")
  • journalctl_unit(unit="{service}.service", lines=50)

5. Broad Log Analysis

  • journalctl_logs(priority="err", since=since, lines=30)
  • journalctl_boot(boot="0", priority="warning", lines=20)

6. Ollama Check

  • ollama_status() — inference server

7. Auto-Restart (if auto_restart and service_name)

  • systemctl_daemon_reload()
  • systemctl_restart(unit="{service}.service")
  • systemctl_status(unit="{service}.service") — verify

8. Analyze

Parse for: inactive service, not enabled, failed units count, OOM, permission denied, connection refused, time not synced, restart success.

9. Log

  • memory_session_log("Investigated service issues", ...)

10. Failure Patterns

  • segfault/core dump → binary compatibility
  • "too many open files" → ulimit, LimitNOFILE
  • learn_tool_fix(...) for recurring patterns

Output

Report: issues, recommendations, service status, recent logs, failed units, restart result, system info.

Quick Actions

  • systemctl_restart(unit="{service}.service")
  • journalctl_unit(unit="{service}.service", lines=100)
  • skill_run("manage_local_services", '{"action": "status"}')

Chains To

  • manage_local_services

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.