Roon - Pi 4 - Ubuntu - Bridge not connecting

Happy Roon customer for several months now. New issues cropped up today making me music-less. :frowning:

Weird issue just happened this morning. First, the setup:

Core: AMD A10 running Ubuntu 20.04 LTS (yeah, still technically pre-release)
Bridge: Pi 4 / 4 GB running Ubuntu 19.10

At some point recently I upgraded packages to the latest.

The issue is that the core doesn’t see the bridge anymore, and I can’t select it to play. Sorry I don’t have any idea how to diagnose. Found a few log files, they looked “normal.” Started the bridge and core in command line mode, and didn’t see anything weird from the messages.

Help!

Are you running UFW on the Core?

I checked, for kicks, and it looks like it is inactive:

$ ufw status
Status: inactive

Reboot the RPi, see if that helps. I can’t help with 20.04 as I’m still on 18.04 (where my core resides) and won’t consider 20.04 until next year earliest. I use Ropieee for my bridges and these reboot every evening.

Thanks, already rebooted the Pi about a dozen times. :frowning:

1 Like

Maybe a daft question, but RoonBridge is definitely running?

sudo systemctl status roonbridge

Yep. Same thing happens if I kill it and run it in a console session, so I can watch the error messages.

If there are error messages can you post them.

Oh, wait, just saw something interesting, what is RAATserver??

roonbridge.service - RoonBridge
Loaded: loaded (/etc/systemd/system/roonbridge.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-04-16 15:10:51 PDT; 21min ago
Main PID: 1507 (start.sh)
Tasks: 36 (limit: 4430)
CGroup: /system.slice/roonbridge.service
├─1507 /bin/sh /opt/RoonBridge/start.sh
├─1516 RoonBridge --debug --gc=sgen --server RoonBridge.exe
├─1638 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe
├─1643 /opt/RoonBridge/Bridge/processreaper 1638
└─1648 RAATServer --debug --gc=sgen --server RAATServer.exe

Apr 16 15:10:51 quattro systemd[1]: Started RoonBridge.
Apr 16 15:10:52 quattro start.sh[1507]: 00:00:00.008 Warn: get lock file path: /tmp/.rnbgem0-
Apr 16 15:10:53 quattro start.sh[1507]: 00:00:00.227 Trace: [childprocess] using unix child process
Apr 16 15:10:53 quattro start.sh[1507]: Initializing
Apr 16 15:10:53 quattro start.sh[1507]: 00:00:00.378 Info: Starting /opt/RoonBridge/Bridge/RoonBridgeHelper
Apr 16 15:10:53 quattro start.sh[1507]: 00:00:00.395 Info: ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBrid
Apr 16 15:10:53 quattro start.sh[1507]: Not Running (.o)
Apr 16 15:10:53 quattro start.sh[1507]: 00:00:00.015 Warn: get lock file path: /tmp/.rnbhgem0-
Apr 16 15:10:54 quattro start.sh[1507]: Running

But no visible error messages I can find, but again, I don’t know what the log files should look like.

Issue fixed.

Apparently the DAC was what needed to be rebooted. I had very poor indicators of what was going on via the UI though. From there it looked as if the Bridge was just not there.

1 Like