烧瓶:uWSGI工作者暂时不会重生

问题描述

我的uWsgi Flask应用程序遇到了问题。它具有以下配置:

[uwsgi]
module=app:create_app()
strict = true
single-interpreter = true
need-app = true
die-on-term = true
memory-report = true
vacuum = true
master = true
processes = 5
enable-threads = true

socket = order.sock
chmod-socket = 660
stats = /tmp/statsock

max-requests = 1000                  ; Restart workers after this many requests
max-worker-lifetime = 3600           ; Restart workers after this many seconds
reload-on-RSS = 2048                 ; Restart workers after this much resident memory
worker-reload-mercy = 60             ; How long to wait before forcefully killing workers
harakiri = 60                        ; Forcefully kill workers after 60 seconds

每小时产生一个工人。但是在某些时候,他们只是不会再开始:

Aug 19 23:35:54 web-1 uwsgi[6306]: worker 1 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 2 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 3 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 4 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 5 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 6 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 7 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 8 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 9 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:54 web-1 uwsgi[6306]: worker 10 lifetime reached,it was running for 3601 second(s)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 1 (new pid: 8715)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 2 (new pid: 8716)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 3 (new pid: 8717)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 4 (new pid: 8718)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 5 (new pid: 8719)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 6 (new pid: 8720)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 7 (new pid: 8721)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 8 (new pid: 8722)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 9 (new pid: 8723)
Aug 19 23:35:56 web-1 uwsgi[6306]: Respawned uWsgi worker 10 (new pid: 8724)
Aug 20 00:35:29 web-1 uwsgi[6306]: [2020-08-20 00:35:29,082] INFO in __init__: <class 'app.config.Config'>
Aug 20 00:35:29 web-1 uwsgi[6306]: [2020-08-20 00:35:29,094] INFO in __init__: None
Aug 20 00:35:29 web-1 uwsgi[6306]: [2020-08-20 00:35:29,220] INFO in __init__: Routes are registered
Aug 20 00:35:29 web-1 uwsgi[6306]: [2020-08-20 00:35:29,220] INFO in jobs: Starting products import
Aug 20 00:35:35 web-1 uwsgi[6306]: [2020-08-20 00:35:35,752] INFO in jobs: Product synchronization result: same: 1298,new: 0,modified: 0
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 1 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 2 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 3 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 4 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 5 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 6 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 7 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 8 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 9 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:57 web-1 uwsgi[6306]: worker 10 lifetime reached,it was running for 3601 second(s)
Aug 20 00:35:58 web-1 uwsgi[6306]: Respawned uWsgi worker 2 (new pid: 9090)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 1 (new pid: 9091)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 3 (new pid: 9092)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 4 (new pid: 9093)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 5 (new pid: 9094)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 6 (new pid: 9095)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 7 (new pid: 9096)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 8 (new pid: 9097)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 9 (new pid: 9098)
Aug 20 00:35:59 web-1 uwsgi[6306]: Respawned uWsgi worker 10 (new pid: 9099)
Aug 20 01:35:58 web-1 uwsgi[6306]: worker 2 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 1 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 3 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 4 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 5 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 6 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 7 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 8 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 9 lifetime reached,it was running for 3601 second(s)
Aug 20 01:36:00 web-1 uwsgi[6306]: worker 10 lifetime reached,it was running for 3601 second(s)

为了使应用程序正常运行,我必须重新启动整个应用程序。发生这种行为的原因可能是什么?到目前为止,我还没有发现任何问题。

造成这种情况的唯一原因可能是我用于后台作业的APScheduler。但我不确定它如何干扰工人的重载

解决方法

暂无找到可以解决该程序问题的有效方法,小编努力寻找整理中!

如果你已经找到好的解决方法,欢迎将解决方案带上本链接一起发送给小编。

小编邮箱:dio#foxmail.com (将#修改为@)

相关问答

Selenium Web驱动程序和Java。元素在(x,y)点处不可单击。其...
Python-如何使用点“。” 访问字典成员?
Java 字符串是不可变的。到底是什么意思?
Java中的“ final”关键字如何工作?(我仍然可以修改对象。...
“loop:”在Java代码中。这是什么,为什么要编译?
java.lang.ClassNotFoundException:sun.jdbc.odbc.JdbcOdbc...