Hi @Juul_Gijsbers,
Thank you for your patience and our apologies for not sending an update. We’ve identified two issues within logs, either one (or both) of which might be responsible for the behavior you’re experiencing.
However, RoonServer didn’t log any crashes within the sets you’ve shared, suggesting the crash is either fully unmanaged or a different descriptor might help pinpoint the issue better. Does Roon hang on the mobile client at all? Do you have any crash reports from the laptop OS that you can share as well?
To business - the first culprit here is one of the mechanisms for database performance decline that we’re investigating in this thread: ROON painfully slow after update with large library sizes [Roon Investigating]
Specifically, Roon is choking up while it analyzes your library content.
The second culprit is what appears to be a cyclical network timeout on the part of your RoonServer laptop. These timeouts don’t correlate to the timestamps of the crashes or any other bad behavior in RoonServer logs, but they certainly indicate that Roon is struggling in your audio environment.
Specifically, the Raspberry Pi and several other AirPlay-capable endpoints are timing out during the device discovery protocol. Additionally, your Remotes sometimes time out attempting to connect to the Server as system output Zones in RAATServer logs.
Curiously, Roon is also receiving an internal IP address from somewhere in your LAN as the external IP address field from the UPnP stack on your router. The unmanaged switch isn’t likely to interfere but try a different ethernet port or remove the switch entirely, just to be sure. Additionally, verify your router firmware is updated.
One possible mechanism for the library analysis issue mentioned above concerns Roon’s handling of IPv6. There are numerous failures related to IPv6 device announcement in your logs, suggesting the router isn’t properly handling that nomenclature. Unless you’re relying on IPv6, try turning it off entirely in your router web administration. Please let us know if this relieves any of your symptoms. I also recommend re-verifying that Roon and its processes are added as network firewall exceptions for Windows and any other security software. Please also try changing your DNS server to Cloudflare DNS, Quad9 or Google DNS.
In the meantime, we’ll pull more recent logs once you’ve made the change and see if there’s evidence of reduced network timeout frequency and, as a more direct test, whether there are still analysis issues.