router-troubleshooting

To fix a router service startup failure when port 8080 is blocked, you need to stop the m5-router service, terminate rogue llama-server processes occupying the port, and restart the service to restore availability.

Your router GUI shows no models because orphaned INI entries and rogue processes disrupt the configuration. Cleaning these problematic INI entries and restarting the router service restores normal GUI operation and model visibility.

The best way to clean orphaned INI entries in an m5-router deployment is to run a deterministic recovery workflow that stops services, removes the invalid configuration data, and verifies the service status before restarting.

To terminate rogue llama-server processes blocking port 8080, execute a process-management sequence to stop the services, kill the conflicting processes, and verify the port bindings are cleared before restarting the router.

Yes, router troubleshooting requires verifying port 8088 for GUI operation. After cleaning INI entries and terminating rogue processes, you must validate the router configuration to ensure port 8088 is correctly used for the GUI.

No, this router recovery workflow is specifically designed for m5-router deployments experiencing startup failures, missing GUI models, or port 8080 conflicts, rather than general systemd service failures.