Connectivity issues and crashes after upgrading to build 1559 (ref#OBRWAP)

Roger_Miliker · October 1, 2025, 12:44pm

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Waiting for your Roon Server"

What happens if you press the "Select a different Roon Server" button?

· I see my Roon Server, but I still can't connect.

When you try to connect, what screen do you see?

· I see the Server but the Connect button is grayed out

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *Ethernet*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· *Linux Server* (Ubuntu, Fedora, ArcLinux...)

Select any of the following components that are present in your local network setup

· *Mesh networks*

You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.

· None of the above

Describe the issue

Only since upgrading to build 1559 I have connectivity problems. Roon endpoints disappear, macos client loses connection to server (shows only with red dot symbol). Sometimes even the macos roon application crashes. Restarting both server and client helps - that however is not a solution.
I have tried disabling other services running on the same server, tried disabling ipv6 entirely, no change! I would like to downgrade both server and client to the former, working version. How can I do that?

Describe your network setup

roon server is running on linux on a mac mini (intel), connected via ethernet. Macbook Air and Raspberry roon bridge is connected via mesh wlan (amplify hd). no issues in the past year until this upgrade to 1559

noris · October 1, 2025, 3:06pm

Hello @Roger_Miliker ,

Thanks for reaching out. Can you please confirm the exact local time + date when a few of these events next occur? We’ll enable diagnostics for your account to see if there’s anything interesting in the logs during that time. Does the issue happen at the same time on mutliple remotes?

Roger_Miliker · October 2, 2025, 10:13am

It is occurring right now:

root@roon:/home/roger# date -u
Do 2. Okt 09:47:55 UTC 2025
root@roon:/home/roger# tail -f  /var/roon/RAATServer/Logs/RAATServer_log.txt 
10/02 11:46:48 Info: [discovery] [iface:lo:127.0.0.1] multicast send socket is bound to 0.0.0.0:37595
10/02 11:46:48 Info: [discovery] [iface:enp1s0f0:192.168.1.194] multicast recv socket is bound to 0.0.0.0:9003
10/02 11:46:48 Info: [discovery] [iface:enp1s0f0:192.168.1.194] multicast send socket is bound to 0.0.0.0:39931
10/02 11:46:48 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
10/02 11:46:48 Trace: [raatmanager] announcing
10/02 11:46:48 Debug: [discovery] broadcast op is complete
10/02 11:46:53 Debug: [easyhttp] [224] POST to https://discovery.roonlabs.net/1/register returned after 838 ms, status code: 200, request body size: 528 B
10/02 11:46:53 Trace: [inetdiscovery] registered 1 devices, 1 services
10/02 11:47:29 Trace: [jsonserver] [127.0.0.1:37258] read: eof
10/02 11:47:29 Trace: [jsonserver] [127.0.0.1:37258] destroying client
10/02 11:48:10 Trace: [jsonserver] [127.0.0.1:49080] accepted connection
___________________________________________________________________-
10/02 11:49:17 Trace: [jsonserver] [127.0.0.1:49080] read: eof
10/02 11:49:17 Trace: [jsonserver] [127.0.0.1:49080] destroying client

Roger_Miliker · October 2, 2025, 10:13am

It happens on all remotes, ios and macos. The only “audio zone” available during this state is the airplay destination “Roonkitchen”. I keep getting "connection to roon server … " on the remotes, but no roonbridge audiozone is available in between these “connecting to roon server” message appearances.

Roger_Miliker · October 2, 2025, 10:13am

root@roon:/home/roger# date -u
Do 2. Okt 09:57:33 UTC 2025
root@roon:/home/roger# tail -f  /var/roon/RAATServer/Logs/RAATServer_log.txt 
10/02 11:53:37 Trace: [jsonserver] [127.0.0.1:51456] destroying client
10/02 11:54:28 Trace: [jsonserver] [127.0.0.1:50422] accepted connection
10/02 11:55:35 Trace: [jsonserver] [127.0.0.1:50422] read: eof
10/02 11:55:35 Trace: [jsonserver] [127.0.0.1:50422] destroying client
10/02 11:56:52 Trace: [jsonserver] [127.0.0.1:45302] accepted connection
10/02 11:57:09 Trace: [jsonserver] [127.0.0.1:45302] read: eof
10/02 11:57:09 Trace: [jsonserver] [127.0.0.1:45302] destroying client
10/02 11:57:12 Trace: [jsonserver] [127.0.0.1:54602] accepted connection
10/02 11:57:12 Trace: [jsonserver] [127.0.0.1:54602] GOT[LL] [1] {"request":"enumerate_devices","subscription_id":"0"}
10/02 11:57:12 Trace: [jsonserver] [127.0.0.1:54602] SENT [1] [nonfinal] {"status": "Success", "devices": [{"device_id": "hw:CARD=PCH,DEV=0", "type": "alsa", "name": "HDA Intel PCH CS4206 Analog"}, {"device_id": "hw:CARD=PCH,DEV=1", "type": "alsa", "name": "HDA Intel PCH CS420
10/02 11:58:22 Warn: [jsonserver] client timed out after 10098ms (timeout=10000)
10/02 11:58:22 Trace: [jsonserver] [127.0.0.1:54602] destroying client
10/02 11:58:58 Trace: [jsonserver] [127.0.0.1:33234] accepted connection
10/02 11:59:03 Trace: [jsonserver] [127.0.0.1:33234] GOT[LL] [1] {"request":"enumerate_devices","subscription_id":"0"}
10/02 11:59:03 Trace: [jsonserver] [127.0.0.1:33234] SENT [1] [nonfinal] {"status": "Success", "devices": [{"device_id": "hw:CARD=PCH,DEV=0", "type": "alsa", "name": "HDA Intel PCH CS4206 Analog"}, {"device_id": "hw:CARD=PCH,DEV=1", "type": "alsa", "name": "HDA Intel PCH CS420
^C
root@roon:/home/roger#

alex_h · October 2, 2025, 12:44pm

Good day @Roger_Miliker !

From the diagnostics logs we were able to spot that the connection is being established between your remote (Mac) and Roon Core, however, when data transfer starts it is not able to be completed and the process terminates.

This might mean that the issue is either with the network or Roon Core is unable to complete the data transmission due to some internal reasons.

We have also spotted that your Roon Server has quite an old CPU which is on the verge of matching the hardware requirements.

Thus, we would like to ask you to disable all non-Roon processes on your server and connect to the Roon Server with only 1 remote and try to play the music without real time Signal Processing on the Core’s side.

Let us know please whether this way it is going to bring more stability.

Looking forward to your reply!

Regards.

Lyall_Johns · October 2, 2025, 1:09pm

I am having very similary issues to Roger.
Is this the right place to detail my issues or do I need to raise my own Help Ticket?

Roger_Miliker · October 2, 2025, 1:54pm

Hi,
I just stopped the roon service and verified that there are no remaining Roon processes.
I then restarted the service - I don’t do any processing core side.
I can assure you there are no networking issues - roon is the only app or service that is causing trouble, and only so since the last upgrade I did (to build1559)

How can I downgrade to the last reliably working version? - whatever version I was using until end of August 2025 was perfectly working.

Geoff_Coupe · October 2, 2025, 1:55pm

Please raise your own Support Request. Go to Support and click the Get Help button.

alex_h · October 2, 2025, 3:24pm

Good day @Roger_Miliker !

Thanks for confirming.

In order to exclude the network from the equation can you please try to roll out the Roon Server on your other PC and test if it is working fine ?

Thanks!

Looking forward to your reply.

Regards.

Roger_Miliker · October 3, 2025, 12:00pm

After ensuring no roon processes left and restarting service the issue reoccurred:

root@roon:/home/roger# date -u
Fr 3. Okt 10:14:40 UTC 2025
root@roon:/home/roger# tail -f /var/roon/RAATServer/Logs/RAATServer_log.txt
10/03 12:14:25 Info: [discovery] [iface:enp1s0f0:192.168.1.194] multicast send socket is bound to 0.0.0.0:33071
10/03 12:14:25 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
10/03 12:14:25 Trace: [raatmanager] announcing
10/03 12:14:25 Debug: [discovery] broadcast op is complete
10/03 12:14:27 Trace: [jsonserver] [127.0.0.1:54614] GOT[LL] [1] {“request”:“enumerate_devices”,“subscription_id”:“0”}
10/03 12:14:27 Trace: [jsonserver] [127.0.0.1:54614] SENT [1] [nonfinal] {“status”: “Success”, “devices”: [{“type”: “alsa”, “device_id”: “hw:CARD=PCH,DEV=0”, “name”: “HDA Intel PCH CS4206 Analog”}, {“type”: “alsa”, “device_id”: “hw:CARD=PCH,DEV=1”, “name”: "HDA Intel PCH CS420
10/03 12:14:31 Debug: [easyhttp] [166] POST to https://discovery.roonlabs.net/1/register returned after 807 ms, status code: 200, request body size: 528 B
10/03 12:14:31 Trace: [inetdiscovery] registered 1 devices, 1 services
10/03 12:14:37 Warn: [jsonserver] client timed out after 10008ms (timeout=10000)
10/03 12:14:37 Trace: [jsonserver] [127.0.0.1:54614] destroying client
10/03 12:14:46 Trace: [jsonserver] [127.0.0.1:38806] accepted connection
10/03 12:14:52 Trace: [jsonserver] [127.0.0.1:38806] GOT[LL] [1] {“request”:“enumerate_devices”,“subscription_id”:“0”}
10/03 12:14:52 Trace: [jsonserver] [127.0.0.1:38806] SENT [1] [nonfinal] {“status”: “Success”, “devices”: [{“type”: “alsa”, “device_id”: “hw:CARD=PCH,DEV=0”, “name”: “HDA Intel PCH CS4206 Analog”}, {“type”: “alsa”, “device_id”: “hw:CARD=PCH,DEV=1”, “name”: "HDA Intel PCH CS420
10/03 12:15:02 Warn: [jsonserver] client timed out after 10010ms (timeout=10000)
10/03 12:15:02 Trace: [jsonserver] [127.0.0.1:38806] destroying client

Roger_Miliker · October 3, 2025, 12:00pm

I am now trying with another PC as roon server.

benjamin · October 3, 2025, 5:08pm

Hi @Roger_Miliker,

Let us know how that goes - and if you have the same issues.

If not, move back over to your Linux server instance and see if you’re able to refresh your RAATServer database folder.

You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings -> Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:

Create a Backup of your current Roon database
Exit out of Roon
Navigate to your Roon’s Database Location
Find the folder that says “RAATServer”
Rename the “RAATServer” folder to “RAATServer_old”
Restart the Roon App to generate a new RAATServer folder

Thank you!

dtich · October 4, 2025, 12:19am

yes, i too am having dropped connections since the latest build update.

this system has been rock solid for years.

i think there is an issue w this build.

Roger_Miliker · October 5, 2025, 10:34am

Rebuilding the RAATServer DB didn’t help.

Issue reoccurred:

root@roon:/home/roger# date -u
So 5. Okt 10:33:07 UTC 2025

Roger_Miliker · October 6, 2025, 11:51am

Enough with this investigating!
How do I roll this back to a functioning state?

Geoff_Coupe · October 6, 2025, 12:26pm

You were advised in another thread to open your own support ticket, but I notice that you have not yet done that. Please, if you want support, open a support ticket.

Roger_Miliker · October 7, 2025, 4:47pm

Can I please get support on rolling back to a stable version?

benjamin · October 8, 2025, 11:00pm

Hi @Roger_Miliker,

There isn’t an option to roll back to previous Roon versions, unfortunately. That said, we were able to review a fresh log report from your server and observed the following:

Oct 8 08:08:58 roon start.sh[1788]: Out of memory.
Oct 8 08:08:59 roon start.sh[1576]: Error
Oct 8 08:09:01 roon start.sh[1576]: Initializing
Oct 8 08:09:01 roon start.sh[1576]: Started

This is a process-level memory exhaustion, not a hardware failure - but it does mean the system ran out of usable memory at that time.

You can check what happened around that time by running:

dmesg | grep -i oom

If you see lines like:

Out of memory: Killed process 1788 (start.sh) ...

Then the kernel OOM killer was invoked, confirming a system-wide memory exhaustion.

We’ll be on standby for your reply, thank you!

Roger_Miliker · October 8, 2025, 11:23pm

What file on my system contains this log report you mention?

root@roon:~# date -u
Mi 8. Okt 23:21:28 UTC 2025
root@roon:~# uptime
01:21:29 up 1 day, 6:32, 4 users, load average: 1,44, 1,47, 1,43
root@roon:~# dmesg | grep -i oom
root@roon:~#