I've installed a RoonServer on a new Ubuntu 24.04 LTS Server. The client constantly goes from connecting to ready. The same client works fine to my existing RoonServer on the same subnet (different IP). The logs are full of this repeating. 03/05 20:41:44 Info: [12] [stats] 3910mb Virtual, 231mb Physical, 131mb Managed, 234 Handles, 36 Threads 03/05 20:41:49 Trace: [Broker:Misc] [remoting/brokerserver] [initconn 10.1.1.153:59595=>10.1.1.11:9332] Connected 03/05 20:41:49 Trace: [Broker:Misc] [remoting/brokerserver] [initconn 10.1.1.153:59595=>10.1.1.11:9332] Initialized Session because we couldn't resume 03/05 20:41:49 Trace: [Broker:Misc] [remoting/brokerserver] killing old client from 52b99a9c-2fd0-410d-a0cb-1f8c9d73aad2 because we have a new one 03/05 20:41:49 Info: [Broker:Misc] [remoting/serverconnectionv2] Client connected: 10.1.1.153:59595 03/05 20:41:49 Trace: [RemotingServerV2] [remoting/remotingserverv2] SENT NONFINAL DistributedBroker.ConnectResponse={ BrokerId=3e02c127-becc-4561-93c7-06bad905b6d2 BrokerName='streamer' } 03/05 20:41:49 Trace: [RemotingServerV2] [remoting/remotingserverv2] SENT NONFINAL DistributedBroker.UpdatesChangedResponse={ IsSupported=True WasJustUpdated=False Status='UpToDate' HasChangeLog=False CurrentVersion={ MachineValue=204701510 DisplayValue='2.47 (build 1510) production' Branch='production' } } 03/05 20:41:49 Trace: [Broker:Misc] [remoting/brokerserver] [initconn 10.1.1.153:59596=>10.1.1.11:9332] Connected 03/05 20:41:49 Trace: [Broker:Misc] [remoting/brokerserver] [initconn 10.1.1.153:59596=>10.1.1.11:9332] Initialized Session because we couldn't resume 03/05 20:41:49 Trace: [Broker:Misc] [remoting/brokerserver] killing old client from 52b99a9c-2fd0-410d-a0cb-1f8c9d73aad2 because we have a new one
Describe your network setup
Client is connected over WiFi. Both servers are wired, the existing is installed on a bare metal and the new one is a virtual machine. Everything is in the same subnet
What is your intention in setting up a second RoonServer while maintaining the first? Are you attempting to migrate from one machine to another, or do you intend to switch back and forth between servers, de-authorizing and re-authorizing as necessary?
With a single license, a client can only have an authorized session layer with a single RoonServer machine.
I was planning to install the new one and discontinue the use of my existing. I did have to switch the authorization. I just tried stopping my existing RoonServer to see if the behaviour of the new server was any different. It seemed to be doing the same.
We’re unfortunately not able to provide official support to anything running in a VM environment - are you able to move your setup outside of this and see if the same issue occurs?
We do have a dedicated area of community - our Tinkering category where others who choose to run Roon Server in a VM environment may be able to help further - let me know if you’d like me to move your thread to this category. Thanks for your understanding!
I don’t know if this is relevant, but 24.04 server network connectivity can be a bit temperamental because of potential conflicts between NetworkManager and netplan/networkd. Default Ubuntu Server configs don’t use NetworkManager, but some apps (such as Cockpit) require it. In that case, you need to tweak the conf to resolve the conflict.
My working instance is on 24.04 too. I tried an LXC of 24.04 and things work perfectly, so I am still confused why that one VM didn’t work. I might try 22.04 on the weekend. I was a little disappointed support offered nothing but ‘it is a VM we won’t help’. A common list of troubleshooting items regardless of the platform wouldn’t be much to ask. Either way, I am working now.
