router-service-recovery

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.