Roon & ARC have become incredibly unreliable for me - what is going on?

I have the same issue too. I think it must be something in the roon build.

2 Likes

The issue gets majorly alleviated when I use Linux instead of Windows, so I dont believe its hardware related.

1 Like

Isn’t ROCK a custom Linux OS also? My NUC runs Roon as ROCK exclusively so the issues seem to be unrelated whether the core runs on Windows or Linux. But don’t know.

It is.

For me at least, it happen in both Windows and Linux, but it happen MUCH more frequently on Windows. Right now its unusable on windows.

On Linux its less frequent, I at least get some hours of interupted listening.

1 Like

This is interesting. Your Windows installation was also fresh, without any other software?

I only have the core running on windows 11, so I cannot make any comparison.

1 Like

The windows installation was also fresh when the issue started, yes. This was on windows 10. I did end up upgrading to 11 and Roon behaves in the exact same way there.

2 Likes

Thanks for taking the time to reply! Still it is very interesting that a linux environment makes the crashes less frequent.

1 Like

Have you guys looked at the system logs to find out why it’s crashing? Have you looked on Windows as you might see a crash log there?

1 Like

I have a nucleus +. Arc always worked well, up to some builds back.

1 Like

I’m on Ubuntu and as mentioned Roon just goes into the weird state above where Arc can’t connect and Album and Home don’t load locally on remotes. These are the logs around the last time it happened (the scrobble at the top went through but one that should have occured at 00.04 listening to local music on Arc didn’t so it must have lost communication in that window). Nothing I can see that looks unusual?

Roon Server Log

