· Is it possible to slow down the "Background Work" process?
For the past two nights, "Background Work" has been crashing my server. "Background Work" is scheduled to run between 1:00 AM and 5:00 AM. In the morning, I find my server burning hot with its fan running at full speed. I can't access the server remotely, either through its web interface or with Roon Remote. I have to unplug it, wait for it to cool down, and then restart it. Fortunately, these two crashes haven't caused any damage. The room temperature is 24°C (75°F). I will provide more technical details in subsequent messages.
Hypothesis: My server’s CPU must be at 100% for a very (too) long period, causing it to crash.
Hence my question: would it be possible to slow down the “Background Work”?
For now, I’ve decided to shut down my server at night, but that’s certainly not a solution because I imagine this “Background Work” is necessary.
Inadequate cooling solution violating intel’s specs at play? Properly built and working computers should be capable of running at nominal speed (100% load) without the thermal protection halting the CPU. Is your fan potentially defect or clogged? I believe it is also thinkable that the reason for the sever being unresponsive lies somewhere else and has nothing to do with the temps. Hard to tell from afar.
I had this happen too. I think it may have been due to having both background work and backup scheduled at the same time overnight. I’ve since taken background off a schedule and I haven’t had an overheating/crash since. I also now have some very quiet USB mini fans pointed at my fan-less case, just in case, but I doubt those would cool it as much as it was hot - it was hot enough to cook on! Mine is a NUC 7i5.
Thank you.
While waiting for a reply from RoonLabs, here is what I have done:
The backup is scheduled for 6:00 PM.
The “background work” schedule is now disabled.
I shut down the Roon server at night and when I am not at home.
This means that, for the time being, I can no longer use Roon ARC.
I hope this is only temporary, but I cannot take the risk of a fire.
Thank you for reaching out and providing such detailed system information and log timestamps. It is incredibly helpful. Turning off the server to avoid the risk of fire was absolutely the right call!
To answer your primary question: Yes, you can slow down the background work. The background tasks typically consist of metadata updates and Background Audio Analysis. You can throttle the analysis portion by navigating to Settings > Library in Roon. Look for Background Audio Analysis Speed and set it to Throttled. This limits the number of CPU cores Roon uses, which significantly reduces the processing load.
However, we need to address the hardware side of this issue. As @BlackJack correctly pointed out, a properly functioning computer should be able to run at 100% CPU utilization without halting. While it will get warm, the CPU should automatically manage its clock speeds (thermal throttling) to prevent crashing or critical overheating.
Because you are using an Intel NUC7I7BNH, which is a 7th-generation processor, the physical cooling system has likely degraded over the years. Specifically:
Thermal Paste: The thermal compound between the CPU and the heatsink has almost certainly dried out, losing its ability to transfer heat.
Dust Accumulation: Dust can easily clog the fan and internal heatsink fins, preventing hot air from escaping the chassis.
When Roon initiates its intensive overnight background work between 1:00 AM and 5:00 AM, the CPU ramps up. Because the degraded thermal paste cannot transfer the heat to the heatsink effectively, the fan spins at maximum speed trying to compensate, but the CPU ultimately overheats and locks up the machine to protect itself.
Recommendations:
Hardware Maintenance: We highly recommend opening the NUC case to carefully blow out any dust with compressed air. More importantly, removing the heatsink, cleaning off the old thermal paste, and applying a fresh layer of high-quality thermal compound is the true fix for this issue.
Software Band-Aid: In the meantime, you can leave your scheduled Background Work turned off, or keep it active but ensure the Audio Analysis Speed is set to "Throttled" as mentioned above.
Let us know if you decide to tackle the thermal paste replacement, or if adjusting the settings to "Throttled" keeps the system stable enough to leave it running overnight!
I’m going to open up the NUC case to remove the dust.
However, I don’t think I’m capable of replacing the thermal paste.
I’ll see if I can find a technician nearby to do it.
I saw similar during what I witnessed (which was in realtime) and my temp climbed higher than normal. I restarted Roonserver to stop what was occurring so it could have gotten worse.
Yes I fed back to another thread, as Roon Appliance on my Mac Mini hard crashed, and I had to kill the process. First time in a long time that has happened to me
Hi Dirk-Pitt, and thanks MusicD, BlackJack, DDPS, and Michael_Harris for the additional data points here.
Roon 2.71 (build 1674) is live now on the Early Access branch and includes memory and performance fixes in this exact area. Could you please give it a try and see if it holds up overnight with Background Work re-enabled? Here’s more info: EarlyAccess: Roon 2.71 Build 1674 and ARC 1.81 Build 422 are Live!
If anyone else in this thread has hit the same overnight crash, please feel free to try the EA build as well and let us know how it goes either way. That’ll help us confirm whether this is the same root cause across the board.
Hello @vadim and thank you for your message.
I’m going to wait a bit before doing this test.
Indeed, I already have several problems with the version of Roon 2.71 (build 1674) on the “Early Access” branch.
Hello @noris,
Thank you for your message.
Apologies for the late reply; I was away from home for a few days.
Currently, I shut down my Roon server every evening.
I plan to run a test of background work in a few days.
I will get back to you as soon as possible.
Just wanted to touch base on this. We’re still standing by to hear what you find once you re-enable the background work, and whether anything changes after that. If you’ve had a chance to test it, let us know what you’re seeing, thanks.
