3👍
Seems this should be fixed in new release and as a temporary workaround branch 3.0 was suggested https://github.com/celery/django-celery/issues/183#issuecomment-10846821.
1👍
Also this problem can be appear if you (as me) get
TIME_ZONE = 'UTC'
...
CELERY_TIMEZONE = 'Europe/Moscow'
in Django settings.py. This 2 strings can be in different parts of this large settings.py config file and in this case Celery beat (for example) will show you message that timezone is changed. Something like that: Timezone changed from 'UTC' to 'Europe/Moscow' but real beat time that you will see will be still in UTC. To fix it, just set correct Django TIME_ZONE setting:
TIME_ZONE = 'Europe/Moscow'
and Celery will pick it up!
Cheers.
- [Django]-Elastix API for communicating with django web application
- [Django]-Celery worker will not pick up a new task after the current one is finished
- [Django]-In Django, how can I calculate or update certain model fields BEFORE any validation happens?
- [Django]-Setting current user on django vanilla CreateView
0👍
At least according to the release notes, the timezone bug was fixed in .0.8 and .0.9.
Use celery 3.09 and django-celery 3.0.9
- [Django]-Adding many to many fields (M2M) manually in django?
- [Django]-Django multiple forms with modelchoicefield -> too many queries
- [Django]-Python private inheritance? How to trick isinstance()?
- [Django]-Django 1.10 password to be used with flask
- [Django]-Django – saving values from a form to database