按照此处找到的说明,我将脚本从github复制到 /etc/init.d/celeryd中 ,然后使其可执行;
$ ll /etc/init.d/celeryd -rwxr-xr-x 1 root root 9481 Feb 19 11:27 /etc/init.d/celeryd*
我按照说明创建了配置文件 / etc / default / celeryd :
# Names of nodes to start # most will only start one node: #CELERYD_NODES="worker1" # but you can also start multiple and configure settings # for each in CELERYD_OPTS (see `celery multi --help` for examples). CELERYD_NODES="worker1 worker2 worker3" # Absolute or relative path to the 'celery' command: CELERY_BIN="/usr/local/bin/celery" #CELERY_BIN="/virtualenvs/def/bin/celery" # App instance to use # comment out this line if you don't use an app #CELERY_APP="proj" # or fully qualified: #CELERY_APP="proj.tasks:app" # Where to chdir at start. CELERYD_CHDIR="/path/to/folder/containing/tasks/" # Extra command-line arguments to the worker CELERYD_OPTS="--time-limit=3000 --concurrency=3 --config=celeryconfig" # %N will be replaced with the first part of the nodename. CELERYD_LOG_FILE="/var/log/celery/%N.log" CELERYD_PID_FILE="/var/run/celery/%N.pid" # Workers should run as an unprivileged user. # You need to create this user manually (or you can choose # a user/group combination that already exists, e.g. nobody). CELERYD_USER="celery" CELERYD_GROUP="celery" # If enabled pid and log directories will be created if missing, # and owned by the userid/group configured. CELERY_CREATE_DIRS=1
注意 :我在CELERYD_OPTS中添加了 --config = celeryconfig 部分。
我创建了一个新的用户 celery 与
sudo useradd -N -M --system -s /bin/false celery
然后创建集体 celery 并向其中添加用户:
$ id celery uid=999(celery) gid=1005(celery) groups=1005(celery)
我将chown celery:celery用于文件夹:
/ var / run / celery /
/ var / log / celery /
当我尝试启动服务时,没有任何错误提示:
$ sudo service celeryd start celery init v10.0. Using config script: /etc/default/celeryd
但是状态使我“找不到pid”:
$ sudo service celeryd status celery init v10.0. Using config script: /etc/default/celeryd celeryd is stopped: no pids were found
实际上,ps -ef没有给出结果,也没有创建PID文件或日志文件:
$ ll /var/run/celery total 0 drwxr-sr-x 2 celery celery 40 Feb 19 14:13 ./ drwxr-xr-x 16 root root 620 Feb 19 12:35 ../ $ ll /var/log/celery total 8 drwxr-sr-x 2 celery celery 4096 Feb 19 14:13 ./ drwxr-xr-x 13 root root 4096 Feb 19 11:37 ../
附加信息:
$ pip freeze | grep celery celery==3.1.9
我想念什么?我应该在哪里寻找有关celeryd为什么不开始的更多线索?
我重复了您的步骤,并导致了同样的问题。问题是Celery使用者没有外壳。
进行更改-s /bin/false以-s /bin/bash解决此问题。原因是celeryd初始化脚本使用celery用户的shell执行celery命令。没有外壳程序,下面的su命令将静默退出。
-s /bin/false
-s /bin/bash
_chuid () { su "$CELERYD_USER" -c "$CELERYD_MULTI $*" }