Waiting for worker... (Vanilla Docker-Compose Install)
mikep11 opened this issue · comments
The demo notebooks are stuck "Waiting for worker ..."
This is a brand-new install, followed all the instructions.
.env file:
NOTEBOOKS_PATH=../mercury-deploy-demo/
DJANGO_SUPERUSER_USERNAME=adminusername
DJANGO_SUPERUSER_PASSWORD=astrongpassword
DJANGO_SUPERUSER_EMAIL=username@email.com
ALLOWED_HOSTS=[static, public user ipv4],[static, public server ipv4],0.0.0.0
SECRET_KEY="******************************************"
DEBUG=False
SERVE_STATIC=False
WELCOME=/app/notebooks/welcome.md
TIME_ZONE=US/Eastern
DJANGO_LOG_LEVEL=INFO
MERCURY_VERBOSE=0
ACCOUNT_EMAIL_VERIFICATION=none
Looking at Issue #391, I implemented the changes recommended by @mariliaribeiro here. No change.
I saw some issues with a number of files containing references to port 8000 vice 9000. I swapped all to port 9000 using grep -rl :8000 . | xargs sed -i 's/:8000/:9000/g'. No change in results. No change.
Results from celery status: ConnectionRefusedError: [Errno 111] Connection refused
Results from django-errors.log: [Blank file]
I'm not sure where to find any more answers describing what is going on. Are there other logs that I can pull that would assist in troubleshooting?
No, I've made no changes. The project is on a private server.
Docker version 20.10.24+dfsg1, build 297e128
docker-compose version 1.29.2, build unknown
docker-py version: 5.0.3
CPython version: 3.11.2
OpenSSL version: OpenSSL 3.0.11 19 Sep 2023
Hi @mikep11,
There must be some bug in our deployment code. Have you managed to run Mercury locally?
When I get a terminal in the Mercury docker image, it seems to run without error:
Version: 2.3.7
Performing system checks...System check identified no issues (0 silenced).
February 16, 2024 - 13:28:08
Django version 4.2.2, using settings 'server.settings'
Starting ASGI/Daphne version 4.0.0 development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
However, it is a headless server, so I can't test this instance.
manage.py test results in the same errors as #416.
hey, can you check logs of mercury?? does it say it sends requests to 127.0.0.1:8000:9000??
cause this same problem happened to me and I got this error.
Hi @codinggeeks06,
I will check but don't have time right now.
Hi @codinggeeks06, which logs should I check? I ran grep -r :8000:9000 on both the /app and /var/log with no results.
/app/django-errors.log and /app/mercury/django-errors.log are both blank.
Having this same issue. 👍