Roonbridge and boot issues on pi zero 2w

[phorize]

I'm wondering if any other pi zero 2 w users are having boot failure following installation of the armv8 roon bridge. This should work running 64 bit moodeaudio 9.05 but I can't get the system to restart once I've run the room install script. I've tried a few times to a fresh moode install and the problem is persistent.

[Tim Curtis]

Try the following on a fresh install.

After installing roonbridge run the command below so it does not automatically start during boot.

Code:

sudo systemctl disable roonbridge

sudo reboot

Then assuming the system boots successfully try starting roonbrodge and see what happens.

Code:

sudo systemctl start roonbridge

systemctl status roonbridge

[phorize]

Try the following on a fresh install.

After installing roonbridge run the command below so it does not automatically start during boot.

Code:

sudo systemctl disable roonbridge

sudo reboot

Then assuming the system boots successfully try starting roonbrodge and see what happens.

Code:

sudo systemctl start roonbridge

systemctl status roonbridge

Thanks Tim. I disabled roon as above. Still getting the boot failure. I'm going to look at the roon forum as there must be others getting this. I'll get hold of a micro hdmi cable this week and look at what is happening on a screen.

[phorize]

I got so fed up messing around with roon bridge that I decided to stop using the service. The functionality is good but the Linux documentation is dire given it's supposed to be officially supported. I feel better already.

[TheOldPresbyope]

Not sure what's happening with your install.

I'm not usng roon here but I was curious enough to try running the roonbridge installer script on a fresh moOde 9.0.6 on a Pi Zero 2W.

Once the script finished  running, I checked the service

Code:

rho@puce:~ $ systemctl status roonbridge
● roonbridge.service - RoonBridge
    Loaded: loaded (/etc/systemd/system/roonbridge.service; enabled; preset: enabled)
    Active: active (running) since Thu 2024-08-08 17:29:51 EDT; 1min 39s ago
  Main PID: 2082 (start.sh)
     Tasks: 30 (limit: 187)
       CPU: 21.551s
    CGroup: /system.slice/roonbridge.service
            ├─2082 /bin/sh /opt/RoonBridge/start.sh
            ├─2085 RoonBridge --debug --gc=sgen --server RoonBridge.exe
            ├─2107 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe
            ├─2113 /opt/RoonBridge/Bridge/processreaper 2107
            └─2117 RAATServer --debug --gc=sgen --server RAATServer.exe

Aug 08 17:29:53 puce start.sh[2085]: 00:00:00.742 Debug: PathForResource, filename: RAATServer
Aug 08 17:29:53 puce start.sh[2085]: 00:00:00.742 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/RAATServer
Aug 08 17:29:53 puce start.sh[2085]: 00:00:00.743 Debug: PathForResource, filename: RoonBridgeHelper
Aug 08 17:29:53 puce start.sh[2085]: 00:00:00.743 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/RoonBridgeHelper
Aug 08 17:29:53 puce start.sh[2085]: Initializing
Aug 08 17:29:53 puce start.sh[2085]: 00:00:00.812 Info:  Starting /opt/RoonBridge/Bridge/RoonBridgeHelper
Aug 08 17:29:53 puce start.sh[2085]: 00:00:00.857 Info:  ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer
Aug 08 17:29:53 puce start.sh[2085]: Not Running (.o)
Aug 08 17:29:54 puce start.sh[2107]: 00:00:00.043 Warn:  get lock file path: /tmp/.rnbhgem0-
Aug 08 17:29:54 puce start.sh[2085]: Running

I then restarted moOde from the WebUI.

After it showed up on my network again I checked the service again

Code:

rho@puce:~ $ systemctl status roonbridge
○ roonbridge.service - RoonBridge
    Loaded: loaded (/etc/systemd/system/roonbridge.service; disabled; preset: enabled)
    Active: inactive (dead)

Aug 08 17:34:08 puce start.sh[552]: Not Running (.o)
Aug 08 17:34:09 puce start.sh[628]: 00:00:00.048 Warn:  get lock file path: /tmp/.rnbhgem0-
Aug 08 17:34:10 puce start.sh[552]: Running
Aug 08 17:35:06 puce systemd[1]: Stopping roonbridge.service - RoonBridge...
Aug 08 17:35:06 puce systemd[1]: roonbridge.service: Killing process 600 (SGen worker) with signal SIGKILL.
Aug 08 17:35:06 puce systemd[1]: roonbridge.service: Killing process 633 (SGen worker) with signal SIGKILL.
Aug 08 17:35:06 puce systemd[1]: roonbridge.service: Killing process 668 (SGen worker) with signal SIGKILL.
Aug 08 17:35:06 puce systemd[1]: roonbridge.service: Deactivated successfully.
Aug 08 17:35:06 puce systemd[1]: Stopped roonbridge.service - RoonBridge.
Aug 08 17:35:06 puce systemd[1]: roonbridge.service: Consumed 22.628s CPU time.

The RoonBridge service ON/OFF button in moOde's Renderer config panel is unresponsive.

So, in my case least, the P and moOde restart. No idea what's up with the roonbridge service though.


Regards,
Kent

[Tim Curtis]

Here's the rb code in worker.php

Code:

// RoonBridge
// Their installer sets the systemd unit to enabled but we need it disabled because we start/stop it via System Config setting
if (file_exists('/opt/RoonBridge/start.sh') === true) {
    $_SESSION['roonbridge_installed'] = 'yes';
    if (sysCmd('systemctl is-enabled roonbridge')[0] == 'enabled') {
        sysCmd('systemctl disable roonbridge');
        sysCmd('systemctl stop roonbridge');
        $msg = 'installed, systemd unit set to disabled';
    }
} else {
    $_SESSION['roonbridge_installed'] = 'no';
    $msg = 'not installed';
}
workerLog('worker: RoonBridge:       ' . $msg);

Try checking some of the conditions:
1. Existence of file /opt/RoonBridge/start.sh
2. Session var 'roonbridge_installed' set to 'yes'
sudo moodeutl -d -gv roonbridge_installed
3. Feature enabled
moodeutl -a should show
128     y       RoonBridge renderer

[TheOldPresbyope]

Seems to pass all the suggested checks.

Oddly, /opt/RoonBridge and all its subdirectories and contents have ownership 1001:116 rather than the root:root (e.g., 0:0) I was expecting.

Just for grins I started from scratch with yet another fresh moOde 9.0.6 on the Pi Zero 2W.

This time the RoonBridge renderer started upon reboot and the RoonBridge section on the moOde Renderer Config panel is alive. Ownership of the relevant material is again 1001:116 and I left it that way.

No idea what went wrong the first time. Before giving up on it I did try changing ownership of the relevant material to root:root. After cold starting moOde, the RoonBridge Renderer started. I can't point to the step that "fixed" the original failure which is why I started over from scratch.

Regards,
Kent

[Tim Curtis]

Good to hear the install eventually works.

[phorize]

Interesting thoughts, thank you for investigating. TBH roon obviously has no interest in properly supporting users with its Linux binaries. I feel embarrassed that this has taken your attention away from more productive activities!

[Tim Curtis]

No trouble at all. Has anyone interacted with Roon dev's on their Forum regarding roonbriodge?