title: Celery workers failing in aws elastic beanstalk [exited: celeryd-worker (exit status 1; not expected)]
body: <p>I've been trying to follow this thorough explanation on how to deploy a django app with celery worker to aws elastic beanstalk:</p>
  
  <p><a href="https://stackoverflow.com/questions/41161691/how-to-run-a-celery-worker-with-django-app-scalable-by-aws-elastic-beanstalk/41161692#41161692">How to run a celery worker with Django app scalable by AWS Elastic Beanstalk?</a></p>
  
  <p>I had some problems installing pycurl but solved it with the comment in:</p>
  
  <p><a href="https://stackoverflow.com/questions/36339529/pip-requirements-txt-global-option-causing-installation-errors-with-other-pack/41097851#41097851">Pip Requirements.txt --global-option causing installation errors with other packages. &quot;option not recognized&quot;</a></p>
  
  <p>Then i got:</p>
  
  <pre><code>[2019-01-26T06:43:04.865Z] INFO  [12249] - [Application update app-190126_134200@28/AppDeployStage0/EbExtensionPostBuild/Infra-EmbeddedPostBuild/postbuild_1_raiseflags/Command 05_celery_tasks_run] : Activity execution failed, because: /usr/bin/env: bash
    : No such file or directory
     (ElasticBeanstalk::ExternalInvocationError)
  </code></pre>
  
  <p>But also solved it: it turns out I had to convert "celery_configuration.txt" file to UNIX EOL (i'm using Windows, and Notepad++ automatically converted it to Windows EOL).</p>
  
  <p>With all these modifications I can successfully deploy the project. But the problem is that the periodic tasks are not running.</p>
  
  <p>I get:</p>
  
  <pre><code>2019-01-26 09:12:57,337 INFO exited: celeryd-beat (exit status 1; not expected)
  2019-01-26 09:12:58,583 INFO spawned: 'celeryd-worker' with pid 25691
  2019-01-26 09:12:59,453 INFO spawned: 'celeryd-beat' with pid 25695
  2019-01-26 09:12:59,666 INFO exited: celeryd-worker (exit status 1; not expected)
  2019-01-26 09:13:00,790 INFO spawned: 'celeryd-worker' with pid 25705
  2019-01-26 09:13:00,791 INFO exited: celeryd-beat (exit status 1; not expected)
  2019-01-26 09:13:01,915 INFO exited: celeryd-worker (exit status 1; not expected)
  2019-01-26 09:13:03,919 INFO spawned: 'celeryd-worker' with pid 25728
  2019-01-26 09:13:03,920 INFO spawned: 'celeryd-beat' with pid 25729
  2019-01-26 09:13:05,985 INFO exited: celeryd-worker (exit status 1; not expected)
  2019-01-26 09:13:06,091 INFO exited: celeryd-beat (exit status 1; not expected)
  2019-01-26 09:13:07,092 INFO gave up: celeryd-beat entered FATAL state, too many start retries too quickly
  2019-01-26 09:13:09,096 INFO spawned: 'celeryd-worker' with pid 25737
  2019-01-26 09:13:10,084 INFO exited: celeryd-worker (exit status 1; not expected)
  2019-01-26 09:13:11,085 INFO gave up: celeryd-worker entered FATAL state, too many start retries too quickly
  </code></pre>
  
  <p>I also have this part of the logs:</p>
  
  <pre><code>[2019-01-26T09:13:00.583Z] INFO  [25247] - [Application update app-190126_161213@43/AppDeployStage1/AppDeployPostHook/run_supervised_celeryd.sh] : Completed activity. Result:
    [program:celeryd-worker]
    ; Set full path to celery program if using virtualenv
    command=/opt/python/run/venv/bin/celery worker -A raiseflags --loglevel=INFO
  
    directory=/opt/python/current/app
    user=nobody
    numprocs=1
    stdout_logfile=/var/log/celery-worker.log
    stderr_logfile=/var/log/celery-worker.log
    autostart=true
    autorestart=true
    startsecs=10
  
    ; Need to wait for currently executing tasks to finish at shutdown.
    ; Increase this if you have very long running tasks.
    stopwaitsecs = 600
  
    ; When resorting to send SIGKILL to the program to terminate it
    ; send SIGKILL to its whole process group instead,
    ; taking care of its children as well.
    killasgroup=true
  
    ; if rabbitmq is supervised, set its priority higher
    ; so it starts first
    priority=998
  
    environment=PYTHONPATH="/opt/python/current/app/:",PATH="/opt/python/run/venv/bin/:%%(ENV_PATH)s",RDS_PORT="5432",RDS_DB_NAME="ebdb",RDS_USERNAME="foobar",PYCURL_SSL_LIBRARY="nss",DJANGO_SETTINGS_MODULE="raiseflags.settings",RDS_PASSWORD="foobar",RDS_HOSTNAME="something.something.eu-west-1.rds.amazonaws.com"
  
    [program:celeryd-beat]
    ; Set full path to celery program if using virtualenv
    command=/opt/python/run/venv/bin/celery beat -A raiseflags --loglevel=INFO --workdir=/tmp -S django --pidfile /tmp/celerybeat.pid
  
    directory=/opt/python/current/app
    user=nobody
    numprocs=1
    stdout_logfile=/var/log/celery-beat.log
    stderr_logfile=/var/log/celery-beat.log
    autostart=true
    autorestart=true
    startsecs=10
  
    ; Need to wait for currently executing tasks to finish at shutdown.
    ; Increase this if you have very long running tasks.
    stopwaitsecs = 600
  
    ; When resorting to send SIGKILL to the program to terminate it
    ; send SIGKILL to its whole process group instead,
    ; taking care of its children as well.
    killasgroup=true
  
    ; if rabbitmq is supervised, set its priority higher
    ; so it starts first
    priority=998
  
    environment=PYTHONPATH="/opt/python/current/app/:",PATH="/opt/python/run/venv/bin/:%%(ENV_PATH)s",RDS_PORT="5432",RDS_DB_NAME="ebdb",RDS_USERNAME="puigdemontAWS",PYCURL_SSL_LIBRARY="nss",DJANGO_SETTINGS_MODULE="raiseflags.settings",RDS_PASSWORD="holahola",RDS_HOSTNAME="aa1m59206y4fljn.cdreg3t50bbl.eu-west-1.rds.amazonaws.com"
    No config updates to processes
    celeryd-beat: ERROR (not running)
    celeryd-beat: ERROR (abnormal termination)
    celeryd-worker: ERROR (not running)
    celeryd-worker: ERROR (abnormal termination)
  [2019-01-26T09:13:00.583Z] INFO  [25247] - [Application update app-190126_161213@43/AppDeployStage1/AppDeployPostHook] : Completed activity. Result:
    Successfully execute hooks in directory /opt/elasticbeanstalk/hooks/appdeploy/post.
  [2019-01-26T09:13:00.583Z] INFO  [25247] - [Application update app-190126_161213@43/AppDeployStage1] : Completed activity. Result:
    Application version switch - Command CMD-AppDeploy stage 1 completed
  [2019-01-26T09:13:00.583Z] INFO  [25247] - [Application update app-190126_161213@43/AddonsAfter] : Starting activity...
  [2019-01-26T09:13:00.583Z] INFO  [25247] - [Application update app-190126_161213@43/AddonsAfter/ConfigLogRotation] : Starting activity...
  [2019-01-26T09:13:00.583Z] INFO  [25247] - [Application update app-190126_161213@43/AddonsAfter/ConfigLogRotation/10-config.sh] : Starting activity...
  [2019-01-26T09:13:00.756Z] INFO  [25247] - [Application update app-190126_161213@43/AddonsAfter/ConfigLogRotation/10-config.sh] : Completed activity. Result:
    Disabled forced hourly log rotation.
  [2019-01-26T09:13:00.756Z] INFO  [25247] - [Application update app-190126_161213@43/AddonsAfter/ConfigLogRotation] : Completed activity. Result:
    Successfully execute hooks in directory /opt/elasticbeanstalk/addons/logpublish/hooks/config.
  </code></pre>
  
  <p>I don't know if it has something to do with the error, but notice above the line [[ PATH="/opt/python/run/venv/bin/:%%(ENV_PATH)s" ]] --> shouldn't ENV_PATH be something else?:</p>
  
  <pre><code>environment=PYTHONPATH="/opt/python/current/app/:",PATH="/opt/python/run/venv/bin/:%%(ENV_PATH)s",RDS_PORT="5432",RDS_DB_NAME="ebdb",RDS_USERNAME="foobar",PYCURL_SSL_LIBRARY="nss",DJANGO_SETTINGS_MODULE="raiseflags.settings",RDS_PASSWORD="foobar",RDS_HOSTNAME="something.something.eu-west-1.rds.amazonaws.com"
  </code></pre>
  
  <p>I'ts my first time deploying an app with celery, and i'm really lost to be honest. I fought a lot to solve the first two errors (i'm really amateur), and now that i get this I don't even know where to start.</p>
  
  <p>Also, i'm not sure if I'm using "celery_configuration.txt" the right way. The only thing I edited was the 2 places where it says "django_app", which I changed for "raiseflags" (the name of my django project). Is this correct?</p>
  
  <p>Does anyone know how to solve it? I can paste my files if needed, but they are just like the ones provided in the first link. I'm using Windows.</p>
  
  <p>Thank you very much!</p>