Apologies for the new-user question, but I don't have a ton of experience here. Is there a way to learn more about what the beets container is doing 'in the background' (eg, when I'm not interacting with it or running any kind of import/update/etc operation)?

The container logs repeat:
error: unknown command 'web'
...but otherwise don't offer much insight.

I've noticed that beets is typically using between 5%-30% more CPU on my Unraid server in short spiky cycles when I think it should just be idle. Here's a before/after view of cpu usage when the container is started, vs when I stop the container.

Edited June 17, 20251 yr by permanentmarker
Added logging context

Updating this in case anyone stumbles across the above post: the web plugin was at fault, beets was repeatedly trying to launch it and failing, forever, rather than gracefully backing off or giving up. 🙃

Regardless of what issue you are experiencing, what you should try if you are stuck is remove the container, then use CA cleaner plugin to completely remove configs (or do it manually if you are familiar with your file system). Reinstall the container from Apps and you should be back to a working state.

As mentioned several times here, there seems to be a database issue and the python code clearly can't handle some exceptions gracefully. None of that really matters if you only want to get to a working state.