-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Processing stuck in "Queued" state #387
Comments
@lucasgonze Thanks for the report. |
Note that this magma repo is big enough with about 1/2 of it that's .git metadata (not that this matters, just a note) |
Your report having a log is great BTW. Thanks for this.
It feels as if the worker is trying to connect to the DB before the DB was actually created fully (e.g. from running the migrations that create/update the tables schema are applied) That's really weird |
@lucasgonze can you confirm that the same issue occurs with even a tiny project? Say a scan_package pipeline with this URL from a PyPI package that is a few KB https://files.pythonhosted.org/packages/eb/5b/f82983127b1a1a4db83ee290e00a94a2b08c566fa6c58466e82ed7b0a76f/boolean.py-3.8-py2.py3-none-any.whl (that's a dep of ScanCode FWIW) |
That's correct. This is an Intel. |
I think that's the right diagnosis. After killing the first run and restarting, I got this following:
Log of the 2nd run attached. This includes all CLI activity from the initial install through the second run. second run log.txt Race conditions are particularly likely on this 2017 system because the hardware is older and slower. |
I'm happy to do that if it's still useful. |
In some case when using docker compose up, the worker processes may start before the web process's database migration is completed. This trigger byzantine errors that are not obvious except by looking in the logs and will let you start a pipeline that will be queued forever. To solve this issue we install the wait-for-it script available in Debian by @vishnubob and as suggested in the Docker documentation. In the docker-compose.yml, we let the worker wait for the web processing to be complete when gunicorn exposes port 8000 and web container is available. Reported-by: Lucas Gonze @lucasgonze Reference: #387 Reference: https://docs.docker.com/compose/startup-order/ Reference: https:/vishnubob/wait-for-it Reference: https://tracker.debian.org/pkg/wait-for-it Signed-off-by: Philippe Ombredanne <[email protected]>
Fix merged in main branch ce21929 |
Context: 2017 Air running OS X Monterey
Install and run...
Zip up a project to analyze and open the Scancode UI:
.
Terminal log:
log.txt
The text was updated successfully, but these errors were encountered: