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
Attempting to upgrade from django-celery 2.4.2 to 2.5.1. Setting CELERYD_FORCE_EXECV = True in my settings.py causes python manage.py celeryd to fail to start and infinitely loop an import error. I observed the same behavior in the demo project included with the django-celery source code. The stacktrace of the error that repeats indefinitely is shown here: http://pastebin.com/4WpQ14qd
To repro:
My environment consisted of a completely clean Ubuntu Oneiric server launched on Amazon AWS EC2. I made a new virtualenv and pip installed Django (1.4) and django-celery (2.5.1). I installed RabbitMQ 2.8.1 from the official RabbitMQ repository. I cloned the django-celery repository from github and added a single line near the top of the demproject's settings.py file: CELERYD_FORCE_EXECV = True. I then execute python manage.py celeryd from the command line. Commenting out the force_execv line results in celeryd starting up correctly.
The text was updated successfully, but these errors were encountered:
Attempting to upgrade from django-celery 2.4.2 to 2.5.1. Setting CELERYD_FORCE_EXECV = True in my settings.py causes
python manage.py celeryd
to fail to start and infinitely loop an import error. I observed the same behavior in the demo project included with the django-celery source code. The stacktrace of the error that repeats indefinitely is shown here: http://pastebin.com/4WpQ14qdTo repro:
My environment consisted of a completely clean Ubuntu Oneiric server launched on Amazon AWS EC2. I made a new virtualenv and pip installed Django (1.4) and django-celery (2.5.1). I installed RabbitMQ 2.8.1 from the official RabbitMQ repository. I cloned the django-celery repository from github and added a single line near the top of the demproject's settings.py file:
CELERYD_FORCE_EXECV = True
. I then executepython manage.py celeryd
from the command line. Commenting out the force_execv line results in celeryd starting up correctly.The text was updated successfully, but these errors were encountered: