Core Machine is ROCK on an Intel NUC, Version 1.8 (build 903) stable
Networking Gear & Setup Details
Core and end points are mostly hardwired, no managed switches in the loop.
The only network oddity is I run a Pi Hole DNS ad blocker on the network. I have checked the logs here but can’t see any Roon/tidal traffic being blocked.
Connected Audio Devices
Multiple network connected devices, including:
Airplay Surround reciever
Google home devices
Number of Tracks in Library
around 33k tracks
Description of Issue
I have been using Tidal / Roon for a number of years with no major issues. For the last couple of weeks I have been having problems with my library.
I often look through Tidal and heart albums from Tidal, to listen to them at a later date through Roon, recently it looks like these items aren’t syncronising and adding into Roon. I have had to get home and then add the album through the Roon interface.
An example of my Tidal and Roon albums, sorted by date with no filtering:
Hi, @Matthew_Clegg, thank you for your report. Do you mind if we pull a diagnostics report from your Core? The last screenshot of yours indicates a networking issue. We need to take a look at Roon logs to get a better understanding of what’s happening on your Roon Core.
Of course Ivan, how do we proceed?
The last issue is very intermittent, and I suspect it is due to rate limiting on DNS requests on my network. I have rebooted the server and it seems to have cleared, though the library is still noy syncing.
Thanks, @Matthew_Clegg, I will send a request via our support system and I hope that your Core will be able to send the data to us. After this, we will analyse it and @david.p should come up with the next steps.
02/23 01:28:34 Trace: [tidal/storage] sync completed unsuccessfully in 20862ms: Result[Status=NetworkError]"
This means that your TIDAL account cannot finish the syncing procedure. After looking around this line in the same log, we noticed a lot of these errors which are intermittent:
02/23 01:28:38 Warn: [easyhttp]  Get https://metadata.roonlabs.net/1/albums/166:0:304838/tracks?c=tidal-gb web exception without response: Name or service not known (metadata.roonlabs.net:443) Name or service not known (metadata.roonlabs.net:443)
It points to a DNS-related issue. As the next step, we suggest temporarily turning off the Pi Hole DNS adblocker. Let’s see if that helps.