Roon Core Machine
MacBook Pro
Linux Mint 21.1
3.5 GHz dual-core i7
16GB Memory
Core 2.0 (1244)
Networking Gear & Setup Details
Core and clients connective via ethernet
Connected Audio Devices
Many different endpoints connected via ethernet
Number of Tracks in Library
~60k
Description of Issue
Re-opening this issue b/c it was never resolved and it’s happening again between two cores:
And now I’m seeing it again between my new core (Linux Mint) trying to find my old core (Synology NAS) even after I’ve completely shutdown the Synology core.
Due to many, many Roon issues around the instability of the DB when backing up and restoring to new Cores, I have to maintain two Roon cores on my network at the same time:
-
Synology DS218+ (named
Nostromo) - My original Roon system where I first installed Roon, imported my music, created all of my playlists and tags, etc. This core is the “master” I use for a clean, working DB when the new core eventually corrupts the DB. -
MacBookPro, currently running Linux Mint. This is the device where I’m building and testing a new core so that I don’t have to run the core on the same NAS as my music files (the DS218+ is just barely enough power to run a full core with DSP). I’ve had lots of problems with Roon running on Mac hardware with multiple types of OS’s so I routinely have to rebuild this core and re-import the master DB that I keep current on the NAS.
During normal day-to-day usage I never run the two cores at the same time (even when I do only one is authorized at any given time based on Roon’s licensing model), but on occasion I do have both up as I’m testing migration, verifying playlists, etc, and each core does see the other one so it looks like it immediately makes a list of that core’s endpoints and/or clients (I’m not sure why a core would have a client, so I’m a bit confused…).
As an aside: Why does roonserver have any RAAT endpoints or clients anyway? Can’t a true core server just be a server and not have endpoints or act as a client? This would be like an NGINX webserver acting as an HTTP client to other webservers…but I digress…
After completely stopping the roonserver core on the NAS, my new MBP core still tries to connect to the clients on the NAS core over and over and over, apparently forever. It saw it once, it will always try to keep talking to it for some reason. This doesn’t make sense to me, even more so because the NAS core never had any endpoints enabled so I don’t know what the MBP core is trying to get from the NAS core.
Here’s an example of what I’m seeing in the logs. Despite the “giving up” message, it never gives up, and the sequence of 5 attempts repeats every minute.
04/13 10:36:40 Trace: [raatserver] [RaatServer Nostromo @ 192.168.1.20:9200] client connection failed. Retrying in 1687ms
04/13 10:36:41 Trace: [raatserver] [RaatServer Nostromo @ 192.168.1.20:9200] connecting (attempt 5)
04/13 10:36:41 Trace: [raatserver] [RaatServer Nostromo @ 192.168.1.20:9200] client connection failed. Giving up
There’s nothing re: Roon running on the NAS:
rcrawley@Nostromo:~$ ps -ef | grep -i roon
rcrawley 24674 24658 0 10:26 pts/12 00:00:00 grep --color=auto -i roon
Why is my core wasting cycles trying to talk to another core client, and can I do anything about it?
Or is this an artifact of restoring the master DB from Nostromo onto the MBP?