Roon has been Crashing every week or so over past month and today can't get it back

Support
#1

Small Green Sonic Transporter running 2.8 (latest)

Networking Gear & Setup Details

Micro Rendu, Sim/Moon Audio Ace, Allo Bridge, and Roon Bridge on Windows 10 PC
3 hard wired, 1 wireless

Connected Audio Devices

Micro Rendu, Sim/Moon Audio Ace, Allo Bridge, and Roon Bridge on Windows 10 PC
3 hard wired, 1 wireless

Number of Tracks in Library

50,000 +

Description of Issue

About once a week Roon has been Crashing. I can connect to server. I can do software reboot’s upgrades, and have followed this in past with success:

  • { margin: 0; padding: 0; } body.gmnewnote { border: 1px solid #888; font-size: 8pt; font-family: “tahoma”; } table.gmnotestable { width: 99.5%; border-collapse: collapse; border-spacing: 0; font-size: 8pt; font-family: “tahoma”;} td.gmnotestable { vertical-align: text-top; padding: 2px; padding-bottom: 0.5em; border: 1px solid #888; } td.gmleftcol { width: 18em; }

Sonicorbiter.com → Manage → Apps → Software Manager → press the update button
Reboot
Go to
sonicorbiter.com → Manage → Settings → Roon Server
And press Save Changes

But today no go. None of my devices or Roon bridge will connect.

#3

Hi @Jay_Kaufman,

I’m sorry to hear you’ve had connection issues. I decided to enable remote diagnostics and found some errors that are relevant to the reported case. When this happens, the core is unavailable to your mobile devices and endpoints.

There are so many possibilities, from networking to device problems, but either way; the core is losing its connectivity. I might suggest that you ensure that all updates are installed on the core and if that doesn’t work, a hard reset might be in order. In addition to this, follow the network path from the core to the router and reset things along the way. Try different cables or different ports etc. Also, check firewalls to ensure proper exceptions are in place.

09/01 08:15:13 Warn: [streammediafile] error reading stream: Unable to read data from the transport connection: Software caused connection abort.
09/01 08:15:16 Trace: [remoting/brokerserver] [initconn 192.168.86.x:45756=>192.168.86.x:9332] Connected
09/01 08:15:16 Warn: [remoting/brokerserver] [initconn 192.168.86.x:45756=>192.168.86.x:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: 30be0e47-c1f3-40dc-a21b-1ed2e5967045
   at Sooloos.Broker.Distributed.InitConnectionV2.Go()
09/01 08:15:21 Trace: [remoting/brokerserver] [initconn 192.168.86.x:45757=>192.168.86.x:9332] Connected
09/01 08:15:21 Warn: [remoting/brokerserver] [initconn 192.168.86.x:45757=>192.168.86.x:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: 30be0e47-c1f3-40dc-a21b-1ed2e5967045
   at Sooloos.Broker.Distributed.InitConnectionV2.Go()
09/01 08:15:26 Info: [stats] 24369mb Virtual, 3835mb Physical, 1503mb Managed, 329 Handles, 80 Threads
09/01 08:15:27 Trace: [remoting/brokerserver] [initconn 192.168.86.x:45758=>192.168.86.x:9332] Connected
09/01 08:15:27 Warn: [remoting/brokerserver] [initconn 192.168.86.x:45758=>192.168.86.x:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: 30be0e47-c1f3-40dc-a21b-1ed2e5967045
   at Sooloos.Broker.Distributed.InitConnectionV2.Go()
09/01 08:15:29 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection.
09/01 08:15:29 Trace: [raatserver] [RaatServer SM-T220 @ 192.168.86.x:9200] lost client connection. Retrying'''