You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
gevent lib is not installed on container and when it starts worker I see following error.
I do not understand how did you managed to run this version without seeing this error.
To Reproduce
Steps to reproduce the behavior:
use latest images with tag 0.34.0 or 0.34.0rc1 from dockerhub
Running on prod and compose parameters
After workers started I see log
Started Celery workers[worker1, worker2] and Flower UI.
After server starts I see in the log
File "/usr/local/lib/python3.6/site-packages/gunicorn/workers/ggevent.py", line 22, in
73218f80f0a8bcaaa3f5f9d2c04fcabd8fa3a4feb0619aeb716e09856a865a85
raise RuntimeError("You need gevent installed to use this worker.")
Expected behavior
If I switch back to 0.33.0rc1 which is current latest, it works with everything else is same.
Additional context
Running on aws ECS, but should not have an effect on this error.
The text was updated successfully, but these errors were encountered:
Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.67. Please mark this comment with 👍 or 👎 to give our bot feedback!
Describe the bug
gevent lib is not installed on container and when it starts worker I see following error.
I do not understand how did you managed to run this version without seeing this error.
To Reproduce
Steps to reproduce the behavior:
Started Celery workers[worker1, worker2] and Flower UI.
File "/usr/local/lib/python3.6/site-packages/gunicorn/workers/ggevent.py", line 22, in
73218f80f0a8bcaaa3f5f9d2c04fcabd8fa3a4feb0619aeb716e09856a865a85
raise RuntimeError("You need gevent installed to use this worker.")
Expected behavior
If I switch back to 0.33.0rc1 which is current latest, it works with everything else is same.
Additional context
Running on aws ECS, but should not have an effect on this error.
The text was updated successfully, but these errors were encountered: