Hello,
I am receiving “There was an issue loading your database” notification upon every restart of Roon, including any Roon launch after a core reboot.
Roon Core Machine
MacBook Pro (14-inch, 2021 Model); Apple M1 Pro Chip–10 Core CPU; 32GB Memory; 2TB SSD. Core is running MacOS Monterey version 12.1 and Roon version 1.8 Build 884.
Networking Gear & Setup Details
Roon Core and all Roon Endpoints are linked via Cat 8 Ethernet cable to main switch–(TRENDnet unmanaged 24-Port Gigabit Switch with 2x10G SFP+ Slots [TEG-30262 Version 1.0R]). The main switch is connected to a Draytek Vigor 2927 Dual-Wan Router in fail over setup. The router is fed through two independent ISPs–one primary and one fail over. Realized internet speed to Roon Core is 900 Mbps Download; 20 Mbps Upload; 15ms Latency.
### Connected Audio Devices
All Roon Endpoints are hardwired, either through Ethernet from the switch or USB-C from the Core. All Endpoints are used exclusively through RAAT protocol.
Endpoints include:
Matrix Audio mini-i Pro 3 connected by USB-C to Core
Naim Mu-so 2nd generation–connected via Ethernet to switch
Naim Mu-so Qb 2nd generation–connected via Ethernet to switch
3-RopieeeXL Raspberry PI 4s connected to USB DAC(s), connected via Ethernet to switch
3 Instances of HQ Player running on three Mac computers, connected via Ethernet to switch, one of which is the Roon Core
### Number of Tracks in Library
Library includes 44,944 tracks with 6,097 albums. Linked streaming services include Tidal and Qobuz.
### Description of Issue Issue: There was an issue loading your database Notes: I am receiving “There was an issue loading your database” notification upon every restart of Roon, including any Roon launch after a core reboot. Frequency: Upon every restart of Roon, including all restarts following a Core reboot. Restore Functionality: I am able to restore from a backup, as long as I use a backup either from a prior build (882 or 880) or a backup at least three iterations old. Timestamp of Error: January 5, 2022 at 15:43 MST Logs: Roon logs from error generating at 15:43 MST were saved, zipped and are ready for upload.
I appreciate your help troubleshooting this issue.
Jeff
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
2
It looks like Roon has detected some form of corruption in your DB and this is why it is now giving you that message.
Are you able to successfully restore and run from an older backup?
Yes, I believe you are correct. I am hoping the Roon Team is able to help me locate the source of corruption, such that I may remediate it without having to fully restart my library build.
I am able to restore from and run many older backups, but once restored I cannot quit & relaunch Roon. To successfully restore, I’ve had to pull a backup at least 3 iterations old or use the last one from a prior build–e.g. a backup from build 880 or 882 when running builds 882 and 884, respectively.
The restore function is how I “restart” Roon. Oddly, I am able to successful restore from backups from all recent builds–880 to 884–all from varied days.
Do you have any knowledge on where I can look in the Roon Logs to identify the source of corruption?
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
4
I’m afraid I do not.
Just a fellow member here, I’m a little confused though as to once you have restored and got Roon running why it does not stay stable and keep running?
I guess there is something you are doing or is happening that I am misunderstanding here
The ability to restore what appears to be a non-stable backup has always struck me as odd.
I think the loops driving the corruption are below. Time to go digging into the library text files…
01/05 15:43:47 Critical: Library.EndMutation: System.Collections.Generic.KeyNotFoundException: work not found: 174:1:3f2d5ada-ccb0-40ea-94ac-b47421b50ed2
at Sooloos.Broker.Metadata.Context.GetWorkLite (System.Sooid workid) [0x00068] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.Context.GetWorkLite (System.Sooid workid) [0x00008] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.MetadataPerformanceLite._Load (Sooloos.Broker.Metadata.Context metacx, Roon.ServiceProxies.MetadataService2.Performance performance) [0x0000d] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.MetadataPerformanceLite..ctor (Sooloos.Broker.Metadata.Context metacx, Roon.ServiceProxies.MetadataService2.Performance performance) [0x00028] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.Context.GetOrCreatePerformanceLite (Roon.ServiceProxies.MetadataService2.Performance performance, System.Nullable`1[T] timestamp) [0x0003c] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.Context.GetPerformanceLite (System.Sooid performanceid) [0x00033] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.MetadataTrackLite._Load (Sooloos.Broker.Metadata.Context metacx, Roon.ServiceProxies.MetadataService2.Track track) [0x000df] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.MetadataTrackLite..ctor (Sooloos.Broker.Metadata.Context metacx, Roon.ServiceProxies.MetadataService2.Track track) [0x00034] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.Context.GetOrCreateTrackLite (Roon.ServiceProxies.MetadataService2.Track track, System.Nullable`1[T] timestamp) [0x000ae] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.Module.GetCachedTrackLite (System.Sooid mediasooid, System.Nullable`1[T] max_age) [0x00036] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Metadata.Module.GetCachedTrackLite (System.Int64 mediaid, System.Nullable`1[T] max_age) [0x00007] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Music.Library.TryGetPlay (Sooloos.Broker.Music.Play play, Sooloos.Broker.Music.LibraryPlay& libraryplay, System.Collections.Generic.Dictionary`2[TKey,TValue] cache) [0x00120] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Music.LibraryProfileHistory.EnsurePlaysLoaded (System.Collections.Generic.Dictionary`2[TKey,TValue] cache) [0x000b2] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Music.Library.InitialLoadProfileHistory () [0x00066] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Music.LibraryMutationEnv.Finish () [0x01d8d] in <43022fa7e52b41e78fcc13e5473c7694>:0
at Sooloos.Broker.Music.Library.EndMutation () [0x00068] in <43022fa7e52b41e78fcc13e5473c7694>:0
Hey @beka
Two zip folders are uploaded, one is the original log set that prompted this thread, which dates back to the 5th. The second are more recent logs pulled this morning for reference following a unexpected crash overnight.
Please let me know what/when I can provide additional information to help troubleshoot.
Thanks.
Any chance you could please narrow down the time window when the most recent and unexpected crash happened? It was on January 16th, at about what time?
As I continue to receive the database loading error, I am keeping logs for each instance. Do you want these uploaded as well or is more information detrimental to your analysis at this point?
Thanks for your thoroughness . We’ll ask for them if the ones we already have prove to be inconclusive, so if you could please hold on to them for a little while longer, that’d be great.
I’m sorry that we didn’t yet have a chance to get back to you on this. I’ll make it a point to follow up with you Monday morning when we return to work.
Thanks again for sending the logs over! Unfortunately, they were inconclusive as to what the issue is, there doesn’t appear to be any corruption traces in these logs.
Yes, can you please upload any new log sets you have? If you can also make short screen recording and include this with the logs, it may help. Thanks!
Hi @noris
I am uploading a new set of logs. The timestamp for the database load error is ~09:45 MT on January 30, 2022. Prior to getting the error I had to relaunch roon as it became largely unresponsive, lost connection with all RAAT devices, which I initially identified by issues using the roon remote app on iOS, which I captured by screen recording.
Not on the ios recording I am frequently pressing pause or next song, which you cannot see, as the app and core are not responsive.
I also have recordings of the Core from that demonstrate the behavior before relaunch, the error, the restart and then in a new recording, the successful launch of the application.
One additional odd behavior I cannot resolve is the Core will not connect to Roon Bridge on networked Macs, but will connect to HQPlayer on those same machines under the same network conditions.
Thanks for sending those logs over, I can confirm receipt of them and the videos! Looking over the log, there does appear to be that same Critical trace you mentioned before:
I’ve escalated your case up the chain to QA and/or the dev team, once I have further feedback from them, I will let you know!
We are discussing your case with the team and we were hoping that you could send us a screenshot of the error message that you receive when the database issue occurs, e.g. when you see this message:
You can upload screenshots to the forum using these directions:
I have included a recent screenshot from the a recent error message. I have uploaded the log files from this error, which happened on February 19, 2022 at 10:15 am MT.
One other piece of info that may be helpful is that roonbridge is non-functional to any computer roon bridge endpoint. I have to use HQPlayer or Airplay to these computer endpoints to establish a connection from the roon core–true for 3 mac computers used as endpoints.
Thanks for all your work digging into this complex issue.
Do you by any chance have Private Relay turned on for the Monterey PC? We have seen this setting cause communication issues in the past:
As for the main issue at hand, I think we’ll need to run some further tests on your database to see what is going on, can we kindly ask that you restore the database that gives the error loading library message and then upload the database to the following link and let us know once uploaded.
. We’ll ask for them if the ones we already have prove to be inconclusive, so if you could please hold on to them for a little while longer, that’d be great.
