WeKnora icon indicating copy to clipboard operation
WeKnora copied to clipboard

[Question]: weknora-docreader循环重启

Open TWO-ICE opened this issue 2 months ago • 6 comments

问题类别

安装和部署

问题描述

日志:确定什么都没改 2025-10-15 11:42:31 2025-10-15 03:42:31,845 INFO success: docreader entered RUNNING state, process has stayed up for > than 5 seconds (startsecs) 2025-10-15 11:42:25 2025-10-15 03:42:25,861 INFO spawned: 'docreader' with pid 6 2025-10-15 11:42:24 2025-10-15 03:42:24,859 INFO supervisord started with pid 1 2025-10-15 11:42:24 2025-10-15 03:42:24,859 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2025-10-15 11:42:24 2025-10-15 03:42:24,859 INFO RPC interface 'supervisor' initialized 2025-10-15 11:42:24 2025-10-15 03:42:24,854 INFO Set uid to user 0 succeeded 2025-10-15 11:39:51 2025-10-15 03:39:51,254 WARN stopped: docreader (terminated by SIGTERM) 2025-10-15 11:39:50 2025-10-15 03:39:50,302 INFO waiting for docreader to die 2025-10-15 11:39:50 2025-10-15 03:39:50,302 WARN received SIGTERM indicating exit request 2025-10-15 11:39:35 2025-10-15 03:39:35,135 INFO success: docreader entered RUNNING state, process has stayed up for > than 5 seconds (startsecs) 2025-10-15 11:39:29 2025-10-15 03:39:29,253 INFO spawned: 'docreader' with pid 7 2025-10-15 11:39:28 2025-10-15 03:39:28,251 INFO supervisord started with pid 1 2025-10-15 11:39:28 2025-10-15 03:39:28,251 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2025-10-15 11:39:28 2025-10-15 03:39:28,251 INFO RPC interface 'supervisor' initialized 2025-10-15 11:39:28 2025-10-15 03:39:28,246 INFO Set uid to user 0 succeeded 2025-10-15 11:39:27 2025-10-15 03:39:27,329 WARN stopped: docreader (terminated by SIGTERM) 2025-10-15 11:39:26 2025-10-15 03:39:26,328 INFO waiting for docreader to die 2025-10-15 11:39:26 2025-10-15 03:39:26,328 WARN received SIGTERM indicating exit request 2025-10-15 11:35:06 2025-10-15 03:35:06,147 INFO success: docreader entered RUNNING state, process has stayed up for > than 5 seconds (startsecs) 2025-10-15 11:35:00 2025-10-15 03:35:00,291 INFO spawned: 'docreader' with pid 7 2025-10-15 11:34:59 2025-10-15 03:34:59,289 INFO supervisord started with pid 1 2025-10-15 11:34:59 2025-10-15 03:34:59,288 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2025-10-15 11:34:59 2025-10-15 03:34:59,288 INFO RPC interface 'supervisor' initialized 2025-10-15 11:34:59 2025-10-15 03:34:59,279 INFO Set uid to user 0 succeeded

背景信息

No response

操作系统

win11

其他环境信息

No response

相关日志


已查找的资源

No response

确认事项

  • [x] 我已经搜索了现有的 issues 和文档
  • [x] 我已经提供了足够的信息来帮助理解问题

TWO-ICE avatar Oct 15 '25 03:10 TWO-ICE

请更新一下最新的代码,现在已经不使用supervisor启动服务了,貌似你的代码比较老旧

lyingbug avatar Oct 20 '25 03:10 lyingbug

咨询一下,您用的是默认的docreader吗? 我这边默认生成一直是unhealthy状态

yaowenjun1988 avatar Oct 20 '25 10:10 yaowenjun1988

请更新一下最新的代码,现在已经不使用supervisor启动服务了,貌似你的代码比较老旧

我已经下载最新的了,部署流程就是复制一份env,改了改env的端口,因为我不想部署ollama,用的docker compose up -d部署的,还是不行

TWO-ICE avatar Oct 21 '25 01:10 TWO-ICE

咨询一下,您用的是默认的docreader吗?我这边默认生成一直是不健康的状态

我的也是,下载最新的代码还是不行,我用的docker compose up -d部署的,只改了env里的的端口,其他的什么都没动

TWO-ICE avatar Oct 21 '25 01:10 TWO-ICE

请更新一下最新的代码,现在已经不使用supervisor启动服务了,貌似你的代码比较老旧

Image我就是这样启动的,就是不行的,不知道什么原因

TWO-ICE avatar Oct 21 '25 02:10 TWO-ICE

我有两台电脑,一台是17年买的intel, 显卡是1060, 另一台是今年的海光,显卡3060。17年这台就一直是unhealthy。今年这台就是好的,日志是一模一样。看了一下,两个cpu也都是支持avx2的,怀疑是显卡问题,但是从日志暂时看不出来。

fwt11 avatar Oct 28 '25 10:10 fwt11