我有一个 django 应用程序,它具有 celery 功能,所以我可以像下面那样成功运行 celery
celery -A tasks worker --loglevel=info
但众所周知,我们需要将它作为守护进程运行,所以我在文件夹中编写了以下celery.conf
文件/etc/supervisor/conf.d/
; ==================================
; celery worker supervisor example
; ==================================
[program:celery]
; Set full path to celery program if using virtualenv
command=/root/Envs/proj/bin/celery -A app.tasks worker --loglevel=info
user=root
environment=C_FORCE_ROOT="yes"
environment=HOME="/root",USER="root"
directory=/root/apps/proj/structure
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
但是当我尝试更新主管时supervisorctl reread
,supervisorctl update
我收到了来自supervisorctl status
celery FATAL Exited too quickly (process log may have details)
所以我去worker.log
归档并看到如下错误消息
Running a worker with superuser privileges when the
worker accepts messages serialized with pickle is a very bad idea!
If you really want to continue then you have to set the C_FORCE_ROOT
environment variable (but please think about this before you do).
User information: uid=0 euid=0 gid=0 egid=0
C_FORCE_ROOT
那么为什么即使我们在主管配置文件中将它设置为环境变量,它也会抱怨 呢?我在上面的 conf 文件中做错了什么?