Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Flat network. QNAP connected to same switch as wireless access points and endpoints.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
HifiBerry DAC+ Pro running Ropieee, wired ethernet
Orchard Audio PecahPi DAC running Ropieee, wired ethernet
Windows 10 connected to Schiit BiFrost DAC via USB, wired ethernet
Description Of Issue
I first raised this as a potential issue with the QNAP build of Roon but having investigated with Chris Rieke, he has identified errors that point to a generic issue rather than a QNAP issue. Chris has also tagged support in the relevant thread.
The issue is that every couple of days Roon will hang and clients will not respond. If I login to the server whilst this is happening I can see that the RoonServer process is taking up 100% of one core and 8GB of RAM - the process has runaway basically. Occasionally this will resolve itself after 5 minutes or so, but usually I have to manually restart the Roon service.
Chris has identified the following recurring error in my logs:
11/05 08:56:08 Critical: scx: in OnExit: System.NullReferenceException: Object reference not set to an instance of an object
at Sooloos.Broker.RoonApi.TransportService_2.EndpointToJson (Sooloos.Broker.Api.Endpoint ep) [0x00028] in <c3f83e578441427188bf8c55d2a55639>:0
at Sooloos.Broker.RoonApi.TransportService_2.<ZoneToJson>b__37_3 (Sooloos.Broker.Api.Endpoint x) [0x00000] in <c3f83e578441427188bf8c55d2a55639>:0
at System.Linq.Enumerable+SelectListIterator`2[TSource,TResult].MoveNext () [0x00048] in <ae162b7061064bfaa55021254699ac67>:0
at System.Collections.Generic.List`1[T]..ctor (System.Collections.Generic.IEnumerable`1[T] collection) [0x00077] in <370a0c27f4b74d1a81431037df6d75bf>:0
at Base.JList..ctor (System.Collections.Generic.IEnumerable`1[T] l) [0x00000] in <e6fb1b8f00f2413595e2298124e24ad2>:0
at Sooloos.Broker.RoonApi.TransportService_2.ZoneToJson (Sooloos.Broker.Api.Zone zone, System.Boolean for_diff) [0x00102] in <c3f83e578441427188bf8c55d2a55639>:0
at Sooloos.Broker.RoonApi.TransportService_2._ActuallyChanged (Sooloos.Broker.Api.Zone zone) [0x00000] in <c3f83e578441427188bf8c55d2a55639>:0
at Sooloos.Broker.RoonApi.TransportService_2.<_update_subscriptions>b__25_0 (Sooloos.Broker.Api.Zone x) [0x00000] in <c3f83e578441427188bf8c55d2a55639>:0
at System.Linq.Enumerable+WhereEnumerableIterator`1[TSource].ToList () [0x0001b] in <ae162b7061064bfaa55021254699ac67>:0
at System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable`1[T] source) [0x0001f] in <ae162b7061064bfaa55021254699ac67>:0
at Sooloos.Broker.RoonApi.TransportService_2._update_subscriptions () [0x000d1] in <c3f83e578441427188bf8c55d2a55639>:0
at Sooloos.Broker.RoonApi.TransportService_2.OnThreadExit () [0x00034] in <c3f83e578441427188bf8c55d2a55639>:0
at Sooloos.Broker.RoonApi.Module.ev_exit () [0x0000b] in <c3f83e578441427188bf8c55d2a55639>:0
at Sooloos.SynchronizationContextThread.OnExit () [0x0000a] in <25d73f18cc0f460fa0e05f69a9433340>:0
I’ve been running Roon Server on a QNAP TS-677 for 6 months or so. It’s never crashed.
About 10 days ago I updated the QNAP QTS software to version 4.4.1 1064 and since then I have had 3 Roon crashes, i.e. no Roon remotes can connect to the server and the only way to fix it is to restart the server process on the QNAP.
Nothing else has changed in my setup.
Anyone else updated to QTS 4.4.1 and had similar problems?
I am running 4.4.1 on a QNAP TVS-471. The QNAP runs my core. I have had no Roon issues since the update. Did you by any chance upgrade the memory in your QNAP?
Not saying that this is your issue, but I had something similar to this earlier this year. After I updated my QNAP to a new rev I started getting reboots and crashes. It turned out to be the memory I used to upgrade my QNAP from 4GB to 16GB. The memory had been in there for more than two years with no issues. Once I replaced my memory with new RAM the issues went away. Took me weeks to sort it out. There is a thread in this forum that details what I did.
Have been using a TS-470 Pro and noticed that 4.4 isn’t yet available for that model. Seems unusual not to update all models at the same time, which raises suspicions about the stability of 4.4 on some models. Installed 4.4.1 on a new TVS-1282 today and Roon has been smooth as silk for several hours.
Might be worth considering rolling back the firmware to the previous version and wait for 4.4.2 before updating. Bear in mind the risks of rolling back, however.
QNAP have started to do that quite a lot now - release new QTS versions for different architectures at different times. It is a strange way of doing things, but they have such a (pointlessly) diverse hardware range now that maybe they have to.
I’ll stick with 4.4.1 for the moment - downgrading when I have a very complex NAS environment is probably too high risk: it’s not like it’s crashing every day, and it might not even be related to 4.4.1. but hopefully 4.4.2 will make it more stable.
Don’t think this will be of any help to you but I’ve been running QNAP version 4.4.1 and the latest revision since they both came out and haven’t had any issues. Hope you get to the bottom of it.
I think your memory problems were causing deeper issues weren’t they - your whole NAS was crashing. It’s only Roon that’s dying for me, nothing is having problems and I use this qnap pretty intensively. The NAS itself isn’t crashing.
I’m also wondering now though if iOS 13 has anything to do with it, as that update was around the same time.
Hi @Jamie_Tudor,
Sorry for not replying yet.
Could you send e a zip file of the RoonServer logs? (in the Roon Server Web UI -> ambulance icon -> Download logs). I’ll send you the email address in a PM…