Skip to content
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

CELERYD_FORCE_EXECV causes crash on Ubuntu Oneiric #122

Closed
mattlong opened this issue Mar 28, 2012 · 2 comments
Closed

CELERYD_FORCE_EXECV causes crash on Ubuntu Oneiric #122

mattlong opened this issue Mar 28, 2012 · 2 comments

Comments

@mattlong
Copy link

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.

@ask
Copy link
Contributor

ask commented Apr 20, 2012

Fixed by ask/celery@8adf8e8

2.5 backport of this is in the 2.5-backport branch,
I'd be very happy if you tested it by doing:

pip install -U https://github.com/ask/celery/zipball/2.5-backport

@ask ask closed this as completed Apr 20, 2012
@mattlong
Copy link
Author

I missed your response requesting I test the 2.5-backport branch. I'd be happy to do so now, but that branch seems to have disappeared...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants