Ropieee Stopped Appearing as Audio Endpoint, Showing Up in About, In Logs With Old IP

Roon Core Machine

MacBookPro
Ubuntu 22.04
3.5 GHz Dual-Core i7
16 GB RAM

Core: Roon 2.0 (1133)

Networking Gear & Setup Details

Ethernet everywhere, between MBP and all audio end-points

Connected Audio Devices

RPi 4 running Ropieee RoPieee 2022.08.1 (0523), USB out to Schiit DAC, connected via ethernet

Number of Tracks in Library

~60k

Description of Issue

I’m rebuilding a new Ropieee USB endpoint using RoPieee 2022.08.1 (0523). I currently have two other Ropieee devices and have been using them for a few years with no issue, but yesterday I had one (that I use daily) disappear from Roon and stop working, so I’m rebuilding it. But when setting up a new Ropieee instance to get it back online with Roon, I’m having an issue where it’s not showing up as an Audio device in Roon → Settings after changing the IP address of the Ropieee to a fixed IP address. It is showing up as an endpoint running RoonBridge in About as the new IP address, and strangely, it’s showing up twice in logs, once with the new IP address and once with the old IP address, even after a complete reboot of the MBP.

  • Flash SD card with latest Ropieee
  • Install card, boot, let Ropieee install and grab a DHCP IP (192.168.1.208)
  • Ropieee comes up fine with Audio USB enabled
  • Set fixed IP address via DHCP lease on the router (192.168.1.123)
  • Restart Ropieee, verify that it’s running on the new IP address (192.168.1.123)
  • In Roon, Settings → About, Ropieee is showing up as a new Roon Bridge device with the new, correct IP address:

Screen Shot 2022-10-20 at 1.14.40 PM

  • Device never shows up in Settings → Audio:

  • Logs are showing Roon finding two devices, one with the old .208 IP and one with the new .123 IP address, but there is no device on my network anymore using .208:
10/20 13:09:48 Trace: [raat] RAATServer discovered: RaatServer ropieee @ 192.168.1.123:9200
10/20 13:09:48 Info: [raatserver] GOT SERVER ad261009-136b-0718-677b-2931d2f43f31::df55b90f-c442-40a6-8b15-0c7f53854f04 @ 192.168.1.123:9200 ropieee PROTOVER=1 RAATVER=1.1.38 
10/20 13:09:48 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.123:9200] connecting (attempt 1)
10/20 13:09:48 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.123:9200] connected
10/20 13:10:02 Trace: [raat] RAATServer discovered: RaatServer ropieee @ 192.168.1.208:9200
10/20 13:10:02 Info: [raatserver] GOT SERVER ea15a54b-57f9-0de5-f323-bbd71648efd6::d32d197d-8d18-4b59-8809-14778f7361fd @ 192.168.1.208:9200 ropieee PROTOVER=1 RAATVER=1.1.38 
10/20 13:10:02 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 1)
10/20 13:10:05 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 500ms
10/20 13:10:06 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 2)
10/20 13:10:08 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 750ms
10/20 13:10:09 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 3)
10/20 13:10:11 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 1125ms
10/20 13:10:12 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 4)
10/20 13:10:14 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 1687ms
10/20 13:10:16 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 5)
10/20 13:10:18 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Giving up
10/20 13:10:50 Trace: [raat] RAATServer discovered: RaatServer ropieee @ 192.168.1.208:9200
10/20 13:10:50 Info: [raatserver] GOT SERVER ea15a54b-57f9-0de5-f323-bbd71648efd6::d32d197d-8d18-4b59-8809-14778f7361fd @ 192.168.1.208:9200 ropieee PROTOVER=1 RAATVER=1.1.38 
10/20 13:10:50 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 1)
10/20 13:10:52 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 500ms

You can see that it finds .123 and connects as expected, then immediately gets into a loop of detecting .208 (no idea why), failing to connect, retrying, then finding again, starting the loop over, etc, until I finally get a “giving up” message. But then less than 1 second later, it re-discovers it and starts over:

10/20 13:32:32 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 5)
10/20 13:32:34 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Giving up
10/20 13:32:48 Trace: [raat] RAATServer discovered: RaatServer ropieee @ 192.168.1.208:9200
10/20 13:32:48 Info: [raatserver] GOT SERVER ea15a54b-57f9-0de5-f323-bbd71648efd6::d32d197d-8d18-4b59-8809-14778f7361fd @ 192.168.1.208:9200 ropieee PROTOVER=1 RAATVER=1.1.38 
10/20 13:32:48 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 1)
10/20 13:32:51 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 500ms
10/20 13:32:52 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 2)
  • Rebooted MBP completely, after Roon comes back up it’s still reporting that it’s discovering the original device on .208.

No device running on .208 at all on my network:

$ ping 192.168.1.208
PING 192.168.1.208 (192.168.1.208): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2

I’ve been able to repro this on two different RPi’s with the exact same behavior with Roon discovering the correct Ropieee but then immediately discovering something on .208, failing, back in the same spot. This is just craziness.

Is there any way to completely flush the endpoints so that it re-detects them again?

