1. 首页
  2. 问答
  3. [whyour/qinglong]突然就无法访问了

[whyour/qinglong]突然就无法访问了

2023-12-21 272 views
8
Qinglong version

dev的最新版

Steps to reproduce

无步骤

What is expected?

莫名其妙就无法访问了，访问提示超时

What is actually happening?

尝试restart docker 无效 尝试ql update 无效 尝试ql check 无效

System Info 
System:
    OS: Linux 4.18 CentOS Stream 8
    CPU: (2) x64 AMD EPYC 7K62 48-Core Processor
    Memory: 1.97 GB / 3.57 GB
    Container: Yes
    Shell: 4.4.20 - /usr/bin/bash
  Binaries:
    Node: 18.18.0 - /usr/local/node-v18.18.0/bin/node
    npm: 10.2.0 - /usr/bin/npm
    pnpm: 8.9.0 - /usr/bin/pnpm
  Browsers:
    Chrome: 119.0.6045.159

pm2 logs:

[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/root/.pm2/pm2.log last 15 lines:
PM2        | 2023-11-30T21:26:16: PM2 log: App [schedule:0] starting in -fork mode-
PM2        | 2023-11-30T21:26:16: PM2 log: App [public:1] starting in -fork mode-
PM2        | 2023-11-30T21:26:27: PM2 log: App [schedule:0] online
PM2        | 2023-11-30T21:26:27: PM2 log: App [public:1] online
PM2        | 2023-11-30T21:26:36: PM2 log: App [panel:2] starting in -fork mode-
PM2        | 2023-11-30T21:26:48: PM2 log: App [panel:2] online

/root/.pm2/logs/schedule-error.log last 15 lines:
/root/.pm2/logs/public-error.log last 15 lines:
/root/.pm2/logs/panel-error.log last 15 lines:
2|panel    | 2023-11-29T22:11:54: Server need close, singal SIGINT

/root/.pm2/logs/schedule-out.log last 15 lines:
0|schedule | 2023-11-29T22:11:54: ✌️ 定时服务启动成功！
0|schedule | 2023-11-30T21:40:11: ✌️ 定时服务启动成功！

/root/.pm2/logs/panel-out.log last 15 lines:
2|panel    | 2023-11-29T22:12:12: ✌️ Dependency Injector loaded
2|panel    | 2023-11-29T22:12:12: ✌️ Express loaded
2|panel    | 2023-11-29T22:12:12: ✌️ init data loaded
2|panel    | 2023-11-29T22:12:12: ✌️ link deps loaded
2|panel    | 2023-11-29T22:12:12: ✌️ init task loaded
2|panel    | 2023-11-29T22:12:12: ✌️ 后端服务启动成功！
2|panel    | 2023-11-30T21:40:13: ✌️ DB loaded
2|panel    | 2023-11-30T21:40:13: ✌️ Init file down
2|panel    | 2023-11-30T21:40:13: ✌️ Sentry loaded
2|panel    | 2023-11-30T21:40:15: ✌️ Dependency Injector loaded
2|panel    | 2023-11-30T21:40:15: ✌️ Express loaded
2|panel    | 2023-11-30T21:40:15: ✌️ init data loaded
2|panel    | 2023-11-30T21:40:15: ✌️ link deps loaded
2|panel    | 2023-11-30T21:40:15: ✌️ init task loaded
2|panel    | 2023-11-30T21:40:15: ✌️ 后端服务启动成功！

/root/.pm2/logs/public-out.log last 15 lines:
1|public   | 2023-11-29T22:11:54: ✌️ Sentry loaded
1|public   | 2023-11-29T22:12:00: ✌️ DB loaded
1|public   | 2023-11-29T22:12:00: ✌️ 公共服务启动成功！
1|public   | 2023-11-30T21:40:11: ✌️ Sentry loaded
1|public   | 2023-11-30T21:40:18: ✌️ DB loaded
1|public   | 2023-11-30T21:40:18: ✌️ 公共服务启动成功！
Any additional comments?

No response

cyxnzb

回答

7
开始执行... 2023-11-30 23:05:17

=====> 开始检测 npm ERR! code EAI_AGAIN npm ERR! syscall getaddrinfo npm ERR! errno EAI_AGAIN npm ERR! request to https://registry.npmmirror.com/pm2 failed, reason: getaddrinfo EAI_AGAIN registry.npmmirror.com

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-11-30T15_05_17_970Z-debug-0.log Writing to /root/.config/pip/pip.conf Lockfile is up to date, resolution step is skipped Already up to date

Done in 1.2s ---> 1. 开始检测配置文件

---> 配置文件检测完成

---> 2. 开始安装青龙依赖

安装 /ql 依赖包...

devDependencies: skipped

@ postinstall /ql max setup 2>/dev/null || true

Done in 1.4s ---> 青龙依赖安装完成

---> 3. 开始安装脚本依赖

安装 /ql/data/scripts 依赖包...

devDependencies: skipped

Done in 624ms ---> 脚本依赖安装完成

---> 1. 复制通知文件

---> 复制一份 /ql/sample/notify.py 为 /ql/data/scripts/notify.py

'/ql/sample/notify.py' -> '/ql/data/scripts/notify.py'

---> 复制一份 /ql/sample/notify.js 为 /ql/data/scripts/sendNotify.js

'/ql/sample/notify.js' -> '/ql/data/scripts/sendNotify.js' ---> 通知文件复制完成

---> 2. 复制nginx配置文件

'/ql/docker/nginx.conf' -> '/etc/nginx/nginx.conf' '/ql/docker/front.conf' -> '/etc/nginx/conf.d/front.conf' ---> 配置文件复制完成

=====> 检测面板

<!DOCTYPE html>

=====> 面板服务启动正常 =====> 检测nginx服务 69 nginx: master process nginx -c /etc/nginx/nginx.conf 71 nginx: worker process 73 nginx: worker process =====> nginx服务正常 ---> pm2日志 2023-11-29T22:12:11: ✌️ DB loaded 2023-11-29T22:12:11: ✌️ Init file down 2023-11-29T22:12:11: ✌️ Sentry loaded 2023-11-29T22:12:12: ✌️ Dependency Injector loaded 2023-11-29T22:12:12: ✌️ Express loaded 2023-11-29T22:12:12: ✌️ init data loaded 2023-11-29T22:12:12: ✌️ link deps loaded 2023-11-29T22:12:12: ✌️ init task loaded 2023-11-29T22:12:12: ✌️ 后端服务启动成功！ 2023-11-30T21:40:13: ✌️ DB loaded 2023-11-30T21:40:13: ✌️ Init file down 2023-11-30T21:40:13: ✌️ Sentry loaded 2023-11-30T21:40:15: ✌️ Dependency Injector loaded 2023-11-30T21:40:15: ✌️ Express loaded 2023-11-30T21:40:15: ✌️ init data loaded 2023-11-30T21:40:15: ✌️ link deps loaded 2023-11-30T21:40:15: ✌️ init task loaded 2023-11-30T21:40:15: ✌️ 后端服务启动成功！ 2023-11-29T22:11:54: Server need close, singal SIGINT =====> 检测后台 {"code":200,"data":{"isInitialized":true,"version":"2.16.5","publishTime":1698580800,"branch":"develop","changeLog":"1. 修复注释或删除环境变量可能无效 2. 修复定时任务详情日志列表样式 ","changeLogLink":"https://t.me/jiao_long/396"}} =====> 后台服务启动正常 [PM2] Applying action reloadProcessId on app [schedule](ids: [ 0 ]) [PM2] Applying action reloadProcessId on app [public](ids: [ 1 ]) [PM2] [schedule](0) ✓ [PM2] Applying action reloadProcessId on app [panel](ids: [ 2 ]) [PM2] [public](1) ✓ [PM2] [panel](2) ✓ ┌────┬─────────────┬─────────────┬─────────┬─────────┬──────────┬────���───┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐ │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │ ├────┼─────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤ │ 2 │ panel │ default │ N/A │ fork │ 20354 │ 2s │ 1 │ online │ 0% │ 125.9mb │ root │ disabled │ │ 1 │ public │ default │ N/A │ fork │ 20278 │ 18s │ 1 │ online │ 0% │ 80.4mb │ root │ disabled │ │ 0 │ schedule │ default │ N/A │ fork │ 20277 │ 18s │ 1 │ online │ 1.8% │ 76.3mb │ root │ disabled │ └────┴─────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘ =====> 检测结束 ## 执行结束... 2023-11-30 23:09:58 耗时 281 秒　　　　　

cyxnzb

3

你的容器内是不是访问不了外网了，你的 dns 好像有问题

whyour

8

对，好像是这样，ql update不了，应该怎么解决呢

cyxnzb

2

看你 centos 能不能访问外网，不能的话排查下你的机器为什么访问不了外网了

whyour

1

外网的话宿主机是可以正常访问的，但是容器的话不太清楚啥情况，回头白天我再看看，谢谢啦

cyxnzb

5

config.sh 里的 npmMirror 换一个试试

whyour

1

感谢，我试了重启了宿主机，恢复正常了，虽然不知道为什么出现了故障哈哈

cyxnzb

7

感谢，我试了重启了宿主机，恢复正常了，虽然不知道为什么出现了故障哈哈

cyxnzb

 相关问题