Tidal's Discovery and Mix not updating in Roon (ref#EJC2R0)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Dear Sir,

Tidal’s “My Daily Discovery” and “My Mix” do not update automatically.

I tried logging out of Tidal in Roon and then restarting the Roon core. After doing this, I was able to update “My Daily Discovery” immediately. However, it still does not update “My Daily Discovery” and “My Mix” the following day.

Please advise how to fix this issue.

Thank you.

Best regards, Danny

Tell us about your home network

· Linksys router

2

Dear Sir,

I have tried to delete the Tidal cache; After doing this, I was able to update “My Daily Discovery” immediately. However, it still does not update “My Daily Discovery” and “My Mix” the following day.

Brgds,

Danny

3

Hey @Young_Danny,

Thanks for writing in and for sharing your report! There’s a chance you may be running into a known server outage we’re currently tracking:

Things may already be back up and running at this point. Could you please use the directions found here and send over a set of logs to our File Uploader? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!

4

Hi Benjamin,

My Roon Core was purchased from an audio company, so I do not have access to the log files on the Linux server. Could you please advise me on how to resolve this issue?

Thank you,
Danny

5

Young_Danny

3h

Hi Benjamin,

I have updated some logs. Please advise how to fix it.

Thanks

Danny

6

Dear Benjamin,

I have tried restarting the Roon Core and clearing the DNS cache over the past few days, but it still cannot automatically sync the next time. Could you please advise on how to resolve this issue as soon as possible?

Thank you, Danny

7

Hi @Young_Danny,

Unfortunately, these outages have been a bit spotty all week. If you reboot your devices again, how do things perform today?

Thank you!

8

Still have same problem. can not fix！

9

Hey @Young_Danny,

Thanks for all your patience so far - if it’s strictly new releases you’re having issues with, our team is currently investigating some known outages there.

Otherwise, please reboot your server and remotes, and let me know if you’re still having issues. Thank you!

10

Still have same problem. can not fix！

11

Hello @Young_Danny ,

Are you still seeing this issue on our latest Roon release that went out today? We enabled diagnostics for your Roon Server, but this is strange, it looks like the diagnostics pacakge that came in is mostly empty. I wonder, is there any issue with avaliable storage space on the server and perhaps Roon is running out of avaliable space to use?

12

Hello @noris

I have upgraded to the latest Roon release but still have same problem. can not fix！

Please advise how to fix it as soon as possible.

Thanks

1 Like
13

Hello @Young_Danny,

I understand it is frustrating when an update does not immediately resolve the problem, and we want to get this fixed for you as quickly as possible. However, to do that, we need your help to fix a core issue on your machine first.

As Noris mentioned previously, the diagnostic logs your server is sending us are completely empty. Without these logs, our technical team cannot see what is causing your system to fail. Roon is currently unable to write any data to its own log files.

Looking at your system information (Linux kernel 6.18.13-rt-x64v3-xanmod1 on an Onda H410SD4-ITX), this strongly points to a permissions issue within your Linux environment. If Roon Server was installed without the correct user privileges, or if the directory where Roon is installed does not have the proper read/write permissions, the system will physically block Roon from writing logs or operating correctly.

To help us get to the bottom of this, could you please provide some details on your setup:

  • How exactly did you install Roon Server on this Linux machine?
  • Which user account is running the Roon Server process?
  • Can you verify that the user running Roon has full read/write permissions to the Roon Server directories?

Let’s get those permissions sorted out first so your server can successfully generate logs. Once we have the logs, we can immediately identify and fix the main issue!

14

@vadim

  1. Yes, my Roon Server is installed on this Linux. I have reinstalled the Roon core on this Linux machine today but it still can not fix this issue.
  2. [Modertor edit: personal information removed.]
  3. Yes, it has full read/write permissions to the Roon Server directories.

I have been using this Roon Core machine for two years, and this issue only started happening a month ago. Please help me check this again and let me know the solution.

Thanks!

15

Hello @Young_Danny,

Thank you for following up and for reinstalling the software. However, we need to be completely transparent with you about what your system is reporting.

Even after the reinstall, we are still not receiving any logs from your Roon Server. The diagnostic snippet we did receive only contains logs from the RAATServer (the audio routing component). The main Roon Server logs—which contain the core database and operational data we absolutely need to fix your issue—are still missing or being blocked from writing to your disk.

Looking closely at the network section of the RAATServer logs that did come through, we can clearly see why this is happening. Your machine is running multiple virtual network interfaces: docker0, lxcbr0, and lxdbr0. This confirms that your Linux environment is utilizing Docker containers and LXC/LXD virtualization.

Please note that Roon does not officially support running Roon Server inside Docker containers or virtual machines. While we understand this setup has worked perfectly for you for the last two years, virtualized environments handle file system permissions, volume mapping, and networking differently than bare-metal operating systems. Because it is an unsupported workaround, any underlying OS update, container update, or Roon update can suddenly break the container’s file mapping—which is exactly what appears to have happened a month ago, completely stripping Roon of its ability to write its own log files.

Without those Roon Server logs, our technical team is entirely blind to what is causing your system to fail.

To move forward and get this resolved, you will need to install Roon Server natively (bare-metal) on an officially supported Linux OS, completely outside of a containerized environment.

To check if the logs were generated properly, please use the directions found here and upload the logs to the uploader, or let us know, and we will pull the diagnostic data again.

Once your system is generating actual Roon Server logs, please let us know, and we will dive in to get your system back up and running!