强制升级后出错 无法启动。一直在启动中 error报错

[cnzh10000]

Clear and concise description of the problem

开始执行... 2024-03-22 18:39:58

=====> 开始检测
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'pnpm@8.3.1',
npm WARN EBADENGINE required: { node: '>=16.14' },
npm WARN EBADENGINE current: { node: 'v16.13.1', npm: '8.1.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'tsx@4.7.1',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.1', npm: '8.1.2' }
npm WARN EBADENGINE }
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm ERR! code EEXIST
npm ERR! path /usr/local/bin/pm2
npm ERR! EEXIST: file already exists
npm ERR! File exists: /usr/local/bin/pm2
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2024-03-22T10_40_30_159Z-debug.log
检测到旧的db目录，拷贝到data目录...

检测到旧的scripts目录，拷贝到data目录...

检测到旧的log目录，拷贝到data目录...

检测到旧的config目录，拷贝到data目录...

---> 1. 开始检测配置文件

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

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

安装 /ql 依赖包...

Packages: -1273

devDependencies:

• @ant-design/icons 4.8.2
• @ant-design/pro-layout 6.38.22
• @monaco-editor/react 4.2.1
• @react-hook/resize-observer 1.2.6
• @sentry/react 7.107.0
• @types/body-parser 1.19.5
• @types/cors 2.8.17
• @types/cross-spawn 6.0.6
• @types/express 4.17.21
• @types/express-jwt 6.0.4
• @types/file-saver 2.0.2
• @types/js-yaml 4.0.9
• @types/jsonwebtoken 8.5.9
• @types/lodash 4.17.0
• @types/multer 1.4.11
• @types/nedb 1.8.16
• @types/node 17.0.45
• @types/node-schedule 1.3.2
• @types/nodemailer 6.4.14
• @types/qrcode.react 1.0.5
• @types/react 18.2.67
• @types/react-copy-to-clipboard 5.0.7
• @types/react-dom 18.2.22
• @types/request-ip 0.0.41
• @types/serve-handler 6.1.4
• @types/sockjs 0.3.36
• @types/sockjs-client 1.5.4
• @types/tar 6.1.11
• @types/uuid 8.3.4
• @uiw/codemirror-extensions-langs 4.21.24
• @uiw/react-codemirror 4.21.24
• @umijs/max 4.1.5
• @umijs/ssr-darkreader 4.9.45
• ahooks 3.7.10
• ansi-to-react 6.1.6
• antd 4.24.16
• antd-img-crop 4.21.0
• axios 1.6.8
• compression-webpack-plugin 9.2.0
• concurrently 7.6.0
• file-saver 2.0.2
• lint-staged 13.3.0
• monaco-editor 0.33.0
• nodemon 3.1.0
• prettier 2.8.8
• pretty-bytes 6.1.1
• qiniu 7.11.1
• qrcode.react 1.0.1
• query-string 7.1.3
• rc-tween-one 3.0.6
• rc-virtual-list 3.5.3
• react 18.2.0
• react-copy-to-clipboard 5.1.0
• react-diff-viewer 3.1.1
• react-dnd 14.0.5
• react-dnd-html5-backend 14.1.0
• react-dom 18.2.0
• react-hotkeys-hook 4.5.0
• react-intl-universal 2.11.1
• react-split-pane 0.1.92
• sockjs-client 1.6.1
• ts-node 10.9.2
• ts-proto 1.169.1
• tslib 2.6.2
• tsx 3.14.0
• typescript 5.2.2
• vh-check 2.0.5
• virtualizedtableforantd4 1.3.0
• webpack 5.91.0
• yorkie 2.0.0

---> 青龙依赖安装完成

---> 脚本依赖安装完成

---> 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'
---> 配置文件复制完成

=====> 检测面板

<script src="./api/env.js"></script> <script src="https://gw.alipayobjects.com/os/lib/react/18.2.0/umd/react.production.min.js"></script> <script src="https://gw.alipayobjects.com/os/lib/react-dom/18.2.0/umd/react-dom.production.min.js"></script>

<script src="./umi.91474f0f.js"></script>

=====> 面板服务启动正常

ps: bad -o argument 'command', supported arguments: user,group,comm,args,pid,ppid,pgid,etime,nice,rgroup,ruser,time,tty,vsz,sid,stat,rss
=====> 检测nginx服务

=====> nginx服务异常，重新启动nginx

