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
Celery worker should always be alive even if its idle or processing the data.
Actual Behavior
At first Celery workers start executing as expected but after 30 to 40 mins it is getting offline and after checking the logs got to know that the MainProcess is getting cancelled automatically. It doesn't matter whether I send any data to queue or not but it is just stopping but ForkPoolWorker are working even though it is marked as offline worker in Flower.
I have tried this method but no luck.
I have upgraded my project from Django 2.2 to Django 4.2 and also upgrade the celery, django-celery-results and django-celery-beat accordingly. After the upgrade I am getting this error.
Checklist
main
branch of Celery.contribution guide
on reporting bugs.
for similar or identical bug reports.
for existing proposed fixes.
to find out if the bug was already fixed in the main branch.
in this issue (If there are none, check this box anyway).
Mandatory Debugging Information
celery -A proj report
in the issue.(if you are not able to do this, then at least specify the Celery
version affected).
main
branch of Celery.pip freeze
in the issue.to reproduce this bug.
Optional Debugging Information
and/or implementation.
result backend.
broker and/or result backend.
ETA/Countdown & rate limits disabled.
and/or upgrading Celery and its dependencies.
Related Issues and Possible Duplicates
Related Issues
Possible Duplicates
Environment & Settings
5.3.6 (emerald-rush)
celery report
Output:Steps to Reproduce
Required Dependencies
Python Packages
pip freeze
Output:Other Dependencies
N/A
Minimally Reproducible Test Case
Expected Behavior
Celery worker should always be alive even if its idle or processing the data.
Actual Behavior
At first Celery workers start executing as expected but after 30 to 40 mins it is getting offline and after checking the logs got to know that the
MainProcess
is getting cancelled automatically. It doesn't matter whether I send any data to queue or not but it is just stopping butForkPoolWorker are working
even though it is marked as offline worker in Flower.Note I have masked the data with some data
I am using the same setup in my localhost machine , there it is working as aspected
RabbitMQ Details:
RabbitMQ 3.12.10
Erlang 26.2.2
The text was updated successfully, but these errors were encountered: