-3👍
I solved my problem, it was a very simple solution, but it was also a weird one:
What I did was:
$ /etc/init.d/celerybeat restart
$ /etc/init.d/celeryd restart
$ service celeryd restart
I had to do this in that order, other way I’d get an ugly Error: No nodes replied within time constraint.
1👍
Use the following command to find the problem :
C_FAKEFORK=1 sh -x /etc/init.d/celeryd start
This usually happens because there are problems in your source project(permission issues, syntax error etc.)
As mentioned in celery docs:-
If the worker starts with “OK” but exits almost immediately afterwards
and there is nothing in the log file, then there is probably an error
but as the daemons standard outputs are already closed you’ll not be
able to see them anywhere. For this situation you can use the
C_FAKEFORK environment variable to skip the daemonization step
Good Luck
Source: Celery Docs
- Host Django with XAMPP on Windows
- Can't login to Django /admin interface
- Getting error with is_popup variable in django 1.9
- Accessing form fields as properties in a django view
- Error "Could not load Boto's S3 bindings."
0👍
its because the celery daemon might not be started. This is one reason. So kindly restart it using python manage.py celeryd –loglevel=INFO
- Django – CSRF token missing or incorrect
- Django form with just a BooleanField
- Django forms.ChoiceField without validation of selected value
- Django: ValueError: Lookup failed for model referenced by field account.UserProfile.user: auth.User
- Using bundle_files = 1 with py2exe is not working