10/06 00:01:31 Debug: Lastfm - Scrobbling 1 tracks to last fm for token: LKQ44M7HBFwUwokFGBuBrlssMp8c7FVv
10/06 00:01:31 Debug: [easyhttp] [4967] POST to http://ws.audioscrobbler.com/2.0/ returned after 129 ms, status code: 200, request body size: 309 B
10/06 00:01:37 Info: [stats] 23803mb Virtual, 2896mb Physical, 1229mb Managed, 383 Handles, 72 Threads
10/06 00:01:52 Info: [stats] 23843mb Virtual, 2897mb Physical, 1239mb Managed, 383 Handles, 79 Threads
10/06 00:02:07 Info: [stats] 23843mb Virtual, 2897mb Physical, 1244mb Managed, 383 Handles, 76 Threads
10/06 00:02:17 Trace: [roonapi] [apiclient 192.168.1.65:39796] CONTINUE Changed {“message”:“Extension Repository loaded (v1.0.15)”,“is_error”:false}
10/06 00:02:22 Info: [stats] 23827mb Virtual, 2897mb Physical, 1247mb Managed, 383 Handles, 77 Threads
10/06 00:02:37 Info: [stats] 23811mb Virtual, 2897mb Physical, 1252mb Managed, 383 Handles, 71 Threads
10/06 00:02:52 Info: [stats] 23803mb Virtual, 2897mb Physical, 1259mb Managed, 383 Handles, 72 Threads
10/06 00:03:07 Info: [stats] 23803mb Virtual, 2897mb Physical, 1264mb Managed, 383 Handles, 72 Threads
10/06 00:03:17 Trace: [roonapi] [apiclient 192.168.1.65:39796] CONTINUE Changed {“message”:“Extension Repository loaded (v1.0.15)”,“is_error”:false}
10/06 00:03:22 Info: [stats] 23827mb Virtual, 2897mb Physical, 1268mb Managed, 383 Handles, 77 Threads
10/06 00:03:37 Info: [stats] 23827mb Virtual, 2897mb Physical, 1275mb Managed, 383 Handles, 74 Threads
10/06 00:03:52 Info: [stats] 23819mb Virtual, 2897mb Physical, 1284mb Managed, 383 Handles, 75 Threads
10/06 00:04:07 Info: [stats] 23819mb Virtual, 2897mb Physical, 1290mb Managed, 383 Handles, 74 Threads
10/06 00:04:17 Trace: [roonapi] [apiclient 192.168.1.65:39796] CONTINUE Changed {“message”:“Extension Repository loaded (v1.0.15)”,“is_error”:false}
10/06 00:04:22 Info: [stats] 23811mb Virtual, 2897mb Physical, 1291mb Managed, 383 Handles, 71 Threads
10/06 00:04:37 Info: [stats] 23811mb Virtual, 2897mb Physical, 1297mb Managed, 383 Handles, 71 Threads
10/06 00:04:44 Info: [mobile] GOT HTTP API /sync
10/06 00:04:46 Trace: [broker/accounts] [heartbeat] now=10/5/2023 11:04:46 PM nextauthrefresh=10/5/2023 11:44:47 PM nextmachineallocate=10/6/2023 12:34:46 AM
10/06 00:04:52 Info: [stats] 23803mb Virtual, 2897mb Physical, 1307mb Managed, 384 Handles, 73 Threads
10/06 00:05:07 Info: [stats] 23803mb Virtual, 2897mb Physical, 1315mb Managed, 381 Handles, 72 Threads
10/06 00:05:17 Trace: [roonapi] [apiclient 192.168.1.65:39796] CONTINUE Changed {“message”:“Extension Repository loaded (v1.0.15)”,“is_error”:false}
10/06 00:05:22 Info: [stats] 23803mb Virtual, 2897mb Physical, 1316mb Managed, 381 Handles, 71 Threads
10/06 00:05:37 Info: [stats] 23803mb Virtual, 2897mb Physical, 1324mb Managed, 381 Handles, 74 Threads
10/06 00:05:52 Info: [stats] 23811mb Virtual, 2897mb Physical, 1332mb Managed, 381 Handles, 75 Threads
10/06 00:06:07 Info: [stats] 23819mb Virtual, 2897mb Physical, 1337mb Managed, 381 Handles, 73 Threads
10/06 00:06:17 Trace: [roonapi] [apiclient 192.168.1.65:39796] CONTINUE Changed {“message”:“Extension Repository loaded (v1.0.15)”,“is_error”:false}
10/06 00:06:22 Info: [stats] 23811mb Virtual, 2897mb Physical, 1339mb Managed, 381 Handles, 71 Threads
10/06 00:06:37 Info: [stats] 23811mb Virtual, 2897mb Physical, 1345mb Managed, 381 Handles, 73 Threads
10/06 00:06:52 Info: [stats] 23811mb Virtual, 2897mb Physical, 1355mb Managed, 381 Handles, 73 Threads
10/06 00:07:07 Info: [stats] 23811mb Virtual, 2897mb Physical, 1361mb Managed, 381 Handles, 72 Threads
10/06 00:07:17 Trace: [roonapi] [apiclient 192.168.1.65:39796] CONTINUE Changed {“message”:“Extension Repository loaded (v1.0.15)”,“is_error”:false}
10/06 00:07:22 Info: [stats] 23811mb Virtual, 2898mb Physical, 1363mb Managed, 381 Handles, 72 Threads
10/06 00:07:33 Info: [mobile] GOT HTTP API /hello
10/06 00:07:33 Info: [mobile] GOT HTTP API /hello
10/06 00:07:33 Trace: [mobile] Got Hello Request body={“coreId”:“02b239af-7470-4208-867c-81848460bdba”}
10/06 00:07:33 Trace: [mobile] Got Hello Request body={“coreId”:“02b239af-7470-4208-867c-81848460bdba”}
10/06 00:07:33 Trace: GetImageData[Remote](id=449202 spec=128 key=anozaaaa) => got from cache overalltime=0ms
10/06 00:07:33 Trace: GetImageData[Remote](id=449202 spec=128 key=anozaaaa) => got from cache overalltime=0ms
10/06 00:07:37 Info: [stats] 23811mb Virtual, 2898mb Physical, 1375mb Managed, 384 Handles, 75 Threads
10/06 00:07:41 Info: [mobile] GOT HTTP API /hello
10/06 00:07:41 Info: [mobile] GOT HTTP API /hello
10/06 00:07:41 Trace: [mobile] Got Hello Request body={“coreId”:“02b239af-7470-4208-867c-81848460bdba”}
10/06 00:07:41 Trace: [mobile] Got Hello Request body={“coreId”:“02b239af-7470-4208-867c-81848460bdba”}
10/06 00:07:52 Info: [stats] 23811mb Virtual, 2898mb Physical, 1383mb Managed, 384 Handles, 75 Threads
10/06 00:08:07 Info: [stats] 23819mb Virtual, 2898mb Physical, 1390mb Managed, 384 Handles, 73 Threads
10/06 00:08:17 Trace: [roonapi] [apiclient 192.168.1.65:39796] CONTINUE Changed {“message”:“Extension Repository loaded (v1.0.15)”,“is_error”:false}
10/06 00:08:22 Info: [stats] 23803mb Virtual, 2898mb Physical, 1391mb Managed, 384 Handles, 70 Threads
10/06 00:08:37 Info: [stats] 23803mb Virtual, 2898mb Physical, 1397mb Managed, 384 Handles, 73 Threads
10/06 00:08:52 Info: [stats] 23811mb Virtual, 2898mb Physical, 1406mb Managed, 384 Handles, 73 Threads

