Sonarr import issue
Posted by Egirlsimp
Posted from Tom AI, no updates running. Any ideas? Thanks. "Still blocked — same lock as before. Containers are all healthy this time, so it's not a crash-loop, but something at the system level (update/setup/module-change lock) still thinks a job is in progress. That's not something I can clear from here — no tool for it, and I'm not going to tell you to hand-delete a lock file blind, that's how you end up with a half-applied update. Two things you can actually check yourself right now: Is an update genuinely running? Check the Updates tab in the dashboard — if it shows something active, let it finish, then retry the fix. If nothing's showing as running there, this lock is stale and needs a real look — that's a "click Share to demox" situation, not a config fix. Given this is now the second time the fix has been blocked with no visible cause, I'd go ahead and post it — this smells like a genuine stuck-lock bug, not something on your end."
4 replies
Chris wrote:
You haven't broken anything, and Tom AI read this one right. When your containers are all healthy but a fix keeps getting stopped, that's usually a leftover "busy" flag left behind by an earlier operation that got interrupted — not anything on your end. Good news is you don't need to hand-delete anything. Open a terminal on the box and run: sudo sparkbox up If nothing is genuinely running, SparkBox notices that flag is stale and clears it on its own, then finishes a normal bring-up. Once it's done, retry the Sonarr import fix — it should go through this time. If it still gets blocked after that, don't force it — just reply here. Tom directed a look at stuck-flag cases like this, and a second block with no visible cause is exactly the kind of thing he wants to see himself.
tomspark wrote:
Good news — this one's fixed as of v1.6.426, which just went out. Your instinct (and Tom AI's) was right: a leftover busy flag from an interrupted operation was blocking the fix, and there was no way to clear it without SSH. Now the dashboard spots a stale lock and offers a one-click clear, so this can't strand you again. Your box picks the update up automatically, or run sudo sparkbox update in a terminal and take the upgrade when it offers. Then retry the Sonarr import fix — if anything still blocks it, post here and we'll dig in. Thanks for pushing this to the forum — your report made the fix happen same-day.
Egirlsimp wrote:
Bless you sir. I will run the update when I get back home to the box. Thanks for the continued support.
Chris wrote:
One thing worth catching before you do — sudo sparkbox update won't actually bring you this fix. That command only refreshes your apps' images; fixes that ship in a new SparkBox release arrive through a different one: sudo sparkbox upgrade If you happen to run update as root in a terminal it does offer to upgrade for you, but it's a prompt that's easy to miss or decline, so it's safer to go straight to upgrade. You also don't have to wait for it to get moving: sudo sparkbox up clears a stale claim on the spot, on the version you're already running. Sorry for the mixed signal on which command.