Roon MacOS client cuts out / disconnects / stops working during playback from Qobuz

Roon Core Machine

Windows 10, Intel i7 CPU, 16GB RAM

Networking Gear & Setup Details

Araknis router, switches, WAPs. Server on CAT6 ethernet, Macbook client on WiFi

Connected Audio Devices

None, playback via Macbook Pro 16 speakers

Number of Tracks in Library

24450 tracks

Description of Issue

Playback aborts unexpectedly mid-track, deletes the queue, and cannot resume on my MacOS Roon client.

I shut down Roon on the Macbook, I signed in to my Windows machine where Roon core runs, started Roon Client, started playback on remote Macbook. Again, it played for a few minutes then cut out hard - same behavior.

FYI @support I am uploading my logs to the log server. I did update Roon Client on MacOS before this issue occurred, and my Core said it was already up to date.

Here’s the timestamp of one of the times playback aborted. It happened several times before this. Not sure whether this may have been occurring after an update - I’ve noticed similar unexpected stops in Arc and with my other devices (Naim streamer and AppleTV), but didn’t have logs and details.

03/19 23:30:35 Warn: [rnet/RnetJsonClient] failed to connect No connection could be made because the target machine actively refused it 10.10.1.128:9200
03/19 23:30:35 Trace: [raatserver] [RaatServer Macbook16-Monty @ 10.10.1.128:9200] client connection failed. Retrying in 500ms

03/19 23:30:44 Warn: [rnet/RnetJsonClient] failed to connect No connection could be made because the target machine actively refused it 10.10.1.128:9200

@Early_Access @support please help…

Just another user here, not running on early access versions.
Something seems funky about your versions not being the same, although stating to have the latest ones running.

If you’re not into fiddling with pre-release problems like me, I’d suggest to pull backups and revert to current production versions for more stability.

Good luck with it!

Hi @Monty_Kosma,

Thank you for your patience while the team investigated your report.

Diagnostics indicate your Core (Windows 10 Machine) is out of storage space. This would most likely be the mechanism for wiping out your queue.

If your database has been operating without sufficient storage, there’s a massive corruption risk. It might be worth restoring from an earlier Backup, if available. If you restore from a Backup from before the issue first occurred, do you still experience any problems?

Please let us know if you have any questions. The storage issue appears systemic and likely underpins most symptoms and performance decline you’ve been experiencing.

We’ll be watching for your response. Thank you!

Ah - that could be. I have a very small C: partition and a very large D: partition. Do you know how I ensure that Roon (and the machine in general) is using the large partition for temp files and cache and the like?

How small did you make the C partition? There are a lot of things that want to live on C.

Anyhow, here is a link on how to move the Temp directory for Win 10 to a different drive.

https://www.howtogeek.com/285710/how-to-move-windows-temporary-folders-to-another-drive/

Not sure this will affect Roon’s running accept for clearing other stuff off the C drive and freeing space up.

1 Like

Thanks for the link, @Rugby … C: is >200GB:

Hi @Monty_Kosma,

A few other notes here after reviewing your setup and logs again.

  1. Have you tried using the Mac in your setup as a Core? Storage aside, the additional processing power might benefit overall performance in Roon.

  2. It’s worth updating Remotes to match the #earlyaccess build of your server/Core. Build mismatches aren’t responsible for the issue you experienced in this thread, but changes accumulate quick in Early Access.

Please let us know if we can assist further here.

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.