Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

青龙改用host模式怎么弄进不去了 #2679

Open
mmeiwenlong opened this issue Mar 14, 2025 · 2 comments
Open

青龙改用host模式怎么弄进不去了 #2679

mmeiwenlong opened this issue Mar 14, 2025 · 2 comments

Comments

@mmeiwenlong
Copy link

Qinglong version

2.18.1

Steps to reproduce

Image

What is expected?

docker run -dit
-v /root/ql5/data:/ql/data
-e QlBaseUrl="/root/ql5"
-e QlPort="5701"
--name ql5
--hostname ql5
--net=host
--restart unless-stopped
whyour/qinglong:latest

What is actually happening?

进不去面版

System Info

======================1. 检测配置文件========================

'/ql/docker/nginx.conf' -> '/etc/nginx/nginx.conf'
'/ql/docker/front.conf' -> '/etc/nginx/conf.d/front.conf'
======================2. 安装依赖========================

======================3. 启动nginx========================

nginx启动成功...

======================4. 启动pm2服务========================

[PM2][WARN] Applications update not running, starting...
[PM2][WARN] App update has option 'wait_ready' set, waiting for app to be ready...
[PM2] App [update] launched (1 instances)
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0  │ update             │ fork     │ 9    │ errored   │ 0%       │ 0b       │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
[PM2][WARN] Applications schedule, public, panel not running, starting...
[PM2][WARN] App schedule has option 'wait_ready' set, waiting for app to be ready...
[PM2][WARN] App public has option 'wait_ready' set, waiting for app to be ready...
[PM2] App [public] launched (1 instances)
[PM2][WARN] App panel has option 'wait_ready' set, waiting for app to be ready...
[PM2] App [schedule] launched (1 instances)
======================1. 检测配置文件========================

'/ql/docker/nginx.conf' -> '/etc/nginx/nginx.conf'
'/ql/docker/front.conf' -> '/etc/nginx/conf.d/front.conf'
======================2. 安装依赖========================

======================3. 启动nginx========================

nginx启动成功...

======================4. 启动pm2服务========================

[PM2][WARN] Applications update not running, starting...
[PM2][WARN] App update has option 'wait_ready' set, waiting for app to be ready...
[PM2] App [update] launched (1 instances)
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0  │ update             │ fork     │ 9    │ errored   │ 0%       │ 0b       │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
[PM2][WARN] Applications schedule, public, panel not running, starting...
[PM2][WARN] App schedule has option 'wait_ready' set, waiting for app to be ready...
[PM2][WARN] App public has option 'wait_ready' set, waiting for app to be ready...
[PM2] App [public] launched (1 instances)
[PM2][WARN] App panel has option 'wait_ready' set, waiting for app to be ready...
[PM2] App [schedule] launched (1 instances)
[PM2] App [panel] launched (1 instances)
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 3  │ panel              │ fork     │ 1    │ launching │ 0%       │ 0b       │
│ 2  │ public             │ fork     │ 0    │ online    │ 0%       │ 84.9mb   │
│ 1  │ schedule           │ fork     │ 3    │ launching │ 0%       │ 0b       │
│ 0  │ update             │ fork     │ 9    │ errored   │ 0%       │ 0b       │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
############################################################

容器启动成功...
############################################################

crond[334]: crond (busybox 1.37.0) started, log level 8

Any additional comments?

No response
@mmeiwenlong
Copy link
Author

docker run -dit
-v /root/ql5/data:/ql/data
-e QlPort="5550"
--name ql5
--hostname ql5
--net=host
--restart unless-stopped
whyour/qinglong:latest
这样装他有提示Received RST_STREAM with code 2 triggered by internal client error: Protocol error

