Wrong error message ”There was an issue loading your database”

Dirk_De_Taey · June 19, 2023, 3:40pm

Details on your Core machine (OS, Hardware specs, Roon build)

Audiolinux Server, running on Audiolinux, Intel i9 13900 processor, 32GB RAM, 1 HD Samsung SSD 512GB for OS+apps Roon + 2 HD Samsung 4TB SSD for local music
Roon version 2.0.1277
HQPlayer: HQPlayer Embedded 5.0.1.2

Details on your Remote(s) (OS, Hardware specs, Roon build)

iPad Air Pro – 128GB - running iPadOS 16.2 - Roon version 2.0.1277
Samsung S10e – running Android version 12 kernel 4.14.113-25257816 – Roon version 2.0.17 Wifi 6
PC running Windows 11 Home - 11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz 2.80 GHz Ram 16GB, Roon version 2.0.1277

Networking details (especially what hardware you’re using, how everything is connected, and anything notable about how it’s all configured)

Ethernet & Wifi Mesh network built on 3 * Asus Zenwifi XT8
Connected to Service Provider modem
Speedtest connection speed ethernet 93Mbps download – 18Mbps upload
Roon Core connected via ethernet, Remote PC connected via ethernet
Mobile Remotes connected via Wifi6

Audio devices in use

T+A 8 DSD connected to connected via Holo Audio Red USB connected to ethernet
Endpoints : 1 * Cambridge Audio CXN v2 , connected via ethernet

Library details

Local library on separate internal 2*4TB SSD harddisks in Roon Server
Qobuz Hi-fi Sublime streaming service
62303 tracks (4189 albums – 2422 local, 1767 Qobuz)

Backup details

Location 1 : SSD disk in Core Machine - 200GB capacity
Location 2 : Synology NAS 10,8 TB capacity
Location 3 : USB disk connected to Synology NAS - 7,2 TB capacity

ISSUE

Everything was working fine this morning. Coming back this afternoon, starting using Roon again, I first got a Qobuz login failure.
Logging out od Qobuz and logging in anew, got rid of that issue. However, shortly after that I got the ”There was an issue loading your database” error message.
So I first rebooted the server, and restarted the audioservices Roon + HQPlayer.
After a minute or so, I got the same error message again.

Refusing to accept something was/is wrong with my database, I stopped and restarted Roon & HQPplayer.
Working fine now for over half an hour without issues so far.

Due to the Qobuz login failure message, I firmly believe that something happened whilst I was away from home - internet failure, Roon server failure, Qobuz outage, … that had an impact on Roon server application.

Without changing anything, just stopping and restarting Roon server, the issue seems to be solved (I cross my fingers).
but I am extremely glad that i did NOT (tried to) restore a Roon backup.

It would be great if you could provide me with instructions on where to find Roon log files on my audiolinux server, for you guys taking a look at it.
If this error message is not to be expected/correct, it would be very worthwhile to findout and avoid other users start to execute backup restore without being necessarry.

Dirk

Rugby · June 19, 2023, 4:00pm

Hi Dirk,

This might help

Dirk_De_Taey · June 19, 2023, 6:33pm

@support

I just hace uploaded all logfiles in the Roonserver- log folder using the Roon log uploader.

Dirk

Dirk_De_Taey · June 21, 2023, 12:20pm

In the description how to provide logs to Roonlabs, using Roon log uploader, it is stated that the user will receive notice of reception.

I have received no such confirmation message since uploading.

Dirk

Dirk_De_Taey · July 4, 2023, 4:41pm

When powering up my Roon server this morning I needed about 5 reboots to get Roon working:

Accessing Roon from my Windows client presented the famous ‘“There was an issue loading your database” error, either immediately of within a minute of use.

For the moment it seems to run back ok, without me doing anything else than rebooting.

I have downloaded the logfiles of today, and in the latest ‘crash’ logfile (Roonserver_log_01), I see

07/04 11:32:48 Error: [broker/database] corruption detected: Corruption: corrupted compressed block contents

07/04 11:32:48 Warn: [broker] detected corrupt database, notifying client

07/04 11:32:48 Warn: [broker] detected corrupt database, halting broker threads

07/04 11:32:48 Critical: Library.EndMutation: LevelDb.Exception: Corruption: corrupted compressed block contents

at LevelDb.Database._CheckError(IntPtr err)

at LevelDb.Database.Write(WriteBatch batch)

at LevelDb.Transaction.Commit(Boolean trace)

at Sooloos.Broker.Music.MusicDatabase.Flush()

at Sooloos.Broker.Music.Library.EndMutation()