Update: RoonCore is still trying to connect to the Ropieee Pi, at both IP addresses, after a complete MBP server reboot even though the Pi is physically turned off (turned it off before rebooting the server, still off):

10/20 13:45:16 Trace: [raat] RAATServer discovered: RaatServer schiitstack @ 192.168.1.26:9200
10/20 13:45:16 Info: [raatserver] GOT SERVER 03ff544a-24ee-6775-5847-ad4922ab0c2b::a38e7141-e9a8-462d-b51b-f975fd2e3a4a @ 192.168.1.26:9200 schiitstack PROTOVER=1 RAATVER=1.1.38 
10/20 13:45:16 Trace: [raatserver] [RaatServer schiitstack @ 192.168.1.26:9200] connecting (attempt 1)
10/20 13:45:16 Trace: [raat] RAATServer discovered: RaatServer ropieee @ 192.168.1.208:9200
10/20 13:45:16 Info: [raatserver] GOT SERVER ea15a54b-57f9-0de5-f323-bbd71648efd6::d32d197d-8d18-4b59-8809-14778f7361fd @ 192.168.1.208:9200 ropieee PROTOVER=1 RAATVER=1.1.38 
10/20 13:45:16 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 1)
10/20 13:45:19 Warn: [rnet/RnetJsonClient] failed to connect No route to host
10/20 13:45:19 Warn: [rnet/RnetJsonClient] failed to connect No route to host
10/20 13:45:19 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 500ms
10/20 13:45:19 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.26:9200] client connection failed. Retrying in 500ms
10/20 13:45:19 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 2)
10/20 13:45:19 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.26:9200] connecting (attempt 2)
10/20 13:45:22 Warn: [rnet/RnetJsonClient] failed to connect No route to host
10/20 13:45:22 Warn: [rnet/RnetJsonClient] failed to connect No route to host
10/20 13:45:22 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.26:9200] client connection failed. Retrying in 750ms
10/20 13:45:22 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 750ms
10/20 13:45:23 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.26:9200] connecting (attempt 3)
10/20 13:45:23 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 3)
10/20 13:45:25 Info: [stats] 23358mb Virtual, 1966mb Physical, 645mb Managed, 399 Handles, 81 Threads
10/20 13:45:25 Warn: [rnet/RnetJsonClient] failed to connect No route to host
10/20 13:45:25 Warn: [rnet/RnetJsonClient] failed to connect No route to host
10/20 13:45:25 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.26:9200] client connection failed. Retrying in 1125ms
10/20 13:45:25 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] client connection failed. Retrying in 1125ms
10/20 13:45:26 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.26:9200] connecting (attempt 4)
10/20 13:45:26 Trace: [raatserver] [RaatServer ropieee @ 192.168.1.208:9200] connecting (attempt 4)

Sounds similar to this issue (which was closed w/o resolution): Endpoints still sending signal after stopping/pausing music

More debugging. Seeing a lot of network reachability changes in the logs, which doesn’t make sense b/c nothing else on the box is changing at all. I’m not seeing any issues or messages in dmesg or in syslog, multiple long-lived ssh connections are staying open to the box w/o issue, I’m physically watching the network adapter and nothing is happening with it when these reachability issues are reported (USB adapter has Tx lights and they continue to function like normal during one of these events), and ifconfig is report 0 Rx or Tx errors. DNS is confirmed working and using 1.1.1.1, 8.8.8.8.

Roon also continues to stream without issue to existing endpoints (Cambridge, Ropieee) during these network reachability events.

Is Roon just confused and having networking issues?

$ tail -f RoonServer_log.txt | grep reachability

10/20 14:38:36 Trace: [broker/accounts] network reachability changed. refreshing
10/20 14:38:36 Debug: [tidal] network reachability changed. refreshing token
10/20 14:38:36 Trace: [mobile] [remoteconnectivity] Port Verification started due to: network reachability changed, port verification not in progress, starting a new attempt
10/20 14:38:36 Trace: [roonapi] network reachability changed. Kicking off discovery cycle
10/20 14:38:38 Trace: [remoting/brokerserver] network reachability changed. Kicking off discovery cycle
10/20 14:38:48 Trace: [broker/accounts] network reachability changed. refreshing
10/20 14:38:48 Debug: [tidal] network reachability changed. refreshing token
10/20 14:38:48 Trace: [mobile] [remoteconnectivity] Port Verification started due to: network reachability changed, port verification not in progress, starting a new attempt
10/20 14:38:48 Trace: [roonapi] network reachability changed. Kicking off discovery cycle
10/20 14:38:50 Trace: [remoting/brokerserver] network reachability changed. Kicking off discovery cycle
10/20 14:38:55 Trace: [broker/accounts] network reachability changed. refreshing
10/20 14:38:55 Debug: [tidal] network reachability changed. refreshing token
10/20 14:38:55 Trace: [mobile] [remoteconnectivity] Port Verification started due to: network reachability changed, port verification not in progress, starting a new attempt
10/20 14:38:55 Trace: [roonapi] network reachability changed. Kicking off discovery cycle