Celery Django Deployment завершается неудачно с Elastic Beanstalk из-за ImportError: невозможно импортировать имя 'Celery' (ElasticBeanstalk :: ExternalInvocationError) - PullRequest
0 голосов
/ 27 февраля 2019

Я получаю ошибки при попытке развернуть приложение django после настройки сельдерея.Работает нормально в местной среде.Похоже, что ни сельдерея не бьет, либо рабочий начинает.Я получаю сообщение об ошибке при попытке запустить работника сельдерея с помощью superviserd

[i-063a3b57f40eb2ffa] [2019-02-27T13:04:39.139Z] INFO  [22820] - [Application update app-8bc8-190227_130333@187/AppDeployStage0/EbExtensionPostBuild/Infra-EmbeddedPostBuild/postbuild_0_django_brain_dev/Command 04_start_celery_beat] : Completed activity. Result:
  celeryd-beat: ERROR (not running)
  celeryd-beat: ERROR (abnormal termination)

[i-063a3b57f40eb2ffa] [2019-02-27T13:04:40.021Z] INFO  [22820] - [Application update app-8bc8-190227_130333@187/AppDeployStage0/EbExtensionPostBuild/Infra-EmbeddedPostBuild/postbuild_0_django_brain_dev/Command 05_start_celery_worker] : Starting activity...
[i-063a3b57f40eb2ffa] [2019-02-27T13:04:42.397Z] INFO  [22820] - [Application update app-8bc8-190227_130333@187/AppDeployStage0/EbExtensionPostBuild/Infra-EmbeddedPostBuild/postbuild_0_django_brain_dev/Command 05_start_celery_worker] : Completed activity. Result:
  celeryd-worker: ERROR (not running)
  celeryd-worker: ERROR (abnormal termination)


  from celery import Celery
  File "/opt/python/current/app/django_app/celery.py", line 3, in <module>
  from celery import Celery
  ImportError: cannot import name 'Celery'
   (ElasticBeanstalk::ExternalInvocationError)

Команды контейнера:

 02_celery_tasks_config:
    command: "cat .ebextensions/files/celery_configuration.txt > /opt/elasticbeanstalk/hooks/appdeploy/post/run_supervised_celeryd.sh && chmod 744 /opt/elasticbeanstalk/hooks/appdeploy/post/run_supervised_celeryd.sh"
    leader_only: true

  03_celery_tasks_run:
    command: "sed -i 's/\r$//' /opt/elasticbeanstalk/hooks/appdeploy/post/run_supervised_celeryd.sh"
    leader_only: true

  04_start_celery_beat:
    command: "/usr/local/bin/supervisorctl -c /opt/python/etc/supervisord.conf restart celeryd-beat"
    leader_only: true

  05_start_celery_worker:
    command: "/usr/local/bin/supervisorctl -c /opt/python/etc/supervisord.conf restart celeryd-worker"

файл конфигурации celery.txt содержит

#!/usr/bin/env bash

# Get django environment variables
celeryenv=`cat /opt/python/current/env | tr '\n' ',' | sed 's/export //g' | sed 's/$PATH/%(ENV_PATH)s/g' | sed 's/$PYTHONPATH//g' | sed 's/$LD_LIBRARY_PATH//g' | sed 's/%/%%/g'`
celeryenv=${celeryenv%?}

# Create celery configuraiton script
celeryworkerconf="[program:celeryd-worker]
; Set full path to celery program if using virtualenv
command=/opt/python/run/venv/bin/celery worker -A djangobrain --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=$celeryenv"

celerybeatconf="[program:celeryd-beat]
; Set full path to celery program if using virtualenv
command=/opt/python/run/venv/bin/celery beat -A djangobrain --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=$celeryenv"

# Create the celery supervisord conf script
echo "$celeryworkerconf" | tee /opt/python/etc/celeryworker.conf
echo "$celerybeatconf" | tee /opt/python/etc/celerybeat.conf

# Add configuration script to supervisord conf (if not there already)
if ! grep -Fxq "[include]" /opt/python/etc/supervisord.conf
  then
  echo "[include]" | tee -a /opt/python/etc/supervisord.conf
  echo "files: celerybeat.conf celeryworker.conf" | tee -a /opt/python/etc/supervisord.conf
fi

# reread the supervisord config
/usr/local/bin/supervisorctl -c /opt/python/etc/supervisord.conf reread
# update supervisord in cache without restarting all services
/usr/local/bin/supervisorctl -c /opt/python/etc/supervisord.conf update

# Start/Restart celeryd through supervisord
supervisorctl -c /opt/python/etc/supervisord.conf restart celeryd-beat
supervisorctl -c /opt/python/etc/supervisord.conf restart celeryd-worker

1 Ответ

0 голосов
/ 15 апреля 2019

Это не ответ, но я отказался от пути Celery и прошел безсерверное развертывание в качестве решения.

Добро пожаловать на сайт PullRequest, где вы можете задавать вопросы и получать ответы от других членов сообщества.
...