· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices
Describe the issue
Still after the last update, yes it’s snappier but after “playing “ around in the Roon remote app, iPad, adding a new album and checking the queue, it was 30 tracks left music stops and the message is as always: lost audio endpoint. This is after 17 hours of use. Please fix this issue. And by the way, new Qobuz favorites are not synced to Roon even if I manually try to activate the blue script saying, syncing libraries. Looks like you have some more work to do.
We’re sorry to hear you’re having issues. We’ll need a little more action to take action on this reported symptom, however.
Your previous logs showed memory pressure accumulating in RoonServer; fortunately this had been relieved by the most recent release, from what we see in logs. However, disconnection events are still occuring with a local cause, probably in the network topology itself.
Roon logs show socket errors accumulating after a startup on 7/9. The server lost its network connection to both the local network and the internet and began retrying connections:
07/09 18:41:31 Warn: [realtime] failed to get time: Name or service not known
This never resolved until the unit was restarted.
That’s not a direct symptom of memory pressure and we don’t see any cause internal to Roon. This also wouldn’t be specific to the 218 or any Meridian protocol; these are basic TCP connection failures.
We’ve discussed your network setup before, but can you precisely describe which switches and equipment (make/model) sit between the Nucleus, the router, the 218, and the internet?