After months of stability, Roon server not reachable

Hi,

I’ve done a very detailed and deep analyses of the networking setup in the work to solve a previous problem (which got solved!), so, the setup is documented and most importantly it works (well, until today).

From that thread, nothing has changed. Briefly sumarized, it’s one flat subnet, there are two switches and the CentOS Roon server.

New is, all of the edge devices (Remotes, Endpoints, Squeezeboxen, and the full PC Roon Install (remote + endpoint) can’t connect anymore.

Here are the entries when starting the PC client just now:

06/29 18:37:41 Trace: [raat] RAATServer discovered: RaatServer EREC @ 192.168.2.3:63748
06/29 18:37:41 Info: [raatserver] GOT SERVER 9a402394-12eb-12b3-3db9-a9c81ee65b83::430ba114-c5e9-4e52-9ad3-9febb4586112 @ 192.168.2.3:63748 EREC PROTOVER=1 RAATVER=1.1.36 
06/29 18:37:41 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
06/29 18:37:41 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] connecting (attempt 1)
06/29 18:37:41 Trace: [push] retrying connection in 20186ms
06/29 18:37:41 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] connected
06/29 18:37:41 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
06/29 18:37:41 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"device_id": "default", "name": "System Output", "type": "wasapi", "is_system_output": true}, {"device_id": "{0.0.0.00000000}.{58288071-8d11-47b7-97ce-770dd2fc630a}", "name": "ASUS Xonar DSX Audio Device", "type": "wasapi"}, {"device_id": "{0.0.0.00000000}.{5c263002-c3a1-403f-af1a-1f95a083184a}", "name": "ASUS Xonar DSX Audio Device", "type": "wasapi"}, {"device_id": "{71E563CB-2BEB-4AF6-9F4B-2629AC49314F}", "name": "ASUS Xonar ASIO driver (64)", "type": "asio", "config": {"unique_id": "f95818d8-a8ca-d027-c5e5-da7606f1eed9", "output": {"name": "ASUS Xonar ASIO driver (64)", "type": "asio", "dsd_mode": "none", "device": "{71E563CB-2BEB-4AF6-9F4B-2629AC49314F}", "force_max_volume": false}, "external_config": {"is_private": true}}}, {"device_id": "{64083009-BD64-42AA-ADA3-73F51E17CAD7}", "name": "iFi (by AMR) HD USB Audio", "type": "asio", "config": {"unique_id": "ef716a89-df35-0f7a-6db0-f4973adfd2cf", "output": {"name": "iFi (by AMR) HD USB Audio", "type": "asio", "dsd_mode": "native", "device": "{64083009-BD64-42AA-ADA3-73F51E17CAD7}", "force_max_volume": false}, "external_config": {"is_private": true}}}]}
06/29 18:37:41 Info: [raatserver] GOT DEVICE 430ba114-c5e9-4e52-9ad3-9febb4586112::default Type=wasapi Name=System Output 
06/29 18:37:41 Info: [raatserver] GOT DEVICE 430ba114-c5e9-4e52-9ad3-9febb4586112::{0.0.0.00000000}.{58288071-8d11-47b7-97ce-770dd2fc630a} Type=wasapi Name=ASUS Xonar DSX Audio Device 
06/29 18:37:41 Info: [raatserver] GOT DEVICE 430ba114-c5e9-4e52-9ad3-9febb4586112::{0.0.0.00000000}.{5c263002-c3a1-403f-af1a-1f95a083184a} Type=wasapi Name=ASUS Xonar DSX Audio Device 
06/29 18:37:41 Info: [raatserver] GOT DEVICE 430ba114-c5e9-4e52-9ad3-9febb4586112::{71E563CB-2BEB-4AF6-9F4B-2629AC49314F} Type=asio Name=ASUS Xonar ASIO driver (64) 
06/29 18:37:41 Info: [raatserver] GOT DEVICE 430ba114-c5e9-4e52-9ad3-9febb4586112::{64083009-BD64-42AA-ADA3-73F51E17CAD7} Type=asio Name=iFi (by AMR) HD USB Audio 
06/29 18:37:41 Trace: [rnet/RnetJsonClient] SENT {"request":"enable_device","device_id":"{64083009-BD64-42AA-ADA3-73F51E17CAD7}","subscription_id":"3"}
06/29 18:37:41 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "DeviceChanged", "device": {"device_id": "{64083009-BD64-42AA-ADA3-73F51E17CAD7}", "name": "iFi (by AMR) HD USB Audio", "error_message": "DeviceOpenFailed", "type": "asio", "config": {"unique_id": "ef716a89-df35-0f7a-6db0-f4973adfd2cf", "output": {"name": "iFi (by AMR) HD USB Audio", "type": "asio", "dsd_mode": "native", "device": "{64083009-BD64-42AA-ADA3-73F51E17CAD7}", "force_max_volume": false}, "external_config": {"is_private": true}}}}
06/29 18:37:41 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "DeviceInitFailed"}
06/29 18:37:48 Info: [stats] 2639mb Virtual, 391mb Physical, 146mb Managed, 0 Handles, 58 Threads
06/29 18:37:50 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] lost client connection. Retrying
06/29 18:37:50 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] connecting (attempt 1)
06/29 18:37:50 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
06/29 18:37:50 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] client connection failed. Retrying in 500ms
06/29 18:37:51 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] connecting (attempt 2)
06/29 18:37:51 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
06/29 18:37:51 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] client connection failed. Retrying in 750ms
06/29 18:37:51 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
06/29 18:37:51 Trace: [push] connecting to 34.74.199.160:9200
06/29 18:37:51 Trace: [push] connected
06/29 18:37:51 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] connecting (attempt 3)
06/29 18:37:51 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
06/29 18:37:51 Trace: [raatserver] [RaatServer EREC @ 192.168.2.3:63748] client connection failed. Retrying in 1125ms

What I will do now is reboot everything. =) And I’ll look at the OS logs to see if anything changed that I’m not taking into account.