【问题标题】:How to configure Celery loglevel in Supervisord如何在 Supervisord 中配置 Celery 日志级别
【发布时间】:2015-07-25 03:46:05
【问题描述】:

我用 supervisord 配置了 celery-worker 和 celery-beat,除了日志记录的一些小问题外,两者都运行良好。

这里是 celery-worker.conf,我将日志级别指定为 WARNING

[program:celery-worker]
command=celery -A apps.crawler.celery:app worker --loglevel=WARNING
directory=/home/django/django_project/django_project
user=django
numprocs=1
stdout_logfile=/home/django/django_project/django_project/logs/celery-worker.log
stderr_logfile=/home/django/django_project/django_project/logs/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 = 10

; 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

但是,celery-worker 总是以 loglevel=INFO 启动

ps -ef |grep celery-worker
django    2422  6909  0 01:13 ?        00:00:03 /usr/bin/python /usr/local/bin/celery -A apps.crawler.celer :app worker --concurrency=1 --loglevel=INFO
django    2427  2422 10 01:13 ?        00:03:04 /usr/bin/python /usr/local/bin/celery -A apps.crawler.celer :app worker --concurrency=1 --loglevel=INFO

如何将日志级别更改为 WARNING?

【问题讨论】:

  • 我一直在努力解决完全相同的问题 - 我怀疑我正在使用的 celery 版本 (3.1.18) 中存在错误
  • 重启服务器后,问题神秘消失。或许你也可以试试

标签: django logging celery supervisord


【解决方案1】:

我遇到了同样的问题,并通过重新启动 supervisord 解决了它。 新配置生效前需要重启 Supervisord。

【讨论】:

    猜你喜欢
    • 2015-06-04
    • 2015-10-11
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2020-04-02
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多