I have the roon server log file but would prefer not to post it to the forum. It has what appear to be session ids and such in it. If that would help please pm with details on what to do to get the log file to you!
Ok so on a whim I decided to restart my NAS. Whatever was going on its resolved - strange but I guess now I know.
Go ahead and mark this as resolved / whatever.
And for the record I had signed out / in on both qobuz and tidal. I was able to use their connect feature to play music - it seems to me to have had something to do with roon itself.
Glad to hear that the reboot cleared things up and the system is now working. If you notice any further errors please let us know and we can take another look, thanks!
So I think I know what was going on. After the reboot I was getting some really strange status/state from the cloud sync - I had the NAS re-syncing a bunch of data up to cloud storage for off-site backup purposes.
The failure I tracked down - DNS resolution failure. I run something called pihole and they have a default configuration that starts blocking dns requests if you exceed 1000 requests in 60 seconds.
The error ( I removed a bunch of things since it seems sensitive )
That error feels like its wrong - how do you have corrupt media with a network stream? I feel like the Roon software was hiding the actual failure. Anyway I don’t know for sure because there is nothing in the logs but I think the issue I was experiencing was actually due to the dns rate limit / blocking that was going on. Once I removed that rate limit in my pihole server both issues were fully resolved.
For whatever thats worth And to be clear, it was for sure not roon causing the issue, it was how synology’s nas sync was flooding the dns server with too many requests! Each file being sent to the cloud storage was a new request - with some number in parallel and many thousands of files to sync.