Frequent Roon Server crashes after recent update (ref#T95PSJ)

What app are you having the slowness issue with?

· Roon

What kind of performance/speed issue are you experiencing?

· The app is crashing

Please try to reboot your Roon Server

· Yes, rebooting helps, but the issue returns after some time

Please try to reboot your networking gear (Router/Switches/etc.)

· No, the issue is still the same even after a reboot

Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?

· No, the issue is still the same

Does the issue happen on multiple Roon Remotes (controllers) or just one?

· Issue happens on multiple remotes

Router Domain Name System (DNS) change

· I was able to change my router's DNS servers but it did not help

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

· Linux Server (Ubuntu, Fedora, ArchLinux...)

Describe the issue

Roon server crashes too often after the recent version update

Describe your network setup

Private home LAN over iptime routers

1 Like

The symptom was a sudden stop of music play and this part becomes empty but ask me to select a music device.

It returns back in around 10 secs so I couldn’t take screenshot. It happens pretty often nowadays like 3~4 times a day. It’s so annoying.

Is it only me or is this a known issue?

I tried to check the server log but couldn’t find any error.

2 Likes

Hello @Jason_Kim ,

Thanks for reaching out. I activated diagnostics for your account to review the error logging, and it looks like right around the time when you play that track, all devices disconnected at the same time. This suggests there was a whole network drop, or something caused the RoonServer to lose its connection. Is the server connected through several switches? Do the router logs show any network event? Here is the relevant trace below:

10/01 09:39:14 Trace: [M33] [Enhanced, 16/44 FLAC => 24/44] [100% buf] [PLAYING @ 0:14/3:09] Préludes (12) for piano, Book I, L. 117: Danseuses de Delphes. Lent et grave - Steven Osborne / Claude Debussy
10/01 09:39:16 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection.
10/01 09:39:16 Trace: [raatserver] [RaatServer junchul-macbookpro @ 192.168.0.104:9200] lost client connection. Retrying(0)
10/01 09:39:16 Trace: [raatserver] [RaatServer junchul-macbookpro @ 192.168.0.104:9200] connecting (attempt 1)
10/01 09:39:17 Trace: [raat_ll/client] [NAD M33 @ 192.168.0.118:38325] no data received for >10000ms. Killing connection.
10/01 09:39:17 Trace: [raat_ll/client] [NAD M33 @ 192.168.0.118:38325] OnDisconnected: no data received for >10000ms. Killing connection.
10/01 09:39:17 Trace: [raat] [NAD M33 @ 192.168.0.118:38325] => Disconnected
10/01 09:39:17 Trace: [raat] [NAD M33 @ 192.168.0.118:38325] lost client connection. Retrying
10/01 09:39:17 Trace: [raat] [NAD M33 @ 192.168.0.118:38325] connecting (attempt 1)
10/01 09:39:17 Info: [transport] destroyed zone M33 was playing? True
10/01 09:39:17 Trace: [zone M33] Suspend
10/01 09:39:17 Info: [zone M33] OnPlayFeedback Stopped
10/01 09:39:17 Info: [zone M33] Canceling Pending Sleep
10/01 09:39:17 Info: [zone M33] Canceling Pending Sleep
10/01 09:39:17 Debug: [raat/tcpaudiosource] disconnecting
10/01 09:39:17 Trace: [raat] [NAD M33 @ 192.168.0.118:38325] => Connecting
10/01 09:39:17 Trace: [M33] [zoneplayer/raat] Endpoint NAD M33 State Changed: Playing => Prepared
10/01 09:39:17 Info: [audio/env] [zoneplayer -> stream] All streams were disposed
10/01 09:39:17 Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
10/01 09:39:17 Info: [audio/env] [zoneplayer] All streams were disposed
10/01 09:39:17 Trace: [library] endmutation in 15ms
10/01 09:39:17 Info: sleep 200ms after flush
10/01 09:39:17 Info: [transport/zonedisplay] Zone display unregistered: CastDevice[DeviceId=Google-Nest-Hub-7ba09e6bb62ad21b234c06e94543ed9e._googlecast._tcp.local, Name=Google Nest Hub, Address=192.168.0.9]
10/01 09:39:17 Info: [cast] lost device CastDevice[DeviceId=Google-Nest-Hub-7ba09e6bb62ad21b234c06e94543ed9e._googlecast._tcp.local, Name=Google Nest Hub, Address=192.168.0.9] because it disconnected
10/01 09:39:18 Trace: [raat_ll/client] [Bluesound N330 @ 192.168.0.6:36357] no data received for >10000ms. Killing connection.
10/01 09:39:18 Trace: [raat_ll/client] [Bluesound N330 @ 192.168.0.6:36357] OnDisconnected: no data received for >10000ms. Killing connection.
10/01 09:39:18 Trace: [raat] [Bluesound N330 @ 192.168.0.6:36357] => Disconnected
10/01 09:39:18 Trace: [raat] [Bluesound N330 @ 192.168.0.6:36357] lost client connection. Retrying
10/01 09:39:18 Trace: [raat] [Bluesound N330 @ 192.168.0.6:36357] connecting (attempt 1)
10/01 09:39:18 Info: [transport] destroyed zone POWERNODE was playing? False
10/01 09:39:18 Trace: [zone POWERNODE] Suspend
10/01 09:39:18 Info: [zone POWERNODE] Canceling Pending Sleep
10/01 09:39:18 Info: [zone POWERNODE] Canceling Pending Sleep
10/01 09:39:18 Trace: [raat] [Bluesound N330 @ 192.168.0.6:36357] => Connecting
10/01 09:39:19 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection.
10/01 09:39:19 Trace: [raatserver] [RaatServer dboxeq1 @ 127.0.0.1:9200] lost client connection. Retrying(0)
10/01 09:39:19 Trace: [raatserver] [RaatServer dboxeq1 @ 127.0.0.1:9200] connecting (attempt 1)
10/01 09:39:22 Trace: [remoting/brokerserver] [initconn 192.168.0.108:54948=>192.168.0.11:9332] Connected
10/01 09:39:22 Trace: [remoting/brokerserver] [initconn 192.168.0.108:54947=>192.168.0.10:9332] Connected
10/01 09:39:22 Info: [library] saved recent ProfileId=6ac695f0-1dbd-47d1-8902-de49a5bfc72e Time=10/1/2025 12:39:22AM DataType=album Type=long_nav MetadataId=2769529 ContentId=808239 LibraryId=808239 Text= Genre=
10/01 09:39:22 Trace: [raatserver] [RaatServer junchul-macbookpro @ 192.168.0.104:9200] connected

Oh. I didn’t know you can check my log remotely. Thank you for the foundings. Let me double check the network or my linux box running roon server if there were any network disruption.

Hello @Jason_Kim

Please keep us posted with your findings.

Hi @Jason_Kim,

From admin diagnostics, it looks like the machine hosting RoonServer appears to have multiple available network interfaces. It’s possible that Roon switched between network interfaces and temporarily lost sight of the devices.

You mentioned multiple routers in this setup - does the same router serve both your RoonServer machine and your remotes, or do you have a mesh/extended setup?

We’ll watch for your response. Thanks!

i have the same issue as OP. frequent loss of (one specific) endpoint. occasionally server lockup.

and i also have multiple nets (subnets) on the same machine. this has been the case for a decade. roon as never, before this build, had an issue finding devices like it does since latest update.

do you recommend i file a support ticket? or are you agreed this is a server build issue and i’ll wait for the forthcoming fix?

thanks guys.

1 Like

My machine has 2 physical ethernet and 1 wifi. 1 eth and 1 wifi were enabled. I disabled the wifi since it’s not needed. I’m monitoring if this fixes the issue.

However just like @dtich, I’ve been using this setup for a while but haven’t had this problem until recent.

Can I let roon to use a fixed net dev in linux and not let it switch between multiple nics?

1 Like

Yes - please raise your own support ticket. The Support Team will merge threads where necessary if common causes are found for issues with similar symptoms. Go to Support and click the Get Help button . Thank you.

I had this issue today again. 3 times in an hour.

I already turned off wifi so I’m not sure what’s the problem.

I realized that I haven’t answer to this. Yes. I have a mesh network. However, all the music players and the roon server is connected over wire ethernet.

One root switch and leaf switches connected to the parent over cat 5e wire.

The lines are less than 10m in total. I’m pretty sure that the connection is pretty stable and I couldn’t find any sign of bad connection. I suspected the host network of the linux box running roon server. That’s a beelink eq14 box. I still can not found any significant issue with it.

Hey @Jason_Kim,

Thanks for the update! There’s an indication your server might be having discovery-related issues due to there being multiple active subnets within your local network.

As a next step in troubleshooting, could you test out disabling all but a single active subnet? Be sure to reboot your devices afterward, and let me know how your server performs.

Thank you, Jason! :folded_hands:

Hi @benjamin ,

I’m not sure what you mean by disabling subnet. If you meant NICs, I have 3 active NICs with different subnets + lo.

  • One physical ethernet with 192.168.0.10/24.
  • tailscale0 with 100.99.254.45/32 for tailscale.
  • podman0 with 10.88.0.1/16 for podman containers.

I need all of them to run my services. Do you mean it’s not possible to run containers or tailscale VPN in parallel to roon server? I’ve been using this setup for a while and didn’t have any problem until recent.

I temporarily disabled the other services to see if that helps but this is only for temporal test.

If this is the actual problem, you must have a solution to address this problem by i.e. let the users whitelist/blacklist subnets/nics for the discovery. I believe this is not very unusual configuration for your customer.

Hello @Jason_Kim,

Thank you for the update.

We’ve enabled an additional layer of diagnostics on your account. Could you please restart your Roon Server several times, reproduce the issue again, and share the exact timestamp when it occurs?

Additionally, please confirm whether Roon Server is installed as a systemd service.

Hi @vadim,

I first restarted roon server 3 times. And yes. I installed it as a systemd service.

sudo systemctl status roonserver.service
● roonserver.service - RoonServer
     Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-10-10 22:16:16 KST; 1min 22s ago
 Invocation: 2596973367074392a8005e9fc8c91c67
   Main PID: 2892 (start.sh)
      Tasks: 104 (limit: 37441)
     Memory: 893.3M (peak: 941M)
        CPU: 26.829s
     CGroup: /system.slice/roonserver.service
             ├─2892 /bin/bash /opt/RoonServer/start.sh
             ├─2899 /opt/RoonServer/RoonDotnet/RoonServer RoonServer.dll
             ├─2920 /opt/RoonServer/RoonDotnet/RoonAppliance RoonAppliance.dll -watchdogport=36951
             ├─2924 /opt/RoonServer/Server/processreaper 2920
             └─2963 /opt/RoonServer/RoonDotnet/RAATServer RAATServer.dll

Oct 10 22:16:16 dboxeq1 systemd[1]: Started roonserver.service - RoonServer.
Oct 10 22:16:16 dboxeq1 start.sh[2899]: 00:00:00.000 Info:  get lock file path: /tmp/.rnsgem0-
Oct 10 22:16:16 dboxeq1 start.sh[2899]: 00:00:00.004 Info:  GetLockFile, fd: 35
Oct 10 22:16:16 dboxeq1 start.sh[2899]: 00:00:00.004 Info:  GetLockFile, res: 0
Oct 10 22:16:16 dboxeq1 start.sh[2899]: 00:00:00.004 Trace: Nope, we are the only one running
Oct 10 22:16:16 dboxeq1 start.sh[2899]: Initializing
Oct 10 22:16:16 dboxeq1 start.sh[2899]: Started
Oct 10 22:16:17 dboxeq1 start.sh[2920]: aac_fixed decoder found, checking libavcodec version...
Oct 10 22:16:17 dboxeq1 start.sh[2920]: has mp3float: 1, aac_fixed: 1
Oct 10 22:16:21 dboxeq1 start.sh[2899]: Running

I will try to reproduce it and I will report the timestamp if it occurs again.

Hello @Jason_Kim

The crucial step is to restart the Roon services multiple times to apply the new diagnostic mode. Please let us know how it goes after that.

Bumping this thread @Jason_Kim let me know if you were able to reboot multiple times - thank you! :folded_hands:

As I already said in my previous comment, I already restarted multiple times.

I’ve been trying to reproduce it since then but for some reason it hasn’t happened. Although it was pretty random, not happening for multiple days sounds like something has changed. I’m keep monitoring it. I will close this if it doesn’t happened for one or two more weeks.

Hi @Jason_Kim ,

Thanks for letting us know. Yes, please do monitor and let us know if the issue re-occurs or if the behavior is now stable, thanks!

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