Try to install/run roon_bridge on ARMv7 devices from Raumfeld

Tinkering
1

Hi, I am trying to install/run roon bridge on an ARMv7 device from raumfeld/teufel. Its an older device but it has neon support. The install script finishes and i can start the bridge but the RAAT Server seems to exits (exit code =0) without any error messages after a few seconds. The RAATServer log shows this:

12/29 11:50:50 Info: Starting RAATServer v1.8 (build 1125) stable on linuxarmv7hf
12/29 11:50:51 Info: Local time is 12/29/2025 11:50:50, UTC time is 12/29/2025 10:50:50
12/29 11:50:52 Trace: [RAATServer] detected ALSA support
12/29 11:50:54 Trace: [bits] myinfo: {"os":"Linux 6.6.64","platform":"linuxarmv7hf","machineversion":100801125,"branch":"stable","appmodifier":"","appname":"RAATServer"}
12/29 11:50:56 Info: [RAATServer] creating RAAT__manager
12/29 11:50:56 Info: [RAATServer]     appdata_dir  = /root/.RAATServer
12/29 11:50:56 Info: [RAATServer]     unique_id    = 381ec600-3f8d-447b-bdb3-ba55e02b87fc
12/29 11:50:56 Info: [RAATServer]     machine_id   = 1669713c-291a-b18d-a4fa-72100c1ae866
12/29 11:50:56 Info: [RAATServer]     machine_name = trixie
12/29 11:50:56 Info: [RAATServer]     os_version   = Linux 6.6.64
12/29 11:50:56 Info: [RAATServer]     vendor       = 
12/29 11:50:56 Info: [RAATServer]     model        = 
12/29 11:50:56 Info: [RAATServer]     service_id   = d7634b85-8190-470f-aa51-6cb5538dc1b9
12/29 11:50:56 Info: [RAATServer]     is_dev       = False
12/29 11:50:56 Trace: [raatmanager] starting
12/29 11:50:56 Trace: [raatmanager/linux] FOUND id=hw:CARD=Element,DEV=0 usb_id=
12/29 11:50:56 Trace: [raatmanager/linux]       vendor=                               name=Element                       
12/29 11:50:56 Trace: [raatmanager] initialized
12/29 11:50:57 Info: [RAATServer] running RAAT__manager
12/29 11:50:57 Trace: [raatmanager] starting discovery
12/29 11:50:57 Trace: [discovery] starting
12/29 11:50:57 Info: [discovery] [iface:lo:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003
12/29 11:50:57 Info: [discovery] [iface:lo:127.0.0.1] multicast send socket is bound to 0.0.0.0:51198
12/29 11:50:57 Info: [discovery] [iface:eth0:10.0.0.48] multicast recv socket is bound to 0.0.0.0:9003
12/29 11:50:57 Info: [discovery] [iface:eth0:10.0.0.48] multicast send socket is bound to 0.0.0.0:34996
12/29 11:50:57 Info: [discovery] [iface:mlan0:10.0.0.208] multicast recv socket is bound to 0.0.0.0:9003
12/29 11:50:57 Info: [discovery] [iface:mlan0:10.0.0.208] multicast send socket is bound to 0.0.0.0:46760
12/29 11:50:57 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
12/29 11:50:57 Trace: [raatmanager] starting server
12/29 11:50:57 Info: [jsonserver] listening on port 9200
12/29 11:50:57 Trace: [raatmanager] announcing
12/29 11:50:57 Debug: [discovery] broadcast op is complete
12/29 11:50:58 Trace: [inetdiscovery] added device raatserver/381ec600-3f8d-447b-bdb3-ba55e02b87fc in addr:__ADDR__
12/29 11:50:58 Trace: [inetdiscovery] added service com.roonlabs.raatserver.tcp for device raatserver/381ec600-3f8d-447b-bdb3-ba55e02b87fc

Starting the bridge log, this goes on forever:

00:00:00.046 Warn:  get lock file path: /tmp/.rnbgem0-
00:00:01.729 Trace: [childprocess] using unix child process
00:00:02.020 Debug: PathForResource, filename: ../.update
00:00:02.090 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/../.update
00:00:02.125 Debug: PathForResource, filename: RAATServer
00:00:02.125 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/RAATServer
00:00:02.140 Debug: PathForResource, filename: RoonBridgeHelper
00:00:02.141 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/RoonBridgeHelper
Initializing
00:00:02.455 Info:  ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer
00:00:02.809 Info:  Starting /opt/RoonBridge/Bridge/RoonBridgeHelper
Not Running (.o)
00:00:00.241 Warn:  get lock file path: /tmp/.rnbhgem0-
Running
00:00:18.047 Warn:  exception starting raatserver: System.Net.Sockets.SocketException (0x80004005): Connection refused
  at System.Net.Sockets.TcpClient..ctor (System.String hostname, System.Int32 port) [0x0006d] in <ef2b8cc0336c473382f0e9112dd3c795>:0
  at Sooloos.RAATServer.ConnectOrStartAndWaitForExit (System.String path, System.String args, System.Action`1[T] status, Base.ChildProcess& p) [0x00165] in <c3e2d33b54f34224bdf8da1e4595ee94>:0
Not Running (.o)
00:00:18.284 Debug: PathForResource, filename: ../.update
00:00:18.284 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/../.update
00:00:20.285 Info:  ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer
Running
00:00:26.322 Warn:  exception starting raatserver: System.Net.Sockets.SocketException (0x80004005): Connection refused
  at System.Net.Sockets.TcpClient..ctor (System.String hostname, System.Int32 port) [0x0006d] in <ef2b8cc0336c473382f0e9112dd3c795>:0
  at Sooloos.RAATServer.ConnectOrStartAndWaitForExit (System.String path, System.String args, System.Action`1[T] status, Base.ChildProcess& p) [0x00165] in <c3e2d33b54f34224bdf8da1e4595ee94>:0
00:00:26.369 Debug: PathForResource, filename: ../.update
00:00:26.369 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/../.update
Not Running (.o)
00:00:28.378 Info:  ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer
Running
00:00:34.422 Warn:  exception starting raatserver: System.Net.Sockets.SocketException (0x80004005): Connection refused
  at System.Net.Sockets.TcpClient..ctor (System.String hostname, System.Int32 port) [0x0006d] in <ef2b8cc0336c473382f0e9112dd3c795>:0
  at Sooloos.RAATServer.ConnectOrStartAndWaitForExit (System.String path, System.String args, System.Action`1[T] status, Base.ChildProcess& p) [0x00165] in <c3e2d33b54f34224bdf8da1e4595ee94>:0
00:00:34.439 Debug: PathForResource, filename: ../.update
00:00:34.439 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/../.update
Not Running (.o)
00:00:36.448 Info:  ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer
Running
00:00:42.475 Warn:  exception starting raatserver: System.Net.Sockets.SocketException (0x80004005): Connection refused
  at System.Net.Sockets.TcpClient..ctor (System.String hostname, System.Int32 port) [0x0006d] in <ef2b8cc0336c473382f0e9112dd3c795>:0
  at Sooloos.RAATServer.ConnectOrStartAndWaitForExit (System.String path, System.String args, System.Action`1[T] status, Base.ChildProcess& p) [0x00165] in <c3e2d33b54f34224bdf8da1e4595ee94>:0
Not Running (.o)
00:00:42.500 Debug: PathForResource, filename: ../.update
00:00:42.500 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/../.update
00:00:44.501 Info:  ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer
Running

Any ideas?

2

RAATServer actually starts fine and listens on port 9200. The problem is the Bridge can’t connect to it afterwards, which suggests RAATServer exits before the Bridge establishes the connection.

Is RAATServer still running after startup? Check with ps aux | grep RAAT while the Bridge is trying to connect.

Maybe check if there’s anything in dmesg that shows RAATServer being killed because of memory issues, missing libs, etc. with dmesg | tail -50