Hi! What’s not quite right with Roon?
· None of the above quite fits
None of the above quite fits
· None of these quite match
Tell us what's going on
· ROCK RoonAppliance crash loop every 303 seconds (exit code 136); RoonOS stays online.
Configuration: RoonOS 3.0 build 287 production; Roon Server 2.74 build 1716 production; Windows 11 Roon Remote. OS update check reports up-to-date.
RoonGoer repeatedly logs: 'watchdog connection closed (length-prefix EOF)' and 'child exited code=136 (abnormal) after 303s of life', then automatically starts RoonAppliance again. Roon Server logs confirm new startup sequences approximately every 5 minutes, coinciding with Remote disconnections.
Important: RoonOS itself is not rebooting. Web administration showed OS uptime 50287 seconds (about 14 hours), while Roon Server uptime was only 13 seconds. SMB remained reachable. A short test completed 25/25 TCP connections to ROCK and 25/25 to the router without failure.
Several server logs end immediately after phase2census resumes the same snapshot at batch index 127 after track 8598578. This is correlation, not a confirmed cause. Library statistics: about 55846 tracks and 8443 albums.
No database reset, rollback, reinstall or storage changes were performed in this diagnostic session. Please investigate exit code 136 and the repeated phase2census resume point. Is this a known build 1716 issue, and is there a supported fix or safe workaround that preserves the database?
Original RoonGoer/RoonServer logs are available for a private secure upload or account diagnostics; I have not posted full logs publicly because they contain account-related data.
Tell us about your home network
· ROCK is connected by Ethernet using a static IPv4 configuration. Windows 11 Roon Remote is connected by Wi-Fi on the same local subnet. A VPN TUN adapter is active on the Windows PC; the routing table has a more-specific direct route for the local subnet. Router/switch make and model have not been verified. TCP reachability tests to ROCK and the router completed 25/25 connections each with no failures. RoonGoer logs independently confirm repeated local RoonAppliance process exits (code 136) on ROCK.