Roonbridge disappears

John_Smith · July 2, 2020, 9:09pm

will try tomorrow

but as i said … it possible there are some dropouts? but i assume it has to somehow reconnect, right? even after internet dropout…

noris · July 2, 2020, 9:53pm

Yes, it should reconnect, but if your external adapter is completely dropping Roon communication it might have something to do with that, I would try the internal WiFi adapter as well, at least then we will have another data point.

John_Smith · July 3, 2020, 11:31am

looks like it has nothing with network … disappeared even on ethernet…

07/03 10:02:39 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [lua@0xb381578c] [10.0.1.44:33884] SENT [5] {“controls”:{“volume”:{“info”:{“con
fig”:{“device”:“hw:CARD=WT04,DEV=0”,“type”:“alsa”}},“step”:1.0,“min”:0.0,“value”:67,“mute”:false,“type”:“number”,“max”:100.0}},“status”:"S
u
07/03 10:12:39 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
07/03 10:12:39 Trace: [raatmanager] stopping device REIYIN Bluetooth Audio WT04
07/03 10:12:39 Trace: [raat_wrap] calling force_teardown on output
07/03 10:12:39 Trace: [raat_wrap] stopping RAAT device
07/03 10:12:39 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [device] stopping server
07/03 10:12:39 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [server] [10.0.1.44:33884] destroying client
07/03 10:12:39 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [session] [10.0.1.44:33884] destroying session
07/03 10:12:39 Trace: [RAAT::REIYIN Bluetooth Audio WT04] [device] run exited successfully
07/03 10:12:40 Trace: [raat_wrap] deleting device
07/03 10:12:40 Trace: [RAAT::REIYIN Bluetooth Audio WT04] deleting device
07/03 10:12:40 Trace: [RAAT::REIYIN Bluetooth Audio WT04] closing multicast
07/03 10:12:40 Trace: [RAAT::REIYIN Bluetooth Audio WT04] deleting server
07/03 10:12:40 Trace: [raat_wrap] deleting volume
07/03 10:12:40 Trace: [raat_wrap] deleting output
07/03 10:12:40 Trace: [raat_wrap] deleting transport
07/03 10:12:40 Trace: [raat_wrap] deleting log
07/03 10:12:40 Trace: [raat_wrap] freeing
07/03 10:12:40 Trace: [jsonserver] [10.0.1.44:55544] SENT [1] [nonfinal] {“status”: “DeviceChanged”, “device”: {“device_id”: “hw:CARD=WT04,DEV=0”, “type”: “alsa”, “name”: “REIYIN Bluetooth Audio WT04”, “config”: {“unique_id”: “d0af64ab-3b63-f5e7-8397-8d1a24b01877”, “output”: {
07/03 10:12:40 Trace: [jsonserver] [10.0.1.44:55544] SENT [2] {“status”: “Removed”}
07/03 10:12:40 Trace: [jsonserver] [10.0.1.44:55544] SENT [1] [nonfinal] {“status”: “DeviceRemoved”, “device”: {“device_id”: “hw:CARD=WT04,DEV=0”, “type”: “alsa”, “name”: “REIYIN Bluetooth Audio WT04”, “config”: {“unique_id”: “d0af64ab-3b63-f5e7-8397-8d1a24b01877”, “output”: {
07/03 10:12:42 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=
07/03 10:12:42 Trace: [raatmanager/linux] vendor= name=REIYIN Bluetooth Audio WT04
07/03 10:12:42 Trace: [raatmanager] [REIYIN Bluetooth Audio WT04] loaded config from /var/roon/RAATServer/Settings/device_d37bb02a099d3c1c442851225991baf9.json
07/03 10:22:40 Trace: [raatmanager/mac] LOST hw:CARD=WT04,DEV=0
07/03 10:22:42 Trace: [raatmanager/linux] FOUND id=hw:CARD=WT04,DEV=0 usb_id=

Logs/RoonBridge_log.txt
07/02 23:33:20 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:56658] SENT NONFINAL {“status”:“Success”,“updates”:{“is_supported”:true,“status”:“UpToDate”,“progress”:null,“current_version”:{“machine_value”:100700571,“branch”:“stable”,“display_value”:“1.7 (build 571) stable”},“available_version”:null,“update_mode”:“AutoCompatible”}}
07/03 00:12:53 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:56658] disconnected
07/03 00:12:53 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:57760] GOT {“request”:“updates_subscribe”}
07/03 00:12:53 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:57760] SENT NONFINAL {“status”:“Success”,“updates”:{“is_supported”:true,“status”:“UpToDate”,“progress”:null,“current_version”:{“machine_value”:100700571,“branch”:“stable”,“display_value”:“1.7 (build 571) stable”},“available_version”:null,“update_mode”:“AutoCompatible”}}
07/03 01:40:49 Trace: [push] short read from connector (1)
07/03 01:40:49 Trace: [push] retrying connection in 18771ms
07/03 01:41:09 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
07/03 01:41:09 Trace: [push] request to manager resulted in unsuccessful response: {“status”:“NotAvailable”}
07/03 01:41:09 Trace: [push] retrying connection in 28720ms
07/03 01:41:40 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
07/03 01:41:40 Trace: [push] request to manager resulted in unsuccessful response: {“status”:“NotAvailable”}
07/03 01:41:40 Trace: [push] retrying connection in 283722ms
07/03 01:46:23 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
07/03 01:46:23 Trace: [push] connecting to 34.75.173.253:9200
07/03 01:46:24 Trace: [push] connected
07/03 02:13:28 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:57760] disconnected
07/03 02:13:29 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:59120] GOT {“request”:“updates_subscribe”}
07/03 02:13:29 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:59120] SENT NONFINAL {“status”:“Success”,“updates”:{“is_supported”:true,“status”:“UpToDate”,“progress”:null,“current_version”:{“machine_value”:100700571,“branch”:“stable”,“display_value”:“1.7 (build 571) stable”},“available_version”:null,“update_mode”:“AutoCompatible”}}
07/03 04:18:47 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:59120] disconnected
07/03 08:05:32 Debug: ScanInBackground timer callback. serial: 9CE5F601-9B4A-4DF4-A922-D227C70FD3DA, userid: , product: RoonBridge, branding: , desired_branch: stable, version: 1.7 (build 571) stable
07/03 08:05:32 Debug: [base/updater] Checking for updates: https://updates.roonlabs.com/update/?v=2&serial=XXX&userid=&platform=linuxarmv7hf&product=RoonBridge&branding=&curbranch=stable&version=100700571&branch=stable
07/03 08:05:33 Debug: [appupdater] Update not needed
07/03 08:33:24 Trace: [push] short read from connector (1)
07/03 08:33:24 Trace: [push] retrying connection in 75718ms
07/03 08:34:40 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
07/03 08:34:40 Trace: [push] connecting to 35.231.45.188:9200
07/03 08:34:40 Trace: [push] connected
07/03 11:25:49 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:40766] GOT {“request”:“updates_subscribe”}
07/03 11:25:49 Trace: [rnet/RnetJsonServer] [client 10.0.1.24:40766] SENT NONFINAL {“status”:“Success”,“updates”:{“is_supported”:true,“status”:“UpToDate”,“progress”:null,“current_version”:{“machine_value”:100700571,“branch”:“stable”,“display_value”:“1.7 (build 571) stable”},“available_version”:null,“update_mode”:“AutoCompatible”}}

