OK! I’ve found out the culprit why my Roon keeps crashing. It is because of TIDAL. When I disable it, it works. When enables, it always rescans the same TIDAL tracks and then a couple minutes later, Roon summarily crashes saying it is unable to restore a backup.
Thanks for reaching out with your report. I’ve enabled diagnostics mode for your account and I do see some interesting errors, along with a corruption notice.
Can you please confirm, if you try to temporarily set up a fresh Roon Server install and sign into TIDAL without restoring a backup, are you able to reproduce the issue, solely with your TIDAL account?
I thought that the DB was corrupt. I was still using Legacy 1.8 but then I heard that the changes were implemented in case there was an Internet failure.
So what I did was download the latest Roon 2 server. Naturally, I backed up the DB first in case I wanted to revert to 1.8.
BTW. I have both 1.8 and 2 servers installed on a Synology NAS.
I removed ALL media from the folders. I back them up in a different place anyway.
I switched off 1.8 and turned on 2 core.
Worked perfectly but I knew it will take a long time to update the DB. I have about 60000 tracks.
But it kicked in and Roon 2 was up and running.
It kept on rescanning all the tracks which I did repeatedly for ages until the number count went down but it got stuck at 4000 odd tracks or so and then it summarily crashes again and again.
I tried to find any log files but couldn’t of the crash.
But then I went into settings and disabled Tidal just in case that was the problem.
Lo and behold. It was.
I slowly moved the media back and Roon flawlessly put everything back. No Tidal though as it was disabled. I tend to use my material anyway and am thinking of unsubscribing from Tidal anyway.
I updated the remotes. PC and iPads.
Even Roon ARC amazingly worked straight out of the box. That was quite something! I can now access my tracks from work. Nice.
But as for the Tidal, I’m not sure why. Perhaps there is a way to not load items into Tidal into Library as a debugger feature? I don’t know.
But yes. Potentially there are people out there who might be experiencing crashes because of Tidal.
Just to re-iterate, this is nothing to do with Roon 1.8 vs Roon 2. Very happy with Roon 2 so far. It is possible perhaps that Tidal is confusing Roon.
You see, you can add albums into Roon from Tidal, however, Tidal has a nasty habit of making songs unavailable from time to time. Sometimes, it is because the source has changed. For example, the Tidal album has been replaced with a different version. Or that the owner of the material has requested Tidal to remove them. For example, I note that some King Crimson material has been removed from Tidal.
Thanks for the information. I am looking over your Synology diagnostics and I notice that you are running out of memory when enabling the TIDAL account:
[18802] 06/30 22:54:30 Warn: [tidal/http] GET https://api.tidal.com/v1/playlists/4....35f/tracks?countryCode=AU&offset=0&limit=50 => UnexpectedError System.Net.WebException: Too many open files in system
[18803] ---> System.Net.Http.HttpRequestException: Too many open files in system
[18804] ---> System.Net.Sockets.SocketException (23): Too many open files in system
[18805] at System.Net.Sockets.Socket..ctor(AddressFamily addressFamily, SocketType socketType, ProtocolType protocolType)
[18806] at System.Net.HttpWebRequest.<>c__DisplayClass216_0.<<CreateHttpClient>b__1>d.MoveNext()
[18807] --- End of stack trace from previous location ---
[18808] at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
[18809] --- End of inner exception stack trace ---
[18810] at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
[18811] at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
[18812] at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
I suspect this may have something to do with your open file limit on your Synology. While this is outside the scope of Roon support, the following articles may help with raising the limit: