router-service-recovery

Diagnose and repair m5-router.service startup failures and port 8080 conflicts.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/crycriM/hermes-skills --skill router-service-recovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: router-service-recovery
Source: https://github.com/crycriM/hermes-skills/tree/main/mlops/router-service-recovery
Command: npx skills add https://github.com/crycriM/hermes-skills --skill router-service-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When m5-router.service fails to start, this Skill provides a repeatable workflow to identify and fix common causes such as INI parse errors (orphan lines), invalid preset flags, and port conflicts that block GUI model selection.

Core Features & Use Cases

  • Inspect systemd journal for m5-router errors and identify common failure modes, including orphan lines in the router-preset.ini and invalid llama-server flags.
  • Clean and validate router-preset.ini to ensure every key is a valid llama-server CLI flag and each model section contains required keys, removing orphan lines and invalid entries.
  • Detect and resolve port conflicts on 8080 by listing listening processes and terminating rogue llama-server instances as needed, then verify exclusive binding.
  • Restart the router service and confirm model loading via the /v1/models endpoint; verify model parameters (RoPE, context length) per architecture.
  • Optional: guidance on customizing chat templates and switching distrobox containers if necessary.

Quick Start

Follow the step-by-step routine to diagnose and recover m5-router.service by inspecting logs, cleaning preset ini, freeing port 8080, restarting the service, and validating loaded models.

Frequently Asked Questions about router-service-recovery

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

FAQPage Schema
Why does m5-router.service fail to start and block GUI model selection?

m5-router.service startup failures are commonly caused by orphan lines in router-preset.ini, invalid llama-server flags, or port 8080 conflicts with rogue llama-server processes, which block GUI model selection.

How do I fix port 8080 conflicts with rogue llama-server processes on Linux?

Resolve port 8080 conflicts by listing listening processes, terminating rogue llama-server instances, and verifying exclusive binding before restarting m5-router.service.

How do I clean and validate router-preset.ini for m5-router?

Clean router-preset.ini by removing orphan lines and invalid entries, ensuring every key is a valid llama-server CLI flag and each model section contains required keys.

How do I verify model loading after restarting m5-router.service?

Verify model loading after restarting m5-router.service by querying the /v1/models endpoint and checking model parameters like RoPE and context length per architecture.

What causes orphan lines in router-preset.ini and how do they affect systemd?

Orphan lines in router-preset.ini cause INI parse errors that trigger m5-router.service startup failures in systemd journals, requiring removal of invalid entries.

Does m5-router recovery provide guidance on customizing chat templates and distrobox containers?

Yes, m5-router service recovery includes optional guidance on customizing chat templates and switching distrobox containers if necessary during the troubleshooting workflow.