RAAT Log

10/05 23:29:54 Debug: [easyhttp] [4] POST to https://discovery.roonlabs.net/1/register returned after 571 ms, status code: 200, request body size: 527 B
10/05 23:29:54 Trace: [inetdiscovery] registered 1 devices, 1 services
10/06 03:29:54 Debug: [easyhttp] [5] POST to https://discovery.roonlabs.net/1/register returned after 572 ms, status code: 200, request body size: 527 B
10/06 03:29:54 Trace: [inetdiscovery] registered 1 devices, 1 services

1 Like

Just want to chip in, that I’m having the exact same issue. It seems to be triggered every time I use Roon ARC. It start playing just fine, but after a while the core itself is still alive, but all connection towards Roon functionality is not working…

Looking at the RAM usage of roonserver, it appears to be eating close to 7 Gb. That’s quite a lot more than some releases ago.

@Somebody_from_Roon any support?

1 Like

Just went over the roon server logging, and no errors are showing up. Even now the server functionality is offline, but the core is online. Resulting in:

or

2 Likes

Now when running Roon ARC, and trying to open Roon on my MacBook Pro it is giving this error on MacOS (all latest versions):

Roon does not want to start up anymore on my MacBook Po…

Closing ARC on my Android phone will result in Roon starting up again on my MacBook Pro. But in the “limbo” state again.

1 Like

Hi @jeroendee,

it does look like a very similar issue. The screenshots of your Roon endpoint just stuck loading any content is exactly what I experience after ARC crashed my Roon core.

As described in this thread a restart of the core temporarily fixes the issue but it will appear again after some time. But once the core crashed a restart or reset of the ARC app does not help.

Here is another thread that states similar problems with ARC crashing the core.

I wonder when Roon support will finally get active on these…

1 Like

I came home today, and indeed: Roon Server had crashed sometime during my holiday. Before ARC, or before me using ARC, this has never happened once.
After a first reboot of Roon Server, ARC on Android seemed to come to life, because part of my holiday play history appeared in Roon Remote’s history. But most of my history seemed to be ‘unreachable’ (or some other term Roon uses). Only after a second reboot of Roon Server all went smooth and normal again.
Both reboots were of Roon Server only, my Sonicorbiter stayed on all the time.

1 Like

Thanks for the follow-up. It indeed seems to be the same issue we in this thread also encountered on our ends over the past few months.

To your point regarding it never happening before ARC: ARC is the main culprit here. I could listen for hours on end with my Roon endpoints and streamer even over a VPN connection to my home-network. But, whenever I try to use ARC it is only a question of time until something in the communication between the core and ARC crashes the core so that only a manual reboot of it fixes the issue albeit only temporarily.

2 Likes

I found two cases where this happens, but there must be more:

  • Roon Server receives an upgrade. While this is waiting to be installed, ARC won’t function anymore.
  • Switching between a downloaded track and a Tidal track in a playlist when there is no mobile network, in a long tunnel for instance. As soon as the Tidal track starts, ARC dies and so does Roon Server.
1 Like

Thanks for providing these. I cannot really say anything to these as I struggled to find any particular pattern to the crashes. But I did notice that crashes appear more frequently in areas with fluctuating mobile network quality and your identified 2nd case could be correct.

I noticed that sometimes even switching from WiFi to 5G causes ARC to crash the core after the currently played track. Don’t know if local music vs streaming platform does make a difference here though. But as I said sometimes I can go for hours without experiencing a single crash whereas other days in similar scenarios I get a couple within the first minutes of listening.

1 Like

Hi All,

Just want to throw my hat in the ring here. I’m having the exact same issue as everyone is describing and have been for months. I use a Nucleus as my core, so considering I am using Roon’s own hardware and the issues still persists makes me certain it is an issue that stems from the core (regardless of what you use) communicating with ARC.

Thanks

3 Likes