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

celery not restarted on deploy #97

Open
foobacca opened this issue Apr 10, 2015 · 1 comment
Open

celery not restarted on deploy #97

foobacca opened this issue Apr 10, 2015 · 1 comment
Milestone

Comments

@foobacca
Copy link
Collaborator

deploying inasp site recently, I'd added a task in main/tasks.py but it wasn't active after the deploy. Restarting celerybeat and celeryd fixed that, but it wasn't done by dye.

@decentral1se
Copy link
Member

decentral1se commented Oct 2, 2017

Oof, I got bitten by this.

EDIT: Solved this with a local task:

    if env in PRODUCTION:
        call(['supervisorctl', 'restart', 'celery-worker-default'])

Problems with dye doing this might be:

  • What is the celery workers name? This is defined in the Puppet configuration.
  • Is Celery managed by Supervisor? If not, a warm shutdown of celery is needed, otherwise, supervisorctl call is needed.

@decentral1se decentral1se added this to the P1: MUST milestone Nov 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants