#celery

I have a question about celery chains, can anyone help? https://stackoverflow.com/questions/49553620/do...

I am having awful trouble with Celery beat cron based tasks and timezones. So I have been using celery/beat for 3 years, and every time the time changes due to DST, I have just run a script to change my celery timezones, however as I have more and more projects/tasks using celery I have finally decided to sort my timezone issue out

So if I run "date" from my shell, I get: "Thu Mar 29 12:37:22 BST 2018"

And with no celery timezone/utc options, if I set a task to run at 11.00am, it will run at 12.00am +1 hour

So I tried adding " CELERY_TIMEZONE = Europe/London CELERY_ENABLE_UTC = False "

When I run my beat worker, I see some output text.. "Timezone changed to 'Europe/London'" however none of my tasks run when expected, I even tried off setting the times by +/- an hour to actually get the tasks running with a valid timezone config, but no such luck

Anyone have any other pointers/suggestions I could try?

I have also tried changing CELERY_TIMEZONE = UTC (as suggested by a few Stackoverlfow posts) but this didn't help either

maybe its stored in your scheduler backend thing?

(wild guess,no idea about anything)

I doubt it, because when I change the timezone in my configutation, celery beat output tells me "Timezone now set to XXX" etc

and if I add an invalid timezone, it throws me out

hello, in the doc it's say use celery multi for a systemd daemon. But some guys on github said that celery multi is not for production

any help here ?