Playback and connection issues with Roon server on ROCK (ref#57ED93)

What best describes your playback issue?

· Music stops playing unexpectedly

What type of Zone is affected by this problem?

· *All of my Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Only local library *music is affected.

Where is your local content stored?

· Somewhere else on the local network (NAS)

If you move the content from your NAS to a local storage location, do you still experience issues with playback?

· The issue happens for both the NAS storage location and on the secondary storage location

Please try playing content of a lower sample rate (44.1kHz or 48kHz), does this work as expected?

· No, lower sample rates are still affected

Do you have an approximate timestamp of when the issue last occurred?

· I hadn't used my Roon account for several months. I want to use it again (started about a week ago).

What are the make and model of the affected audio device(s) and the connection type?

· Intel i7 NUC (ROCK).

Describe the issue

Since about a week ago, when I load Roon (I have my music library connected from a drive going into a ROCK) music playback suddenly stops and I get disconnected from the Roon server. I then get a message noting that the server cannot be found.

Describe your network setup

ROCK connected to Ethernet, connected to modem. I then have a WiiM connected to the same network. Streaming does work, but the server disconnects after a few minutes.

Hi @Adam_Zulawnik,
Thanks for reaching out to us to ask about this issue. I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.

However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.

First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.

Hi Daniel,

Yes sure. So, it just happened. 9:16 pm AEST. I started my roon remote at 9:14 pm AEST. Started to play a track. When I started looking for a new track, the server was lost.

Adam

Hey @Adam_Zulawnik,

Thanks for sharing the timestamp! Which track did you play specifically? And, could you please bring your ROCK back online so we can enable diagnostics?

We do see traces that point to your ROCK potentially being out of memory, which kills Roon Server, for example:

user.warn kernel: [ 4883.843720] Worker (5) invoked oom-killer: 
user.warn kernel: [ 4883.843748]  out_of_memory+0x246/0x500

A solution you may find could be to increase the RAM within your ROCK from 8GB to 16GB. Here is a resource you can check for RAM compatibility, if needed:

https://www.intel.com/content/www/us/en/support/articles/000087833/intel-nuc.html

Thank you! :raised_hands:

Hi Ben!

Sorry, I switched it off over night. Back on now. I played a 2NE1 song and then the server froze when I tried so search for a BigBang album.

I see, so it may be the RAM? I tested on my laptop (i7 with 16G RAM) a few days ago and it seemed ok, so I guess that would explain it?

Thank you!

Adam

1 Like

Hey @Adam_Zulawnik,

Thanks for the follow-up! We did see the unmanaged crash around the time stamp you shared, but no obvious traces stating it was a memory-related crash.

Another option for testing - if you temporarily cut your library in half, do you still run into the same issues?

Hi Ben,

I just upgraded my RAM to 2x 8GB. I will test and let you know how things go!

Cheers,
Adam

Thanks for the update @Adam_Zulawnik , do let us know your feedback once you’ve had a chance to test further!

Hi Ben! Just reporting back. The issue seems to have been caused by insufficient RAM. After changing to 2x 8GB, there are no issues. Thank you for your support!
Adam

Hi @Adam_Zulawnik,
That’s great to hear. I’m glad the RAM upgrade helped. I’ll mark this thread as solved for you. It’ll remain open a few more days in case the fix doesn’t hold.