Running Roon in Docker on a QNAP machine via Container station. Application is up and running.
Roon 2.71 had worked flawlessly until yesterday evening, getting stuck during import of one album multiple times. Was initiating a reinstall, as I suspected a problem with the database SSD and anyways wanted to update QTS firmware to 5.2.10.
After everything was re-installed, up and running, logging in from any remote fails continuously. After showing this for some time
It jumps back to the option to log in. Same after restoring a backup, which works till 100% and seemingly creates a useful database in roon´s container (like 5.8GB and 12,000 files), but then jumps back to the log in screen.
Anyone any idea what could be done here?
Did you check for free space on all the server’s volumes and also RAM?
Yes, 1TB+ on both the container station volume and the database volume available, as well as 5GB+ of RAM unused. Had cleared all folders prior to reinstalling, and roon application itself is running and showing as “Ready” in Roon Remote.
It seems to be rather a login/account issue, or maybe something network-related.
And it also does not work if you restore the backup from the login screen without a prior attempt to login?
No, it does not, jumping back to login screen.
In the past I had an issue with roon not recognizing the new server install as a different one from a preexisting one, so will alter all IP addresses, server name, reboot and give it a try.
Edit: the latter at least got me one step further, by asking for a deauthorization. Never made it to this point so far.
Finally managed to unauthorize the previous install, and roon server would start up again. Very very slow, I must say, not loading album names/covers, freezing from the moment on remote can access the server, and even after new albums are identified and imported, everything is extremely sluggish with frequent crashes.
After rebooting, it stabilized a bit. Things had gone south the moment I was trying to import a specific album. Trying the same now, brings roon to standstill and crash again, but in general performance degraded in general.
Kind of a mystery to me. Maybe it has to do with roon not being able to do metadata maintenance? There was such notification.
After rebooting numerous times, witnessing crashs and sluggishness, the solution appeared by itself: When starting up roon the 10th time or so, a screen appeared ´after restoring a backback, your database needs improvement, this can take some time´.
And it worked, all fine again! Something seemingly preventing roon from applying database maintenance for several times, after I had restored a backup from a previous roon version and added albums.