root@ql5:/ql $ pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/root/.pm2/pm2.log last 15 lines:
PM2 | 2025-03-14T14:34:45: PM2 log: App [schedule:1] exited with code [0] via signal [SIGINT]
PM2 | 2025-03-14T14:34:45: PM2 log: App [schedule:1] starting in -fork mode-
PM2 | 2025-03-14T14:34:45: PM2 log: App [schedule:1] online
PM2 | 2025-03-14T14:34:48: PM2 log: App [schedule:1] exited with code [0] via signal [SIGINT]
PM2 | 2025-03-14T14:34:48: PM2 log: App [schedule:1] starting in -fork mode-
PM2 | 2025-03-14T14:34:48: PM2 log: App [panel:3] online
PM2 | 2025-03-14T14:34:48: PM2 log: App [schedule:1] online
PM2 | 2025-03-14T14:34:50: PM2 log: App [panel:3] exited with code [0] via signal [SIGINT]
PM2 | 2025-03-14T14:34:50: PM2 log: App [panel:3] starting in -fork mode-
PM2 | 2025-03-14T14:34:51: PM2 log: App [schedule:1] exited with code [0] via signal [SIGINT]
PM2 | 2025-03-14T14:34:51: PM2 log: App [schedule:1] starting in -fork mode-
PM2 | 2025-03-14T14:34:51: PM2 log: App [schedule:1] online
PM2 | 2025-03-14T14:34:54: PM2 log: App [schedule:1] exited with code [0] via signal [SIGINT]
PM2 | 2025-03-14T14:34:54: PM2 log: App [schedule:1] starting in -fork mode-
PM2 | 2025-03-14T14:34:54: PM2 log: App [panel:3] online

/root/.pm2/logs/update-out.log last 15 lines:
/root/.pm2/logs/update-error.log last 15 lines:
/root/.pm2/logs/schedule-out.log last 15 lines:
/root/.pm2/logs/public-error.log last 15 lines:
/root/.pm2/logs/public-out.log last 15 lines:
2|public | 2025-03-14T14:29:34: ✌️ DB loaded
2|public | 2025-03-14T14:29:34: ✌️ 公共服务启动成功！

/root/.pm2/logs/panel-out.log last 15 lines:
3|panel | 2025-03-14T14:34:26: ✌️ DB loaded
3|panel | 2025-03-14T14:34:26: ✌️ Init file down
3|panel | 2025-03-14T14:34:26: ✌️ Dependency loaded
3|panel | 2025-03-14T14:34:32: ✌️ DB loaded
3|panel | 2025-03-14T14:34:32: ✌️ Init file down
3|panel | 2025-03-14T14:34:33: ✌️ Dependency loaded
3|panel | 2025-03-14T14:34:38: ✌️ DB loaded
3|panel | 2025-03-14T14:34:38: ✌️ Init file down
3|panel | 2025-03-14T14:34:39: ✌️ Dependency loaded
3|panel | 2025-03-14T14:34:45: ✌️ DB loaded
3|panel | 2025-03-14T14:34:45: ✌️ Init file down
3|panel | 2025-03-14T14:34:45: ✌️ Dependency loaded
3|panel | 2025-03-14T14:34:51: ✌️ DB loaded
3|panel | 2025-03-14T14:34:51: ✌️ Init file down
3|panel | 2025-03-14T14:34:51: ✌️ Dependency loaded

/root/.pm2/logs/panel-error.log last 15 lines:
3|panel | 2025-03-14T14:34:51: at processTicksAndRejections (node:internal/process/task_queues:85:11)
3|panel | 2025-03-14T14:34:51: for call at
3|panel | 2025-03-14T14:34:51: at ServiceClientImpl.makeUnaryRequest (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client.ts:325:42)
3|panel | 2025-03-14T14:34:51: at ServiceClientImpl.addCron (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/make-client.ts:189:15)
3|panel | 2025-03-14T14:34:51: at /ql/back/schedule/client.ts:20:19
3|panel | 2025-03-14T14:34:51: at new Promise ()
3|panel | 2025-03-14T14:34:51: at Client.addCron (/ql/back/schedule/client.ts:19:12)
3|panel | 2025-03-14T14:34:51: at CronService.autosave_crontab (/ql/back/services/cron.ts:658:22)
3|panel | 2025-03-14T14:34:51: at exports.default (/ql/back/loaders/initData.ts:208:3)
3|panel | 2025-03-14T14:34:51: at Object.exports.default (/ql/back/loaders/app.ts:14:3)
3|panel | 2025-03-14T14:34:51: at startServer (/ql/back/app.ts:13:3) {
3|panel | 2025-03-14T14:34:51: code: 13,
3|panel | 2025-03-14T14:34:51: details: 'Received RST_STREAM with code 2 triggered by internal client error: Protocol error',
3|panel | 2025-03-14T14:34:51: metadata: Metadata { internalRepr: Map(0) {}, options: {} }
3|panel | 2025-03-14T14:34:51: }

