Roonbridge and boot issues on pi zero 2w

[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