Does the issue happen with local library music, streaming service music, or both?
· *Both streaming and local* *library* music are affected.
Do you encounter any playback errors with the "System Output" Zone?
· The System Output has the same problem as my other Zone.
Do you have a complex network setup?
· I don't have a mesh network, but I use *managed network switches*
Your local network might need some re-arranging to support Roon.
· None of the suggestions have helped me. I'd like to submit a support request.
What are the make and model of the affected audio device(s) and the connection type?
· Raspberry Pi 2 (Alsa) with DietPi v9.7.1 [100Mbit ethernet], 2 x Auralic Aries Mini with 9.6 firmware [1000Mbit ethernet], Roonserver running on i7 16MB with SSD storage, Ubuntu Server LTS 24.04 (latest patches) (also tested Ubuntu 20.04 and 22.04) [1000Mbit ethernet].
Describe the issue
Zones vanish from client and showing a text like Nothing to play, resumes usually after some time. Music stopping for a while and start playing again. Other services including video streaming, native client to Qobuz, Radio streams from broadcaster, Qobuz with Aralic client, work without any problems. With the same network configuration i had no problems with Roon previously (approx. half year ago).
Describe your network setup
Router/Firewall: MikroTik hEX S with SFP to provider. Cisco WS-C3560CX-12PC-S connected to router. 3 x Cisco CBS250-8T-D. All AV including Roon on VLAN 20. All AV is hardwired.
Hi @connor
One Auralic is connected on Cisco WS-C3560CX-12PC-S, in VLAN20
One Auralic is connected on a CBS250-8T-D in VLAN 20 that is connected with a trunk to Cisco WS-C3560CX-12PC-S.
The Rpi2 is connected on a CBS250-8T-D in VLAN 20 that is connected with a trunk to Cisco WS-C3560CX-12PC-S.
So everything AV including all Roon clients, endpoints and server is in VLAN 20.
The MikroTik hEX S is the router that connects VLAN20 to the internet.
VLAN 20 is subnet 192.168.20.0/24 all devices get IP addresses with DHCP and have reserved addresses in the DHCP server so they always get the same address.
All devices get IPv4 and IPv6 except the roonserver where IPv6 is disabled as it is best practice.
I will send a dropout timestamp when it occurs, but as it is night here (norway) now it can take a while.
@connor
+/- 2024-08-30T08:36:00 MEST: The radio stream stopped and and did not start again. had to press play after a approx. 60 seconds. On the left where the streamname was it says “Nothing playing”. When it stopped the zoe icon was gone for a few second (could just see that). Endpoint is my office Raspberry Pi 2 with DIetPi to USB (alsa).
+/- 2024-08-30T08:51:00 MEST: Same as above
+/- 2024-08-30T09:37:00 MEST: Same as above
+/- 2024-08-30T10:06:00 MEST: Same as above
+/- 2024-08-30T10:21:00 MEST: Same as above , now streaming from Qobuz
+/- 2024-08-30T10:51:25 MEST: Hickup of a second in the stream.
+/- 2024-08-30T11:06:25 MEST: Same as the first with stream from Qobuz.
Looks like there is a pattern, wil restart roonserver now and see if it solves the issue for a while as it did before.
+/- 2024-08-30T11:10:00 MEST: restartet roonserver (systemctl restart roonserver)
+/- 2024-08-30T11:11:30 MEST: roonserver service started, listening again to Nick Cave and the Bad Seeds new album Wild God
+/- 2024-08-30T16:38:00 MEST: No errors after the restart earlier, so long.
20:00 everything still stable, no hickups or missing zones, a restart solves it temporarely. Now it is weekend, cheers.
I’m sorry to report, unfortunately, that we’re not able to assist with anything running in a VLAN setup, as it falls outside of the scope of official Roon support.
If there was one area we would investigate further, it would start with the temporary bypassing of your Cisco switches, especially any that are layer-3 business-grade switches.
I’ll go ahead and move your thread over to our Tinkering category in hopes that others in the community who run similar setups may be able to assist further.
You have my apologies here, and I hope you’re able to sort it out!
This is very dissapointing.
Ignoring facts and just dissmiss a support case because of the use VLAN.
VLANs technology is mature and has earned its place in networking.
It is obviously and proven that the roonserver program does not behave over time.
After a restart it is stable for a few hours but mostly days before it falls in instability again.
Roonsupport should focus on this, also because other users have reported this.
Just moving the support case to tinkering and say «you are on your own» is not okay.
So now i have to buy new consumer grade networking gear and other extra equipment, thus using extra money to find out the roonserver program is not behaving on linux.
What happened to, «send in the times and we look into the problem in our logs».
I have send very accurate time stamps to help support finding out what could be wrong.
To be ignored by support…
I will see what my actions will be, it could just not be in favour of Roon (i am an annual paying customer).
Some may disagree with this, but Roon are right here in my view.
I look at problems, within my scope of knowledge and from the outset the OP mentioned Cisco Layer3 switches. Roon’s recommendations are for a flat/simplified network. I believe using Layer3 switches is part causation for the OPs troubles.
A number of us have ran Roon fine on a managed network, but most likely with Layer2 switches, like me and haven’t had issues. I’ve used VLANs and had multiple devices across several VLANs with the required firewall rules in place and everything has worked. Even Sonos . I now run a simplified managed network, 1 subnet.
I’m more interested in the OPs history over the last 4 years. Have they always had a network with Layer3 switches, have they always had issues. Did the issues creep in recently, around an update of network firmware, Roon, DietPi etc.
Yeah, I read that, but it’s ambiguous to me, sorry.
Either way it sounds like they may have ran in to “Roon” troubles relating to a network being outside of what Roon recommends. Maybe not
Maybe Roon could/should have looked at the users logs to see if an issue related due to a setup outside of their recommendations.
What is clear, is for some an update can cause havoc with Roon and some go unaffected. Why though? Same software. From user to user their network and endpoints differ greatly.
To rule one thing out you may need to implement something you don’t want to because it worked before.
If someone said a potential cause for my Roon troubles was network related and gave me advice to simplify it, I would.
‘A car manufacturer recommends running your new car on 95 RON petrol because you’ll get better economy and less ware. You decide to use 97 RON petrol and you get crappy economy and burn out a piston ring. Will you get the manufacturers support?’
(Petrolheads, sorry for the crappy analogy)
I don’t run Rock on a supported device and my network isn’t as per recommendations. I could be lucky Roon on the whole works ok. I’ve had weird issues as you know. Could just be me.
TBH no where in Roon’s docs does it mention anything about not supporting VLAN’s in their Compatibility section on the main site nor in the Networking best practices section of the Help. In fact the help section doesn’t find anything related to them at all. So if you don’t frequent these forums a lot you are likely to not ever know. Which explains why users are surprised or annoyed when they come on here to be told with we don’t support that configuration and they have already bought in.
Just to be clear, i have used this network configuration with VLANs for over 10 years.
This means that i have used this config as long as i had Roon and before.
I have done all it takes to debug that was in my power, and presented this to support, just to be shoved aside.
True, Roon cannot support everything, but some effort could have been nice.
Anyway, i love the Roon product but the way they run support is far below par.
I cannot pay the annual fee and have to debug and fix issues myself.
I could be a resource for Roon, but it is easier for support to just say «your on your own».
Having just 2 days again on my subscription was bad luck for Roon.
I wish we could be together longer but it was not ment to be…
I have used Roon succesfully with L3 spanned over L2.
I had a Roon endpoint in my office at work with VPN and used a client on my phone over 4G.
The core was at home!
Why?, just for fun and because i could.
BTW; enterprise networking and unix/linux systems are my expertise for just short for 40 years…
I wish i had lied about my network and let «support» find out.
To be honest, does not pay and to behonest i miss Roon’s conveniant way of unifying my audio.
The solution i have now gives me error free listening, but not the unified experiance Roon offers.
Anyway, music is more important than everything else.
Will there ever be Roon in my life?
Probably not, i will not switch to another Roon server os, i will not change my network and Roon will not change the way they offer «support»,
Not that anyone cares, Roon users do not care, Roon was automatically sad to see me go, Roon support solved their support case and me, i just have a bad taste in my mouth about the way support treated the case and made me abbandon Roon.
Doubt that Roon staff will give this scribling any thought, but thats why i wrote this; they should.
To whom who have read this; ROCK ON and enjoy music and Roon!
. I now run a simplified managed network, 1 subnet.
