Strange Failed Child Process Loop

[nahnotnathan]

Previously working Beets Flask install suddenly broken.

When I log into Dozzle to see whats up this is what I get.

It usually just loops the Child Process died thing infinitely. On occasion this error will pop up:

Process SpawnProcess-10: Traceback (most recent call last): File "/usr/local/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap self.run() File "/usr/local/lib/python3.11/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/usr/local/lib/python3.11/site-packages/uvicorn/_subprocess.py", line 80, in subprocess_started target(sockets=sockets) File "/usr/local/lib/python3.11/site-packages/uvicorn/supervisors/multiprocess.py", line 64, in target return self.real_target(sockets) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/uvicorn/server.py", line 67, in run return asyncio_run(self.serve(sockets=sockets), loop_factory=self.config.get_loop_factory()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/uvicorn/_compat.py", line 30, in asyncio_run return runner.run(main) ^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/runners.py", line 118, in run return self._loop.run_until_complete(task) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/base_events.py", line 654, in run_until_complete return future.result() ^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/uvicorn/server.py", line 71, in serve await self._serve(sockets) File "/usr/local/lib/python3.11/site-packages/uvicorn/server.py", line 78, in _serve config.load() File "/usr/local/lib/python3.11/site-packages/uvicorn/config.py", line 445, in load self.loaded_app = self.loaded_app() ^^^^^^^^^^^^^^^^^ File "/repo/backend/beets_flask/server/app.py", line 33, in create_app from ..database import setup_database File "/repo/backend/beets_flask/database/__init__.py", line 1, in <module> from .setup import db_session_factory, setup_database, with_db_session File "/repo/backend/beets_flask/database/setup.py", line 11, in <module> from .models import Base File "/repo/backend/beets_flask/database/models/__init__.py", line 2, in <module> from .states import CandidateStateInDb, FolderInDb, SessionStateInDb, TaskStateInDb File "/repo/backend/beets_flask/database/models/states.py", line 21, in <module> from beets.autotag import AlbumMatch File "/usr/local/lib/python3.11/site-packages/beets/autotag/__init__.py", line 30, in <module> from .match import Proposal, Recommendation, tag_album, tag_item File "/usr/local/lib/python3.11/site-packages/beets/autotag/match.py", line 24, in <module> import lap File "/usr/local/lib/python3.11/site-packages/lap/__init__.py", line 16, in <module> from ._lapjv import ( File "_lapjv_cpp/_lapjv.pyx", line 1, in init _lapjv ImportError: numpy.core.multiarray failed to import (auto-generated because you didn't call 'numpy.import_array()' after cimporting numpy; use '<void>numpy._import_array' to disable if you are certain you don't need it).

Any idea what happened here?

[pSpitzner]

Strange.

Did you change anything recently, like updating? We have the latest tag attached to v2.0.0-rc1 since a few weeks ago.

The child processes are workers for uvicorn, which could indeed crash due to the numpy issues, as the remaining logs suggest.
Seems that beets.autotag cant find the right compiled) numpy files.

[nahnotnathan]

Did you change anything recently, like updating? We have the latest tag attached to v2.0.0-rc1 since a few weeks ago.

Yeah, I use Watchtower and beets is auto-updated to the stable tag. I tried calling the new 2.0.0-rc1 tag and it also has the same issue. I also purged the DBs and config YAML files, deleted the cached images, and started fresh multiple times -- still persisted.

When I reverted to 1.2.0 the issue went away, so hopefully that can help pinpoint the issue. For now I'm just going to stick with that, but hopefully you can figure out a solution for 2.0.0-rc2

I'm running Docker on Ubunutu Server LTS. Let me know if there are any additional troubleshooting steps I can take to help you figure this out.

[semohr]

There might be a dependency that updated and is causing that issue. Needs more investigation to pinpoint.

We did not have any related changes that could cause this between version 1.2.0 and 1.2.1.

v1.2.0...v1.2.1

The only thing we can do is hope a future dependency update fixes this issue.

We will depend on you checking future versions as we can't reproduce the issue locally ;)

[nidstirr]

Hi, I am also having the Child process died loop issue.

Completely fresh install on the latest tag, using docker compose on a Debian 13 machine.

Posting for clarity!

[nahnotnathan]

Hi, I am also having the Child process died loop issue.

Completely fresh install on the latest tag, using docker compose on a Debian 13 machine.

Posting for clarity!

If you set the version to v1.2.0 in Docker Compose does it fix the issue for you as well?

[nidstirr]

Switched to stable tag, but yes, it did.