It appears my library still becomes unstable / unavailable intermittently.
Since we have addressed the memory issue (I think), what do you see as the cause and/or solution to this issue now?
Still periodically have to restart my server after the “library becomes unavailable.”
I was going to upload a new version of the log files but I noticed that now there is also a dotmem folder in the logs folder that is almost 8 gigabytes in size? curious if you added this for diagnostics / what is this purpose/function of this folder? is it temporary?
Please advise as I can’t zip up the logs folder and upload it since it is > 100MB.
Thank you!
Alan
Hello @Alan_Goldenberg
We’re seeing clear traces of library corruption in the logs:
09/04 02:34:58 [Local 09/03 21:34:58] Error: [broker/database] corruption detected: IO error: /roon/data/RoonServer/Database/Core/891fc774eaa541169c7f338427afb052/broker_4.db/12732522.ldb: Too many open files
You mentioned that you started from scratch with a new library. Just to be sure, could you please:
- Stop the Roon Server from the WebUI.
- Reinstall the Roon Server software.
- Rename the
Databasefolder before restarting, so Roon creates a completely clean library.
If a brand new, clean library becomes corrupted again, this would strongly suggest an underlying hardware issue, most likely a failing drive.
Should I also rename the existing Logs folder to OLD_Logs before restarting?
Recall there is an 8 gigabyte dotmem folder still inside the current/existing Logs folder.
How will I know that the database rebuild completed?
I’d imagine I need to wait before launching Roon remote and trying to access the Roon server… Am I correct that if I try to access the server before it finishes rebuilding the database, I will get a warning?
I don’t want to interrupt the process, but I also don’t know how long it’s supposed to take, and I don’t know if there is a way to check the state of the database rebuild process.
What happens when you touch the “Select a different Roon Server” button?
So try touching the Yes button and then see what happens… If you’ve reinstalled the Roon operating system, the Roon client may still be looking for the “old” Roon Server…
Hi @Alan_Goldenberg,
Thanks for the additional information!
When on the webUI - where you reinstalled the operating system for your Nucleus, you can also select ‘Reset’ under ‘Roon Database & Settings’ which will reset your database.
Based on a fresh diagnostic report from your Nucleus, the last traces of database corruption we see are from this time stamp:
[Local 09/04 07:46:54] Warn: [broker] detected corrupt database, notifying client Is this before or after you attempted a database reset?
Thank you!
Hi @Alan_Goldenberg,
Thanks for the screenshot - what’s odd is that when you refresh the Roon Server database, it usually resets the log set that follows the database. In your case, we’re not seeing a log refresh around the times given.
Since a few days have passed, how are things performing?
So far so good.
Things are almost back to normal.
Haven’t encountered any issues like the library becoming unavailable or corrupted, but now there is a 5-10 second delay after clicking the play button in roon that was never there before. After the delay, I can hear
two audible “pops” (sounds like “pop-pop”) and then music begins playing.
Would like to know if I can remove the old logs / dotmem folder per my previous emails and what might be causing this new latent behavior?
Hello @Alan_Goldenberg
The .dotmem folder was part of additional diagnostic data collection. We have already excluded it from your setup, so it should disappear automatically.
As for the latency you are now experiencing — this can be caused by a variety of factors, for example:
- Improper shutdowns of the system
- SSD or storage issues
- Other underlying hardware or filesystem-related problems
- Viruses
- Third party sofrware
Regarding the “pop-pop” noises — could you please clarify on which device you hear them, how exactly it is connected, and whether you have Resync Delay enabled for that device? This information will help us narrow down the cause. Delay may be related to the background library analysis. Please let us know if the behaviour has improved now?
i stream music from the nucleus one to a meitner ma-3, then to a meitner pre, then to my amps. both the nucleus and the ma-3 are connected to the network using a cisco business class switch via ethernet cable.
I’ve tried adjusting the resync delay, increasing it incrementally by 500ms as noted. i got up to 5000ms and still hear the pop pop at the beginning of every track.
when i play music from other digital sources through the meitner ma3, there are no pops (via coax, toslink, or spdif).
when i play music from the nucleus through the Meitner (via ethernet network connection), there is an audible pop:pop sound just before playback starts and i can confirm the pop:pop is only coming from one channel (left channel).
i never heard this from the nucleus before we did the rebuild.
Hey @Alan_Goldenberg,
Thanks for the additional information! Only the left channel pops → suggests it’s not just a “relay click” or muting relay (which are usually symmetrical) but something in the digital stream initialization or clock sync.
Resync delay didn’t solve it (even up to 5 seconds) → so the pop isn’t happening during the music start, but right when the MA-3 locks onto Roon’s stream.
Things to try / check next
- MA-3 firmware - Double-check you’re on the latest Meitner firmware. Past updates have specifically addressed “pops/clicks” on input changes for some users. If you’re not sure, I can point you to the EMM Labs update process.
- In Roon, try enabling the MA-3’s AirPlay or UPnP endpoint (if supported).
- If possible, connect the Nucleus One directly to the MA-3 via USB. If pops vanish, that confirms it’s the network → DAC handshake, not general playback.
Switch/network isolation
- Cisco business switches can sometimes introduce quirks with RAAT (especially if IGMP snooping, QoS, or energy-saving features are enabled).
- Try plugging both the Nucleus and MA-3 into a simple unmanaged gigabit switch or straight into your router.
- If the pops disappear, the Cisco config is the culprit.
Left channel only clue
- In Roon’s DSP Engine, try enabling a headroom adjustment (e.g., -3 dB) or upsampling all output to a fixed sample rate (say 192/24).
- If that masks the pop, it means the DAC is misinterpreting the very first PCM frame from RAAT on that channel.
Thanks Alan, we’ll monitor for your response! 