Having some issues with the setup (just got it all running). Got some dropouts and music playing out of sync. Started trying to investigate and found something odd in the Roon log.
The reason I am confused by this, is because I have no device on my network called āJohns-Mini-2018āā¦ The IP that this refer to (192.168.1.184) is one of my DSP amplifiers connected to Ethernetā¦
I have no clue why that amplifier would do anything on my network and I get a bit worried that thereās something fishy going onā¦ Any thoughts on this?
Do I have someone hi-jacking my network, or could it potentially be scrap traffic on the network that confuse Roon?.. It looks like Roon idenfities this IP as a RoonServer and tries to connect to it, which failsā¦
Iām not sure whatās going on but have you checked your router to confirm that there isnāt a device on your network called āJohns-Mini-2018ā? If you go through the log does it appear again, either earlier or later?
Will wait hopefully Roon Support can have some idea about what could potentially cause thisā¦ or whether I should be worriedā¦
It seems that the ROCK believes thereās a device it should connect to on the IP of this amplifierā¦ I would love to clear that somehow and see if the ROCK believes that device reappear, but I have no clue how to delete ROCKās memory of older devices.
Yep, definitely odd. I canāt think of any other reason for this, so you will probably need to wait for support to get to you. In the meanwhile, do you see anything odd in Settings ā Audio?
EDIT: If this is something to do with the amp I donāt think it will show up in Settings ā Audio unless you reenable it.
I donāt have an open WIFI or guest networkā¦ Just to make sure I disconnected the amplifier so I donāt have it wired to the router anymore.
I just reinstalled the ROCK completely. (reseted Roon Database & Settings, reinstalled itās OS and restarted it entirelyā¦)
After restarting itā¦ and checking the logā¦ I can see this quite early in the log:
05/31 22:56:08 Trace: [raat] [NAD CI580 (1) @ 192.168.1.12:43013] => Connected
05/31 22:56:08 Trace: [raat] [NAD CI580 (1) @ 192.168.1.12:43013] connected
05/31 22:56:08 Trace: [NAD CI580 (1) @ 192.168.1.12:43013] [raatclient] GOT [3] {āstatusā:āSuccessā}
05/31 22:56:09 Debug: [easyhttp] [18] GET to https://api.roonlabs.net/internetradio/2/api/location?format=msgpack& returned after 403 ms, status code: 200, request body size: 0 B
05/31 22:56:09 Trace: [radio/library] got location SE 05/31 22:56:09 Debug: [easyhttp] [22] POST to https://api.roonlabs.net/discovery/1/query returned after 379 ms, status code: 200, request body size: 74 B 05/31 22:56:09 Trace: [SOOD] Adding User IP 192.168.1.184 05/31 22:56:09 Trace: [SOOD] Adding User IP 192.168.1.181 05/31 22:56:09 Trace: [SOOD] Adding User IP 192.168.1.20 05/31 22:56:09 Trace: [raat] RAATServer discovered: RaatServer Johns-Mini-2018 @ 192.168.1.184:9200
05/31 22:56:09 Info: [raatserver] GOT SERVER d54cc52d-955d-5182-b55b-303d70361623::02d71373-e24b-4593-a7fe-8b9c88e720bb @ 192.168.1.184:9200 Johns-Mini-2018 PROTOVER=1 RAATVER=1.1.39
05/31 22:56:09 Trace: [raatserver] [RaatServer Johns-Mini-2018 @ 192.168.1.184:9200] connecting (attempt 1)
What the heck?.. I have no device on the network with that IP (192.168.1.184), and I have tried to ping it in terminal without successā¦ (The two other IPās are correct, my laptop and stationary pc)
Can Roon somehow get data from the cloud that is incorrect?.. It seems the row in the log before the IP gets added is some kind of POST query towards the Roon domain?..
The first part of the text string after āGOT SERVERā, i.e. the bit before the double colon, looks like the software serial number for Roon. If you take a look at Settings ā About you can see if it matches with your serial number. If not, then support will be able to identify who it does belong to.
But why would that IP go to his amp then? OP go into your router and see whatās actually connected. Did you assign a previously used static IP or something?
edit: I saw youāre using a UDMP. It sometimes identifies devices incorrectly. If youāre positive that IP maps to your amp, log in to your console and edit the device name.
Looks to me like itās the same router as in the thread I shared. I donāt own Ubiquiti products but what Iāve heard, they are very flexible and may demand solid networking knowledge to setup properly ā so this might be some sort of configuration error (Roon Core exposed to the internet accidentally for example).
PS: Also a reset of RAATServer to see if the āJohns-Mini-2018ā returns again or stays forgotten might be worth testing. Make a backup first, stop Roon on the NUC then rename the RAATServer folder in the database directory and start Roon again. If unsure, wait until/if instructed by official Roon support to do so.
UniFi user here: Your UniFi console should give you enough information to track down that mysterious device, on the Client Devices tab. Each row shows name, vendor, connection type, IP address, network, and more.
I did test this. I stopped Roon Server Software, I renamed the RAATServer folder (to āRaatServer(backup)ā) and restarted Roon Server Software.
I also tried setting the listening port to 0 (as was mentioned in another thread to stop Roon ARC potentiallyā¦) - didnāt seem to change anything.
After restart the log file was clean, but quickly the log again showed notice of this 192.168.1.184 IP RaatServer appearing. Note, I have no device on my network with this IP active.
First these rows
06/01 06:52:28 Trace: [SOOD] Adding User IP 192.168.1.184 (the rogue ip?..)
06/01 06:52:28 Trace: [SOOD] Adding User IP 192.168.1.181 (my roon server)
06/01 06:52:28 Trace: [SOOD] Adding User IP 192.168.1.20 (my laptop)
Then these
06/01 06:52:28 Trace: [raat] RAATServer discovered: RaatServer Johns-Mini-2018 @ 192.168.1.184:9200
06/01 06:52:28 Info: [raatserver] GOT SERVER d54cc52d-955d-5182-b55b-303d70361623::02d71373-e24b-4593-a7fe-8b9c88e720bb @ 192.168.1.184:9200 Johns-Mini-2018 PROTOVER=1 RAATVER=1.1.39
(note is that if this should be the same as my Roon Server Software ID, Itās notā¦ my id is differentā¦)
Then these
06/01 06:52:31 Warn: [rnet/RnetJsonClient] failed to connect No route to host
06/01 06:52:31 Trace: [raatserver] [RaatServer Johns-Mini-2018 @ 192.168.1.184:9200] client connection failed. Retrying in 500ms
06/01 06:52:32 Trace: [raatserver] [RaatServer Johns-Mini-2018 @ 192.168.1.184:9200] connecting (attempt 2)
06/01 06:52:33 Trace: [raatserver] [sood] Refreshing device list
Yeah, I know, but the only device Iāve had on my network with that IP (192.168.1.184) is a Blaze Power Connect Amplifier (does not run Roon), and I have since disconnected it / thereās no device on the network currently with the IP.
So your UDMās DHCP is not supplying that IP address, but could there be a (partially) accessible device that has that as its fixed IP, and is reachable by IP multicast, which is what Roon uses for device discovery? Note that remotes that can serve as endpoints also run RAAT servers, for example my phone and my laptop. There are ways to try get more network routing info, for instance traceroute on Linux.
