Since one of the last major Roon updates (I don’t know which one) I have a problem with Roonbride two of my DietPi based Raspberry installations: After a couple of hours it stops working, and only a reboot helps turning on the Rasperberries’ RoonBridge capabilities. I had the same problem with the rom provided by iqaudio.
I installed the RoonBridge with the “dietpi-software” app. Two only other programs I have installed are Shairport and RPimonitor.
Otherwise the installation works almost flawlessly. It’s just annoying, that when I come home from work and want to hear music, first thing I have to do is log into the two Raspberries and reboot.
First of all, thank you for your help and the great software you created.
One of my Raspberries is connected by ethernet, the other one by WiFi.
The output of the one connected over ethernet is:
root@Wohnzimmer:~# systemctl status roonbridge -l
● roonbridge.service - Roon Bridge
Loaded: loaded (/etc/systemd/system/roonbridge.service; disabled)
Active: active (running) since Mon 2017-06-19 18:09:40 UTC; 2 days ago
Main PID: 1115 (start.sh)
CGroup: /system.slice/roonbridge.service
├─1115 /bin/sh /etc/roonbridge/start.sh
├─1121 RoonBridge --debug --gc=sgen --server RoonBridge.exe
├─1300 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe
├─1335 /etc/roonbridge/Bridge/processreaper 1300
└─1826 RAATServer --debug --gc=sgen --server RAATServer.exe
Jun 19 18:09:40 Wohnzimmer systemd[1]: Started Roon Bridge.
Jun 19 18:09:42 Wohnzimmer start.sh[1115]: Initializing
Jun 19 18:09:43 Wohnzimmer start.sh[1115]: 00:00:00.021 Info: Starting /etc/roonbridge/Bridge/RoonBridgeHelper
Jun 19 18:09:43 Wohnzimmer start.sh[1115]: 00:00:00.047 Info: ConnectOrStartAndWaitForExit RAATServer
Jun 19 18:09:43 Wohnzimmer start.sh[1115]: Not Running (.o)
Jun 19 18:09:44 Wohnzimmer start.sh[1115]: Running
root@Wohnzimmer:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr b8:27:eb:10:1a:25
inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fe10:1a25/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8399458 errors:0 dropped:0 overruns:0 frame:0
TX packets:192020 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:441564650 (421.1 MiB) TX bytes:23503955 (22.4 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:4102 errors:0 dropped:0 overruns:0 frame:0
TX packets:4102 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1065631 (1.0 MiB) TX bytes:1065631 (1.0 MiB)
root@Wohnzimmer:~# ping google.com -c 1
PING google.com (172.217.22.14) 56(84) bytes of data.
64 bytes from fra16s14-in-f14.1e100.net (172.217.22.14): icmp_seq=1 ttl=56 time=23.9 ms
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 23.938/23.938/23.938/0.000 ms
The one of the Wifi connected is:
root@Schlafzimmer:~# systemctl status roonbridge -l
● roonbridge.service - Roon Bridge
Loaded: loaded (/etc/systemd/system/roonbridge.service; disabled)
Active: active (running) since Mon 2017-06-19 18:09:43 UTC; 2 days ago
Main PID: 1211 (start.sh)
CGroup: /system.slice/roonbridge.service
├─1211 /bin/sh /etc/roonbridge/start.sh
├─1215 RoonBridge --debug --gc=sgen --server RoonBridge.exe
├─1462 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe
├─1509 /etc/roonbridge/Bridge/processreaper 1462
└─2050 RAATServer --debug --gc=sgen --server RAATServer.exe
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
root@Schlafzimmer:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr b8:27:eb:e4:f9:a4
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:4197 errors:0 dropped:0 overruns:0 frame:0
TX packets:4197 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1125210 (1.0 MiB) TX bytes:1125210 (1.0 MiB)
wlan0 Link encap:Ethernet HWaddr b8:27:eb:b1:ac:f1
inet addr:10.0.0.18 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:feb1:acf1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:821145 errors:0 dropped:0 overruns:0 frame:0
TX packets:509592 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:721533035 (688.1 MiB) TX bytes:51441659 (49.0 MiB)
root@Schlafzimmer:~# ping google.com -c 1
PING google.com (216.58.208.46) 56(84) bytes of data.
64 bytes from fra15s12-in-f46.1e100.net (216.58.208.46): icmp_seq=1 ttl=56 time=23.2 ms
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 23.208/23.208/23.208/0.000 ms
From what I see in my network monitoring software, they were permanently connected to my home network. On the other hand: my network is due to integration of PowerLan adapters not very stable.
I don’t understand the output of “systemctl status roonbridge -l”. Is RoonBridge running?
Not sure what to make of that either, it says its running. Everything else looks fine.
Did you check the service status when both systems were unavailable on main Roon app?.
my network is due to integration of PowerLan adapters not very stable.
I still feel this is a networking issue, lets check a few things:
Is the WiFi RPi connected directly to the router’s WiFi? If so (and you have not done this already/recently), hard power cycle your router.
Which system are you using for the main Roon control app, and how is that connected to network (WiFi)?
It shouldn’t be a factor, but it may be worth changing the hostnames on both DietPi systems to something unique (dietpi-config > Security options > hostname).