Unable to access Roon after updating Wyred4Sound Essential MS Linux system (ref#XIR1XB)

Support
1

Is Roon Server running?

· No, Roon Server is not running.

For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.

· I can't turn on Roon Server, I need help.

Describe the issue

I have a Wyred4Sound Essential MS. In readiness for the imminent Roon update I successfully updated the Linux system from 2.7 to 2.8. After numerous attempts - network chesks, Roon reinstall - I can't access Roon any more. It's gone from bad to worse. I hope you can help.

Describe your network setup

Sky Max Hub, Wyred4Sound Essential MS running Linux 2.8. Ethernet cable from router to server. Optical link to one Devialet Phantom 1 speaker. Wireless connection to second Phantom 1. One netgear umanaged swirtch.

2

Hello @Jayk,

We were able to enable diagnostics for your account and pull the latest logs from your server. Having reviewed them closely, we can definitively confirm that the issue is not with the Roon software itself, but rather with how the Wyred4Sound operating system is handling your local network connection after the 2.8 update.

The diagnostic reports are flooded with system-level network failures. Specifically, we are seeing continuous No route to host errors when Roon tries to communicate with other devices on your local network, alongside constant network reachability changed events.

This behavior indicates that the Wyred4Sound device’s network interface is repeatedly dropping its connection or completely failing to establish a stable routing path to your Sky Max Hub. Because these network drops are happening at the operating system level, the Roon Server process is essentially being blocked from communicating over your network.

04/19 23:33:48 Trace: [raatmanager] updating network interfaces
04/19 23:33:48 Trace: [discovery] stopping
04/19 23:33:48 Trace: closing multicast
04/19 23:33:48 Trace: [discovery] closing unicast send socket
04/19 23:33:48 Trace: [discovery] closing unicast recv socket
04/19 23:33:48 Trace: [discovery] starting
04/19 23:33:48 Info: [discovery] [iface:lo:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003
04/19 23:33:48 Info: [discovery] [iface:lo:127.0.0.1] multicast send socket is bound to 0.0.0.0:60828
04/19 23:33:48 Info: [discovery] [iface:eth0:192.168.0.172] multicast recv socket is bound to 0.0.0.0:9003
04/19 23:33:48 Info: [discovery] [iface:eth0:192.168.0.172] multicast send socket is bound to 0.0.0.0:43959
04/19 23:33:48 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
04/19 23:33:48 Debug: [discovery] broadcast op is complete
04/19 23:02:23 [Local 04/20 00:02:23] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.196:9200] connecting (attempt 1)
04/19 23:02:26 [Local 04/20 00:02:26] Warn: [rnet/RnetJsonClient] failed to connect No route to host
04/19 23:02:26 [Local 04/20 00:02:26] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] client connection failed. Retrying in 500ms
04/19 23:02:27 [Local 04/20 00:02:27] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] connecting (attempt 2)
04/19 23:02:28 [Local 04/20 00:02:28] Info: [stats] 5678mb Virtual, 1300mb Physical, 544mb Managed, 756mb estimated Unmanaged, 376 Handles, 68 Threads, 0.32% of runtime in GC pauses, 6ms last GC pause duration
04/19 23:02:30 [Local 04/20 00:02:30] Warn: [rnet/RnetJsonClient] failed to connect No route to host
04/19 23:02:30 [Local 04/20 00:02:30] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] client connection failed. Retrying in 750ms
04/19 23:02:30 [Local 04/20 00:02:30] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] connecting (attempt 3)
04/19 23:02:32 [Local 04/20 00:02:32] Error: [cast/client] [BRAVIA-4K-GB-ffde774e8c80a293e9b6e563d132f49d._googlecast._tcp.local] Unable to authenticate TLS connection
04/19 23:02:33 [Local 04/20 00:02:33] Warn: [rnet/RnetJsonClient] failed to connect No route to host
04/19 23:02:33 [Local 04/20 00:02:33] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] client connection failed. Retrying in 1125ms
04/19 23:02:34 [Local 04/20 00:02:34] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] connecting (attempt 4)
04/19 23:02:36 [Local 04/20 00:02:36] Warn: [rnet/RnetJsonClient] failed to connect No route to host
04/19 23:02:36 [Local 04/20 00:02:36] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] client connection failed. Retrying in 1687ms
04/19 23:02:37 [Local 04/20 00:02:37] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] connecting (attempt 5)
04/19 23:02:39 [Local 04/20 00:02:39] Warn: [rnet/RnetJsonClient] failed to connect No route to host
04/19 23:02:39 [Local 04/20 00:02:39] Trace: [raatserver] [RaatServer JeffsMacStudio @ 192.168.0.102:9200] client connection failed. Giving up
04/19 23:02:39 [Local 04/20 00:02:39] Trace: [raat] [sood] Refreshing device list

You now have concrete data to take back to the manufacturer. Please provide these specific findings to Wyred4Sound support. Knowing that the 2.8 firmware update caused severe local network routing errors and constant reachability drops will give their engineers exactly what they need to pinpoint the bug in their OS.

3

I suspect the errors reported are a consequence of my attempts to fix things. Good news - I am now reconnected and appear to be fully operational.