/root/.pm2/logs/schedule-error.log last 15 lines:
1|schedule | 2025-03-14T14:34:45: E No address added out of total 1 resolved
1|schedule | 2025-03-14T14:34:45: Error: No address added out of total 1 resolved errors: [listen EADDRINUSE: address already in use 0.0.0.0:5500]
1|schedule | 2025-03-14T14:34:45: at Server.bindAddressList (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:751:13)
1|schedule | 2025-03-14T14:34:45: at processTicksAndRejections (node:internal/process/task_queues:105:5)
1|schedule | 2025-03-14T14:34:45: at Server.bindPort (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:794:24)
1|schedule | 2025-03-14T14:34:48: E No address added out of total 1 resolved
1|schedule | 2025-03-14T14:34:48: Error: No address added out of total 1 resolved errors: [listen EADDRINUSE: address already in use 0.0.0.0:5500]
1|schedule | 2025-03-14T14:34:48: at Server.bindAddressList (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:751:13)
1|schedule | 2025-03-14T14:34:48: at processTicksAndRejections (node:internal/process/task_queues:105:5)
1|schedule | 2025-03-14T14:34:48: at Server.bindPort (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:794:24)
1|schedule | 2025-03-14T14:34:51: E No address added out of total 1 resolved
1|schedule | 2025-03-14T14:34:51: Error: No address added out of total 1 resolved errors: [listen EADDRINUSE: address already in use 0.0.0.0:5500]
1|schedule | 2025-03-14T14:34:51: at Server.bindAddressList (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:751:13)
1|schedule | 2025-03-14T14:34:51: at processTicksAndRejections (node:internal/process/task_queues:105:5)
1|schedule | 2025-03-14T14:34:51: at Server.bindPort (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:794:24)