nginx: [emerg] bind() to 0.0.0.0:5700 failed (98: Address in use)
nginx: [emerg] bind() to [::]:5700 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:5700 failed (98: Address in use)
nginx: [emerg] bind() to [::]:5700 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:5700 failed (98: Address in use)
nginx: [emerg] bind() to [::]:5700 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:5700 failed (98: Address in use)
nginx: [emerg] bind() to [::]:5700 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:5700 failed (98: Address in use)
nginx: [emerg] bind() to [::]:5700 failed (98: Address in use)
nginx: [emerg] still could not bind()
---> pm2日志
2024-03-21T22:55:16: ✌️ DB loaded
2024-03-21T22:55:16: ✌️ Init file down
2024-03-21T22:55:16: ✌️ Sentry loaded
2024-03-21T22:55:18: ✌️ Dependency Injector loaded
2024-03-21T22:55:18: ✌️ Express loaded
2024-03-21T22:55:19: ✌️ init data loaded
2024-03-21T22:55:19: ✌️ link deps loaded
2024-03-21T22:55:19: ✌️ init task loaded
2024-03-22T17:16:13: ✌️ DB loaded
2024-03-22T17:16:13: ✌️ Init file down
2024-03-22T17:16:14: ✌️ Sentry loaded
2024-03-22T17:16:17: ✌️ Dependency Injector loaded
2024-03-22T17:16:17: ✌️ Express loaded
2024-03-22T17:16:18: ✌️ init data loaded
2024-03-22T17:16:19: ✌️ link deps loaded
2024-03-22T17:16:19: ✌️ init task loaded
2024-03-21T22:55:19: RangeError: options.port should be >= 0 and < 65536. Received NaN.
2024-03-21T22:55:19: at new NodeError (node:internal/errors:371:5)
2024-03-21T22:55:19: at validatePort (node:internal/validators:216:11)
2024-03-21T22:55:19: at Server.listen (node:net:1461:5)
2024-03-21T22:55:19: at Function.listen (/ql/node_modules/.pnpm/express@4.18.3/node_modules/express/lib/application.js:635:24)
2024-03-21T22:55:19: at startServer (/ql/back/app.ts:18:6) {
2024-03-21T22:55:19: code: 'ERR_SOCKET_BAD_PORT'
2024-03-21T22:55:19: }
2024-03-21T22:55:19: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-03-21T22:55:19: RangeError: options.port should be >= 0 and < 65536. Received NaN.
2024-03-21T22:55:19: at new NodeError (node:internal/errors:371:5)
2024-03-21T22:55:19: at validatePort (node:internal/validators:216:11)
2024-03-21T22:55:19: at Server.listen (node:net:1461:5)
2024-03-21T22:55:19: at Function.listen (/ql/node_modules/.pnpm/express@4.18.3/node_modules/express/lib/application.js:635:24)
2024-03-21T22:55:19: at startServer (/ql/back/app.ts:18:6)
2024-03-22T17:16:19: RangeError: options.port should be >= 0 and < 65536. Received NaN.
2024-03-22T17:16:19: at new NodeError (node:internal/errors:371:5)
2024-03-22T17:16:19: at validatePort (node:internal/validators:216:11)
2024-03-22T17:16:19: at Server.listen (node:net:1461:5)
2024-03-22T17:16:19: at Function.listen (/ql/node_modules/.pnpm/express@4.18.3/node_modules/express/lib/application.js:635:24)
2024-03-22T17:16:19: at startServer (/ql/back/app.ts:18:6) {
2024-03-22T17:16:19: code: 'ERR_SOCKET_BAD_PORT'
2024-03-22T17:16:19: }
2024-03-22T17:16:19: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-03-22T17:16:19: RangeError: options.port should be >= 0 and < 65536. Received NaN.
2024-03-22T17:16:19: at new NodeError (node:internal/errors:371:5)
2024-03-22T17:16:19: at validatePort (node:internal/validators:216:11)
2024-03-22T17:16:19: at Server.listen (node:net:1461:5)
2024-03-22T17:16:19: at Function.listen (/ql/node_modules/.pnpm/express@4.18.3/node_modules/express/lib/application.js:635:24)
2024-03-22T17:16:19: at startServer (/ql/back/app.ts:18:6)

=====> 检测后台

[PM2] Applying action reloadProcessId on app [public](ids: [ 1 ])
[PM2] Applying action reloadProcessId on app [schedule](ids: [ 0 ])
[PM2] schedule ✓
[PM2] Applying action reloadProcessId on app [panel](ids: [ 2 ])
[PM2] public ✓
[PM2] panel ✓
┌─────┬─────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼─────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 2 │ panel │ default │ N/A │ fork │ 31748 │ 10s │ 1 │ online │ 0% │ 91.0mb │ root │ disabled │
│ 1 │ public │ default │ N/A │ fork │ 32078 │ 0 │ 7367 │ launching │ 0% │ 0b │ root │ disabled │
│ 0 │ schedule │ default │ N/A │ fork │ 31711 │ 12s │ 1 │ online │ 1.6% │ 68.0mb │ root │ disabled │
└─────┴─────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

=====> 检测结束

执行结束... 2024-03-22 18:41:33 耗时 95 秒　

Suggested solution

希望能协助解决

Alternative

No response

Additional context

No response

Validations

• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.