John_Smith · July 4, 2020, 10:43am

ok retested with ethernet again dropped out … from roon endpoints…
any idea here?

noris · July 7, 2020, 6:11pm

Hi @John_Smith,

Here it looks like your network on the Bridge dropped out as it lost connection to our servers. Do you have any jobs running on it which could reset the network stack? Have you tried reinstalling the Bridge Software?

John_Smith · July 7, 2020, 6:38pm

@noris well my question why its not get reconnected… ?

havent tried to reinstall it … .but nothing is running its fresh bananian install

noris · July 9, 2020, 5:20am

Hi @John_Smith,

Can you please provide your full setup details including:

Core model/manufacturer
Network setup
A full copy of the full set of your Core when this occurs
A full copy of your Bridge logs when this occurs

Have you tried any other OS’s on the Bridge?
Perhaps this is an issue just impacting Bananian?

John_Smith · July 24, 2020, 10:26pm

@noris too much details

core is VM
network is standard setup, bananian is connected via wifi / eth to local network

as issue is happening randomly i am not able to get logs from the time it happened on time

i provided so many logs here…

no other OS was tried as i dont know if any other is supported for bananian

dont know what it impacts…

noris · July 28, 2020, 1:13am

Hi @John_Smith,

I suggest we first start off by eliminating the VM from the equation, do you have another Windows or Mac PC you can try to use as the Core? I would be interested to know if it auto re-connects on a standard OS-type Core.

John_Smith · July 31, 2020, 9:37am

@noris … which is strange… i think these days there is no diff running inside VM compare to physical hw… isnt it?

i restarted the core - and endpoint disappeared… so on the endpoint i executed

root@bananapi ~ # /etc/init.d/roonbridge restart
[ ok ] Stopping RoonBridge:.
[…] Starting RoonBridge:Daemon is running as PID 4835
. ok

no change… endpoint not shown in the list of endpoinds

I forced a kill of roonbridge

root@bananapi ~ # ps aux | grep -i roon
root 2415 0.0 2.6 78944 26268 ? Sl Jul30 0:06 RoonBridge --debug --gc=sgen --server RoonBridge.exe
root 2444 0.6 5.3 108224 53144 ? Sl Jul30 4:56 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe
root 2450 0.0 0.0 1684 292 ? S Jul30 0:00 /opt/RoonBridge/Bridge/processreaper 2444
root 4871 0.0 0.0 3664 800 pts/0 S+ 09:34 0:00 grep --color=auto -i roon
root@bananapi ~ # kill -9 2415
root@bananapi ~ # kill -9 2444
kill: kill 2444 failed: no such process

executed start of the bridge >

1 root@bananapi ~ # /etc/init.d/roonbridge start

Endpoint now shows in list …

so isnt that strange? Even Restart is broken…
[…] Starting RoonBridge:Daemon is running as PID 4884
. ok
root@bananapi ~ #

noris · August 5, 2020, 3:48am

Hi @John_Smith,

Thanks for those snippets. I spoke to the team and we will need a clear test to proceed here, can I please ask you to:

Note the exact local time + date that you encounter this issue and let me know here.
Send me a set of both your Core and Roon Bridge full logs folder. It’s best to send via Dropbox / Google Drive, but if you don’t have either I can also create an account for you on our diagnostics servers.

system · August 5, 2021, 3:48am

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