1|schedule | 2025-03-14T14:34:54: E No address added out of total 1 resolved
1|schedule | 2025-03-14T14:34:54: Error: No address added out of total 1 resolved errors: [listen EADDRINUSE: address already in use 0.0.0.0:5500]
1|schedule | 2025-03-14T14:34:54: at Server.bindAddressList (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:751:13)
1|schedule | 2025-03-14T14:34:54: at processTicksAndRejections (node:internal/process/task_queues:105:5)
1|schedule | 2025-03-14T14:34:54: at Server.bindPort (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:794:24)
PM2 | App [schedule:1] online
PM2 | App [panel:3] exited with code [0] via signal [SIGINT]
PM2 | App [panel:3] starting in -fork mode-
3|panel | 2025-03-14T14:34:57: ✌️ DB loaded
3|panel | 2025-03-14T14:34:57: ✌️ Init file down
PM2 | App [schedule:1] exited with code [0] via signal [SIGINT]
PM2 | App [schedule:1] starting in -fork mode-
3|panel | 2025-03-14T14:34:57: ✌️ Dependency loaded
3|panel | 2025-03-14T14:34:57: Error: 13 INTERNAL: Received RST_STREAM with code 2 triggered by internal client error: Protocol error
3|panel | 2025-03-14T14:34:57: at callErrorFromStatus (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/call.ts:82:17)
3|panel | 2025-03-14T14:34:57: at Object.onReceiveStatus (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client.ts:360:55)
3|panel | 2025-03-14T14:34:57: at Object.onReceiveStatus (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client-interceptors.ts:458:34)
3|panel | 2025-03-14T14:34:57: at Object.onReceiveStatus (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client-interceptors.ts:419:48)
3|panel | 2025-03-14T14:34:57: at /ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/resolving-call.ts:163:24
3|panel | 2025-03-14T14:34:57: at processTicksAndRejections (node:internal/process/task_queues:85:11)
3|panel | 2025-03-14T14:34:57: for call at
3|panel | 2025-03-14T14:34:57: at ServiceClientImpl.makeUnaryRequest (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client.ts:325:42)
3|panel | 2025-03-14T14:34:57: at ServiceClientImpl.addCron (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/make-client.ts:189:15)
3|panel | 2025-03-14T14:34:57: at /ql/back/schedule/client.ts:20:19
3|panel | 2025-03-14T14:34:57: at new Promise ()
3|panel | 2025-03-14T14:34:57: at Client.addCron (/ql/back/schedule/client.ts:19:12)
3|panel | 2025-03-14T14:34:57: at CronService.autosave_crontab (/ql/back/services/cron.ts:658:22)
3|panel | 2025-03-14T14:34:57: at exports.default (/ql/back/loaders/initData.ts:208:3)
3|panel | 2025-03-14T14:34:57: at Object.exports.default (/ql/back/loaders/app.ts:14:3)
3|panel | 2025-03-14T14:34:57: at startServer (/ql/back/app.ts:13:3) {
3|panel | 2025-03-14T14:34:57: code: 13,
3|panel | 2025-03-14T14:34:57: details: 'Received RST_STREAM with code 2 triggered by internal client error: Protocol error',
3|panel | 2025-03-14T14:34:57: metadata: Metadata { internalRepr: Map(0) {}, options: {} }
3|panel | 2025-03-14T14:34:57: }
1|schedule | 2025-03-14T14:34:57: E No address added out of total 1 resolved
1|schedule | 2025-03-14T14:34:57: Error: No address added out of total 1 resolved errors: [listen EADDRINUSE: address already in use 0.0.0.0:5500]
1|schedule | 2025-03-14T14:34:57: at Server.bindAddressList (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:751:13)
1|schedule | 2025-03-14T14:34:57: at processTicksAndRejections (node:internal/process/task_queues:105:5)
1|schedule | 2025-03-14T14:34:57: at Server.bindPort (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:794:24)
PM2 | App [schedule:1] online
PM2 | App [schedule:1] exited with code [0] via signal [SIGINT]
PM2 | App [schedule:1] starting in -fork mode-
PM2 | App [panel:3] online
1|schedule | 2025-03-14T14:35:01: E No address added out of total 1 resolved
1|schedule | 2025-03-14T14:35:01: Error: No address added out of total 1 resolved errors: [listen EADDRINUSE: address already in use 0.0.0.0:5500]
1|schedule | 2025-03-14T14:35:01: at Server.bindAddressList (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:751:13)
1|schedule | 2025-03-14T14:35:01: at processTicksAndRejections (node:internal/process/task_queues:105:5)
1|schedule | 2025-03-14T14:35:01: at Server.bindPort (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:794:24)
PM2 | App [schedule:1] online
PM2 | App [panel:3] exited with code [0] via signal [SIGINT]
PM2 | App [panel:3] starting in -fork mode-
3|panel | 2025-03-14T14:35:03: ✌️ DB loaded
3|panel | 2025-03-14T14:35:03: ✌️ Init file down
3|panel | 2025-03-14T14:35:03: ✌️ Dependency loaded
PM2 | App [schedule:1] exited with code [0] via signal [SIGINT]
PM2 | App [schedule:1] starting in -fork mode-
3|panel | 2025-03-14T14:35:03: Error: 13 INTERNAL: Received RST_STREAM with code 2 triggered by internal client error: Protocol error
3|panel | 2025-03-14T14:35:03: at callErrorFromStatus (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/call.ts:82:17)
3|panel | 2025-03-14T14:35:03: at Object.onReceiveStatus (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client.ts:360:55)
3|panel | 2025-03-14T14:35:03: at Object.onReceiveStatus (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client-interceptors.ts:458:34)
3|panel | 2025-03-14T14:35:03: at Object.onReceiveStatus (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client-interceptors.ts:419:48)
3|panel | 2025-03-14T14:35:03: at /ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/resolving-call.ts:163:24
3|panel | 2025-03-14T14:35:03: at processTicksAndRejections (node:internal/process/task_queues:85:11)
3|panel | 2025-03-14T14:35:03: for call at
3|panel | 2025-03-14T14:35:03: at ServiceClientImpl.makeUnaryRequest (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/client.ts:325:42)
3|panel | 2025-03-14T14:35:03: at ServiceClientImpl.addCron (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/make-client.ts:189:15)
3|panel | 2025-03-14T14:35:03: at /ql/back/schedule/client.ts:20:19
3|panel | 2025-03-14T14:35:03: at new Promise ()
3|panel | 2025-03-14T14:35:03: at Client.addCron (/ql/back/schedule/client.ts:19:12)
3|panel | 2025-03-14T14:35:03: at CronService.autosave_crontab (/ql/back/services/cron.ts:658:22)
3|panel | 2025-03-14T14:35:03: at exports.default (/ql/back/loaders/initData.ts:208:3)
3|panel | 2025-03-14T14:35:03: at Object.exports.default (/ql/back/loaders/app.ts:14:3)
3|panel | 2025-03-14T14:35:03: at startServer (/ql/back/app.ts:13:3) {
3|panel | 2025-03-14T14:35:03: code: 13,
3|panel | 2025-03-14T14:35:03: details: 'Received RST_STREAM with code 2 triggered by internal client error: Protocol error',
3|panel | 2025-03-14T14:35:03: metadata: Metadata { internalRepr: Map(0) {}, options: {} }
3|panel | 2025-03-14T14:35:03: }
1|schedule | 2025-03-14T14:35:04: E No address added out of total 1 resolved
1|schedule | 2025-03-14T14:35:04: Error: No address added out of total 1 resolved errors: [listen EADDRINUSE: address already in use 0.0.0.0:5500]
1|schedule | 2025-03-14T14:35:04: at Server.bindAddressList (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:751:13)
1|schedule | 2025-03-14T14:35:04: at processTicksAndRejections (node:internal/process/task_queues:105:5)
1|schedule | 2025-03-14T14:35:04: at Server.bindPort (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:794:24)
PM2 | App [schedule:1] online
PM2 | App [schedule:1] exited with code [0] via signal [SIGINT]
PM2 | App [schedule:1] starting in -fork mode-
PM2 | App [panel:3] online
1|schedule | 2025-03-14T14:35:07: E No address added out of total 1 resolved
1|schedule | 2025-03-14T14:35:07: Error: No address added out of total 1 resolved errors: [listen EADDRINUSE: address already in use 0.0.0.0:5500]
1|schedule | 2025-03-14T14:35:07: at Server.bindAddressList (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:751:13)
1|schedule | 2025-03-14T14:35:07: at processTicksAndRejections (node:internal/process/task_queues:105:5)
1|schedule | 2025-03-14T14:35:07: at Server.bindPort (/ql/node_modules/.pnpm/@grpc+grpc-js@1.12.3/node_modules/@grpc/grpc-js/src/server.ts:794:24)
PM2 | App [schedule:1] online
PM2 | App [panel:3] exited with code [0] via signal [SIGINT]

@whyour
Copy link
Owner

whyour commented Mar 14, 2025

不设置前缀 不需要参数 QlBaseUrl ， host 模式端口不能重复，建议使用非 host 模式

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@whyour @mmeiwenlong