【问题标题】:Gunicorn: worker timeout and worker exiting on all containersGunicorn:工人超时和工人退出所有容器
【发布时间】:2022-01-13 06:03:55
【问题描述】:

关于我的问题的一点背景:
我有以下 Gunicorn 配置文件:gunicorn_cofig.py

pidfile = 'app.pid'
worker_tmp_dir = '/dev/shm'
worker_class = 'gthread'
workers = 1
worker_connections = 1000
timeout = 30
keepalive = 1
threads = 2
proc_name = 'app'
bind = '0.0.0.0:8080'
backlog = 2048
accesslog = '-'
errorlog = '-'

最初,我在 Docker 中运行单个 Flask 应用和 Nginx,而 Gunicorn 从来没有遇到过问题。后来我添加了另一个应用程序并将我的 Nginx 配置为将来自不同子域的请求重定向到不同的端口(例如 mydomain.com -> 端口 81 和 app.mydomain.com -> 端口 5000)(如果我理解正确,因为我将所有子域绑定到来自所有子域的相同 IP(我使用 LetsEncrypt)请求到达端口 443,然后 Nginx 将它们反向代理到相应的端口)。为此,我只是在新应用中复制粘贴了相同的 gunicorn_cofig.py,它运行良好。

现在我添加了 6 个应用程序,并且我在所有应用程序中都使用了相同的配置文件,我收到以下错误:

app1           [2022-01-13 05:30:26 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:9)
app1          | [2022-01-13 05:30:26 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:10)
app1          | [2022-01-13 05:30:26 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:11)
app1          | [2022-01-13 05:30:26 +0000] [11] [INFO] Worker exiting (pid: 11)
app1          | [2022-01-13 05:30:26 +0000] [9] [INFO] Worker exiting (pid: 9)
app1          | [2022-01-13 05:30:26 +0000] [10] [INFO] Worker exiting (pid: 10)
app1          | [2022-01-13 05:30:27 +0000] [1] [WARNING] Worker with pid 9 was terminated due to signal 9
app1          | [2022-01-13 05:30:27 +0000] [1] [WARNING] Worker with pid 11 was terminated due to signal 9
app1          | [2022-01-13 05:30:27 +0000] [12] [INFO] Booting worker with pid: 12
app1          | [2022-01-13 05:30:27 +0000] [1] [WARNING] Worker with pid 10 was terminated due to signal 9
app1         | [2022-01-13 05:30:27 +0000] [13] [INFO] Booting worker with pid: 13
app2         | [2022-01-13 05:30:27 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:9)
app2         | [2022-01-13 05:30:27 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:10)
app2         | [2022-01-13 05:30:27 +0000] [10] [INFO] Worker exiting (pid: 10)
app2         | [2022-01-13 05:30:27 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:11)
app2         | [2022-01-13 05:30:27 +0000] [9] [INFO] Worker exiting (pid: 9)
app1         | [2022-01-13 05:30:27 +0000] [14] [INFO] Booting worker with pid: 14

等等,适用于每个应用程序。

我试图将proc_name = 'app' 更改为不同的值,但同样的事情正在发生。这是我的 docker compose 文件的 sn-p,我在其中运行 Gunicorn 的命令:

m:
    build:
      dockerfile: ./m/Dockerfile 
      context: ../../
    command: gunicorn --bind 0.0.0.0:82 --workers 3 ${M_FLASK_APP}:app
    environment:
      - FLASK_ENV=${FLASK_ENV}
      - PYTHONUNBUFFERED=1
    ports:
      - 82:82
    volumes:
      - ./m/src:/opt/m
  
 p:
    build:
      dockerfile: ./p/Dockerfile 
      context: ../../
    command: gunicorn --bind 0.0.0.0:83 --workers 3 ${P_FLASK_APP}:app
    environment:
      - FLASK_ENV=${FLASK_ENV}
      - PYTHONUNBUFFERED=1
    ports:
      - 83:83
    volumes:
      - ./p/src:/opt/p

谁能指引我正确的方向。是gunicorn配置问题还是docker(因为我运行了6个应用和1个nginx服务器)?

【问题讨论】:

    标签: python docker nginx flask gunicorn


    【解决方案1】:

    我通过升级我的 Compute Engine 实例(我使用的是 Google Cloud)解决了这个问题。以前我有 2 个 CPU 内核和 4GB RAM,并将其更改为 4 个 CPU 内核和 4GB RAM 和 CPU 优化机器。现在我可以在同一个实例上托管超过 6 个应用程序,但成本要高得多。显然,上述错误的原因是硬件限制。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 2014-08-05
      • 2020-07-16
      • 2016-07-27
      • 2014-10-22
      • 2019-08-12
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多