-
Notifications
You must be signed in to change notification settings - Fork 261
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
Waiting for worker... (Vanilla Docker-Compose Install) #420
Comments
Hi @mikep11, do you make any changes in the dockerfile? is your project on github? |
No, I've made no changes. The project is on a private server.
|
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:
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 |
Hi @codinggeeks06, I will check but don't have time right now. |
Hi @codinggeeks06, which logs should I check? I ran |
Having this same issue. 👍 |
The demo notebooks are stuck "Waiting for worker ..."
This is a brand-new install, followed all the instructions.
.env file:
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 refusedResults 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?
The text was updated successfully, but these errors were encountered: