After months of stability, Roon server not reachable

Support
1

Hello,

Core Machine (Operating system/System info/Roon build number)

6/29 12:27:28 Info: Starting RoonServer v1.6 (build 416) stable on linuxx64
06/29 12:27:28 Trace: Checking if we are already running
06/29 12:27:28 Warn: get lock file path: /tmp/.rnsems0-roon
06/29 12:27:28 Trace: Nope, we are the only one running
06/29 12:27:28 Info: Is 64 bit? True
06/29 12:27:28 Info: Command Line Argument: -watchdogport=37051
06/29 12:27:28 Trace: [childprocess] using .NET child process
06/29 12:27:28 Trace: [realtime] fetching time from NTP server
06/29 12:27:28 Trace: [realtime] Got time from NTP: 6/29/2019 10:27:28 AM (3770792848400ms)
06/29 12:27:28 Trace: [realtime] Updated clock skew to -00:00:00.0238790 (-23.879ms)
06/29 12:27:28 Info: [broker] starting 3cd1d781-2554-4cb0-b258-8e8aa79ded1c

[root@grendel Logs]# uname -a
Linux grendel.home 3.10.0-957.21.3.el7.x86_64 #1 SMP Tue Jun 18 16:35:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@grendel Logs]# cat /etc/redhat-release 
CentOS Linux release 7.6.1810 (Core)

Description Of Issue

Remotes + Endpoints don’t connect to Roon Server.

This morning (after months of running fine --and no changes to network or audio or server gear-- there was no connection to Roon server.

I restarted the Roon service - service was running, stopped and started without errors.

Connection to Soon server is still failing.

In /var/roon/RoonServer/Logs/RoonServer_log.txt these are the last entries:

06/29 12:29:30 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
06/29 12:29:30 Trace: [push] retrying connection in 47002ms
06/29 12:29:36 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] lost client connection. Retrying
06/29 12:29:36 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] connecting (attempt 1)
06/29 12:29:36 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
06/29 12:29:36 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] client connection failed. Retrying in 500ms
06/29 12:29:37 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] connecting (attempt 2)
06/29 12:29:37 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
06/29 12:29:37 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] client connection failed. Retrying in 750ms
06/29 12:29:37 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] connecting (attempt 3)
06/29 12:29:37 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
06/29 12:29:37 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] client connection failed. Retrying in 1125ms
06/29 12:29:38 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] connecting (attempt 4)
06/29 12:29:38 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
06/29 12:29:38 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] client connection failed. Retrying in 1687ms
06/29 12:29:40 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] connecting (attempt 5)
06/29 12:29:40 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
06/29 12:29:40 Trace: [raatserver] [RaatServer EREC @ 192.168.0.3:56583] client connection failed. Giving up
06/29 12:29:40 Trace: [raat] [sood] Refreshing device list
06/29 12:29:40 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
06/29 12:29:40 Trace: [push] connecting to 35.237.162.37:9200
06/29 12:29:40 Trace: [push] connected

It’s not clear to me what is failing to connect to what. The roonlabs.com IP is listed at the end of the logs, does it have something to do with connecting to Roon’s servers?

2

Your server is running and connects to the external Roon service. It is the Roon remote that is failing to connect.

Can you confirm the IP of your server and remote? These should be on the same subnet, e.g. 195.168.1.0. Also, do you have a firewall running on the server?

Try restarting your router.

In addition please provide a little more information about your setup including networking and devices.

4

Hi @CRo,

Can you provide some details about your current networking setup?

Is it only one remote experiencing this issue or are all remote devices unable to connect?

5

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.

6

Windows. 10. got. an. update. that. it. didn’t. ask. to. install.

I noticed this because I rebooted my windows PC and it said it was installing updates and I saw Intel ProSet Tools mentioned. I have two Intel NICs (X540 - 10gigE, and I210 - gigE on the Mobo). Aha.

-> Windows Roon app runs again.

Wouldn’t explain why for example the Web Remote Control (Roon extension) didn’t want to work. Or perhaps it does, because that is running in a browser on the Windows 10 PC.

-> Web Remote works again (as part of the Windows driver update reboot.)

Ok, so why didn’t the Android remotes want to work???

-> Oh, Wifi seems to be hung, as it’s downloading via 4G (cell) and not the WLAN. Lets reboot the Cell phone. OK.

Ok, what’s with the Ropiee and the Squeezeboxen? Well, I was trying to connect to those via Web, right? The NIC on the Windows 10 PC was in a bad state.

Sooooo. Thank you Microsoft.

Thanks dylan and Martin for calming me down. :wink:

2 Likes
7

Hi @CRo,

Thanks for the update here! Windows 10 does seem to like to sneak in updates sometimes, but glad to hear you were able to get to the bottom of the issue and that everything is working properly now :slight_smile:

8

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