I've had a constant message of: ⚠ 1 service needs attention shelfarr-init — 28 of 29 healthy · open the Apps page When asking AI, it says that the Init function doesnt run constantly and things are okay. Can we get a filter in place to stop this service from throwing the fault all the time?
8 replies
Chris wrote:
Thanks for flagging this. You're right, it shouldn't keep nagging you. SparkBox already hides a setup helper like shelfarr-init once it finishes cleanly. It only shows up like this when the helper stopped with an error. That helper has one job: it sets the owner of Shelfarr's audiobooks, ebooks and downloads folders. If those folders live on a network share or a Windows drive, that storage manages its own file owners and refuses the change. The helper stops with an error, and the warning stays, even though Shelfarr itself may be working fine. We've fixed that. The helper now leaves those folders as they are and finishes, so the warning clears after the update and Shelfarr starts normally. It's in the next SparkBox update. Once that's out, run sudo sparkbox upgrade (on Windows, open the box's terminal with wsl -d SparkBox -u root first and leave out sudo). If you want to confirm that's what happened on your box, run sudo sparkbox logs shelfarr-init. If the last lines say "Operation not permitted" or "Read-only file system", it's exactly this, and if Shelfarr opens normally you can ignore the warning until the update. If it says something else, paste those lines here (leave out any folder names you'd rather keep private).
Chris wrote:
Quick update: that fix is out now, in SparkBox 1.6.838. Legend and Backer boxes can update today. Use the update button on the dashboard, or run sudo sparkbox upgrade (on Windows, open the box's terminal with wsl -d SparkBox -u root first and leave out sudo). Other boxes get it automatically around 9 October. The update runs the shelfarr-init helper again, and this time it finishes, so the "1 service needs attention" warning should clear by itself. If it still shows after the update, run sudo sparkbox logs shelfarr-init and paste the last few lines here.
EineBeBoP wrote:
I still see 1 service needs attention related to the shelfarr-init. here are the requested logs. [WARN] sb-shelfarr-init is not running (state: exited, exit code 0). [WARN] sb-shelfarr-init has written no log at all — it stopped before the app itself started, [WARN] so the reason is Docker's line above, not inside the app. Nothing was changed on your box.
Chris wrote:
Sorry—I said this warning meant the helper had stopped with an error, but your log shows exit code 0, which means it completed successfully. This helper is meant to exit after its setup task; SparkBox 1.6.838 also changed it to leave network-share and Windows-drive folder ownership alone. That log by itself doesn't explain why the dashboard still flags it. Please tell me the SparkBox version currently shown on your dashboard. I've corrected what I know about this warning so we don't make the same assumption for the next person.
EineBeBoP wrote:
SparkBox v1.6.839 on an Ugreen NAS drive system.
Chris wrote:
Thanks — the clean exit you shared means the Shelfarr setup helper completed, so the earlier explanation that it stopped with an error was wrong. SparkBox 1.6.838 already includes the folder-ownership fix, and you’re on 1.6.839; the remaining warning appears to be the dashboard counting a successfully completed one-shot helper as unhealthy, which the log alone can’t confirm. I’ve recorded that mismatch for investigation. Could you check whether the warning is still present after refreshing the dashboard once?
EineBeBoP wrote:
Still present.
Chris wrote:
Thanks—that confirms the warning is still there on 1.6.839 after refreshing. The exit code 0 means the setup helper completed; it doesn't explain why the dashboard still flags it, so I don't want to guess at another fix. Does Shelfarr itself open and work, or is it also failing to start? Just let me know which.