permanentmarker

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. 🙃

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.