07/04 11:32:48 Trace: [dbperf] flush 129544 bytes, 0 ops in 4 ms (cumulative 147163670 bytes, 64647 ops in 17253 ms)

07/04 11:32:48 Trace: [zone HQPlayer] Suspend

07/04 11:32:48 Info: [zone HQPlayer] Canceling Pending Sleep

07/04 11:32:48 Trace: [zone KEF LSX II] Suspend

07/04 11:32:48 Info: [zone KEF LSX II] Canceling Pending Sleep

07/04 11:32:48 Trace: [zone CXNv2 (be)] Suspend

07/04 11:32:48 Info: [zone CXNv2 (be)] Canceling Pending Sleep

07/04 11:32:48 Trace: [leveldb] closing /var/roon/RoonServer/Database/Core/7b64ae83bef54392b703b65625ccfe54/transport/zone_1601d935088f5a8521851f0b72f30228de66.db temporarily

07/04 11:32:48 Trace: [leveldb] closing /var/roon/RoonServer/Database/Core/7b64ae83bef54392b703b65625ccfe54/transport/zone_16014b93547471cc484093b79451f9179bb4.db temporarily

07/04 11:32:48 Trace: [leveldb] closing /var/roon/RoonServer/Database/Core/7b64ae83bef54392b703b65625ccfe54/transport/zone_160121b5788e01f1925eb86f7ecdb86b783d.db temporarily

07/04 11:32:53 Info: [stats] 36555mb Virtual, 4400mb Physical, 1302mb Managed, 324 Handles, 116 Threads

07/04 11:33:08 Info: [stats] 36611mb Virtual, 4400mb Physical, 1305mb Managed, 319 Handles, 121 Threads

07/04 11:33:09 Info: [remoting/serverconnectionv2] Client disconnected: 192.168.0.156:58922

I have used the Roon Log Uploader to upload the complete Roon log files.
The ones of today are:
RoonServer_log.05.txt - 04 - 03 -02 - 01 and RoonServer_log.txt, with 05 being the earliest of today
and RoonServer_log.txt the latest (of the session running fine during the day)

I have executed diskchecks, reporting no errors, for my system disks and both Music (data) disks.
I am running a ‘test’ conversion by dBPoweramp of all my AIFF & Flac files (dsf files are not taken into account, but these have not changed in more than over a year)

I also have tested my memory modules with Passmark MemTest86, 0 errors reported.
reference: How to Test RAM: Make Sure Bad Memory Isn’t Crashing Your PC | Tom’s Hardware

So I am running out of ideas what to do next. I am reluctant to restore a backup , as I keep up to about max. 20 daily backups. Any ‘real’ error in the database will be be present in my backups as well.

Could someone please take a look at today’s logfile, to see if you can trace any possible reason for the challenging startup this morning. Thanks in advance.

Dirk

benjamin · July 6, 2023, 11:31pm

Hey @Dirk_De_Taey,

My apologies for the delay in getting to your thread! I was able to pull a fresh diagnostic from your core, and confirm you’re experiencing database corruption. To put it simply, database corruption means that the records Roon is reading from your database are different from what was originally written.

This isn’t common and can happen for a number of reasons, like failing harddrives or an unstable power source (frequent outages, hard power cuts, etc).

In some cases, corrupt database records can go completely undetected. And it’s only when we release an update that requires Roon to re-scan every record that the corruption shows itself.

These updates don’t happen frequently, which increases the risk of data loss. For example, if you only have a few weeks of backups, the chances that you have a usable backup drop significantly if the “latent” corruption isn’t detected for many months.

Roon now detects database corruption “on the fly”. So if corruption is detected during a backup or during normal use of Roon, you’ll be immediately prompted to restore from a backup.

If you restore from a backup and still see “There was an issue loading your database”, try restoring from your oldest backup.

If you’re not having any luck with your oldest backup, then the only alternative is to start with a fresh database.I sincerely hope it doesn’t come to this, as we understand the time it takes to curate your collection.

I’ll be on standby for your reply.

Dirk_De_Taey · July 7, 2023, 2:53pm

Hi Benjamin

Thanks for your feeedback.

It would be great if, for my learning, if you could provide me with any insight/one example of an actual error reported in a logfile that I have uploaded.
I have been going through these logfiles, but apparently, I do not have any (enough) knowledge to be able to do any meaningfull deductions

Looking forward to your feedback

Dirk

benjamin · July 7, 2023, 10:23pm

Hey @Dirk_De_Taey,

Sure, you posted a snippet earlier in the thread that provides an example:

system · July 14, 2023, 7:24pm

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.