HydraIssues

Castleviewer geeft volgende melding: Failed to fond application rupelmonde-castle-viewer

Fix (2026-05-07)

Root cause: hydrabody on the rupelmonde body (boom-pickle-38, node-74f9fbf2) crashed at 2026-05-06 05:24 with exit code 2. Its scheduled task trigger is At system start up only, so it never auto-restarted. Without hydrabody running, Sunshine's apps.json kept its stale state — only mercator-talks was registered, rupelmonde-castle-viewer was missing. The Moonlight client (Castleviewer) then fails its app-name lookup with the message above.

Action taken: ran schtasks /run /tn HydraBody on the body. hydrabody started (PID 4436, 15:45:14) and immediately re-registered rupelmonde-castle-viewer with prep-cmd hooks. Verified apps.json now contains both mercator-talks and rupelmonde-castle-viewer.

Follow-ups (separate issues recommended):

• HydraBody scheduled task has no on-failure restart trigger — a single crash takes the body out until the machine reboots.
• fetchHeadsForVenue in hydrabody/pkg/provider/sunshine.go does not set the Authorization header, so it spams HTTP 401 logs every 30s. Doesn't block app registration today (state.Installed fallback covers it), but masks real signal in the logs.