search

fscarmen2 / Argo-Nezha-Service-Container

Nezha server over Argo tunnel 使用 Argo 隧道的哪吒服务端
675 stars 408 forks source link

fly.io部署后均显示已离线 #27

Closed DullJZ closed 1 year ago

DullJZ commented 1 year ago

如图，日志看似均无问题 image 但有实时连接已建立的弹窗 环境变量均按照文档配置正确 gRPC开关已打开

疑问1

按照文档，argo tunnel应该不支持gRPC才对 image

疑问2

请输入选择 [0-13]: 9
> 修改Agent配置
请先在管理面板上添加Agent，记录下密钥
请输入一个解析到面板所在IP的域名（不可套CDN）:

脚本显示不可套CDN，argo的CNAME为何需要点亮小云朵

日志

容器端 ```bash 2023-08-13T12:12:14.371 runner[1781912f515d89] hkg [info] Pulling container image registry.fly.io/nezha-dulljz:deployment-01H7QCYQ7BEMVZ4TQC7QSPA6BP 2023-08-13T12:12:15.140 runner[1781912f515d89] hkg [info] Successfully prepared image registry.fly.io/nezha-dulljz:deployment-01H7QCYQ7BEMVZ4TQC7QSPA6BP (769.640673ms) 2023-08-13T12:12:15.155 runner[1781912f515d89] hkg [info] Setting up volume 'nz_data' 2023-08-13T12:12:15.155 runner[1781912f515d89] hkg [info] Opening encrypted volume 2023-08-13T12:12:16.994 runner[1781912f515d89] hkg [info] Configuring firecracker 2023-08-13T12:12:17.249 app[1781912f515d89] hkg [info] INFO Sending signal SIGINT to main child process w/ PID 263 2023-08-13T12:12:22.305 app[1781912f515d89] hkg [info] INFO Sending signal SIGTERM to main child process w/ PID 263 2023-08-13T12:12:23.087 app[1781912f515d89] hkg [info] INFO Main child exited with signal (with signal 'SIGTERM', core dumped? false) 2023-08-13T12:12:23.087 app[1781912f515d89] hkg [info] INFO Starting clean up. 2023-08-13T12:12:23.088 app[1781912f515d89] hkg [info] INFO Umounting /dev/vdb from /dashboard/data 2023-08-13T12:12:23.089 app[1781912f515d89] hkg [info] ERROR error umounting /dashboard/data: EBUSY: Device or resource busy, retrying in a bit 2023-08-13T12:12:23.838 app[1781912f515d89] hkg [info] ERROR error umounting /dashboard/data: EBUSY: Device or resource busy, retrying in a bit 2023-08-13T12:12:24.589 app[1781912f515d89] hkg [info] ERROR error umounting /dashboard/data: EBUSY: Device or resource busy, retrying in a bit 2023-08-13T12:12:25.340 app[1781912f515d89] hkg [info] ERROR error umounting /dashboard/data: EBUSY: Device or resource busy, retrying in a bit 2023-08-13T12:12:26.100 app[1781912f515d89] hkg [info] 2023-08-13 20:12:26,096 INFO exited: agent (terminated by SIGTERM; not expected) 2023-08-13T12:12:26.100 app[1781912f515d89] hkg [info] 2023-08-13 20:12:26,096 WARN received SIGTERM indicating exit request 2023-08-13T12:12:26.100 app[1781912f515d89] hkg [info] 2023-08-13 20:12:26,096 INFO waiting for argo, nezha, nginx to die 2023-08-13T12:12:26.101 app[1781912f515d89] hkg [info] WARN hallpass exited, pid: 264, status: signal: 15 (SIGTERM) 2023-08-13T12:12:26.109 app[1781912f515d89] hkg [info] 2023-08-13 20:12:26,106 INFO exited: argo (exit status 0; expected) 2023-08-13T12:12:26.109 app[1781912f515d89] hkg [info] 2023-08-13 20:12:26,106 INFO stopped: nginx (exit status 0) 2023-08-13T12:12:26.109 app[1781912f515d89] hkg [info] 2023-08-13 20:12:26,106 INFO exited: nezha (exit status 0; expected) 2023-08-13T12:12:26.120 app[1781912f515d89] hkg [info] 2023/08/13 20:12:26 listening on [fdaa:2:a79:a7b:7f07:dc3d:fed3:2]:22 (DNS: [fdaa::3]:53) 2023-08-13T12:12:27.101 app[1781912f515d89] hkg [info] [ 382.742486] reboot: Restarting system 2023-08-13T12:12:27.447 app[1781912f515d89] hkg [info] [ 0.036235] PCI: Fatal: No config space access function found 2023-08-13T12:12:27.667 app[1781912f515d89] hkg [info] INFO Starting init (commit: b437b5b)... 2023-08-13T12:12:27.688 app[1781912f515d89] hkg [info] INFO Mounting /dev/vdb at /dashboard/data w/ uid: 0, gid: 0 and chmod 0755 2023-08-13T12:12:27.690 app[1781912f515d89] hkg [info] INFO Resized /dashboard/data to 1069547520 bytes 2023-08-13T12:12:27.691 app[1781912f515d89] hkg [info] INFO Preparing to run: `./entrypoint.sh` as root 2023-08-13T12:12:27.699 app[1781912f515d89] hkg [info] INFO [fly api proxy] listening at /.fly/api 2023-08-13T12:12:27.708 app[1781912f515d89] hkg [info] 2023/08/13 20:12:27 listening on [fdaa:2:a79:a7b:7f07:dc3d:fed3:2]:22 (DNS: [fdaa::3]:53) 2023-08-13T12:12:27.833 app[1781912f515d89] hkg [info] * Restarting OpenBSD Secure Shell server sshd 2023-08-13T12:12:27.844 app[1781912f515d89] hkg [info] ...done. 2023-08-13T12:12:27.855 app[1781912f515d89] hkg [info] Generating RSA private key, 2048 bit long modulus (2 primes) 2023-08-13T12:12:27.869 app[1781912f515d89] hkg [info] .............+++++ 2023-08-13T12:12:27.901 app[1781912f515d89] hkg [info] ................................+++++ 2023-08-13T12:12:27.901 app[1781912f515d89] hkg [info] e is 65537 (0x010001) 2023-08-13T12:12:27.907 app[1781912f515d89] hkg [info] Signature ok 2023-08-13T12:12:27.907 app[1781912f515d89] hkg [info] subject=CN = nezha-data.jz-home.top 2023-08-13T12:12:27.908 app[1781912f515d89] hkg [info] Getting Private key 2023-08-13T12:12:27.917 app[1781912f515d89] hkg [info] * Restarting periodic command scheduler cron 2023-08-13T12:12:27.918 app[1781912f515d89] hkg [info] * Stopping periodic command scheduler cron 2023-08-13T12:12:27.920 app[1781912f515d89] hkg [info] ...done. 2023-08-13T12:12:27.922 app[1781912f515d89] hkg [info] * Starting periodic command scheduler cron 2023-08-13T12:12:27.925 app[1781912f515d89] hkg [info] ...done. 2023-08-13T12:12:28.168 app[1781912f515d89] hkg [info] 2023-08-13 20:12:28,167 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2023-08-13T12:12:28.168 app[1781912f515d89] hkg [info] 2023-08-13 20:12:28,167 INFO Included extra file "/etc/supervisor/conf.d/damon.conf" during parsing 2023-08-13T12:12:28.174 app[1781912f515d89] hkg [info] 2023-08-13 20:12:28,174 INFO RPC interface 'supervisor' initialized 2023-08-13T12:12:28.174 app[1781912f515d89] hkg [info] 2023-08-13 20:12:28,174 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2023-08-13T12:12:28.175 app[1781912f515d89] hkg [info] 2023-08-13 20:12:28,174 INFO supervisord started with pid 319 2023-08-13T12:12:29.178 app[1781912f515d89] hkg [info] 2023-08-13 20:12:29,178 INFO spawned: 'agent' with pid 322 2023-08-13T12:12:29.182 app[1781912f515d89] hkg [info] 2023-08-13 20:12:29,181 INFO spawned: 'argo' with pid 323 2023-08-13T12:12:29.184 app[1781912f515d89] hkg [info] 2023-08-13 20:12:29,183 INFO spawned: 'nezha' with pid 324 2023-08-13T12:12:29.193 app[1781912f515d89] hkg [info] 2023-08-13 20:12:29,192 INFO spawned: 'nginx' with pid 325 2023-08-13T12:12:30.576 app[1781912f515d89] hkg [info] 2023-08-13 20:12:30,575 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-08-13T12:12:30.576 app[1781912f515d89] hkg [info] 2023-08-13 20:12:30,576 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-08-13T12:12:30.576 app[1781912f515d89] hkg [info] 2023-08-13 20:12:30,576 INFO success: nezha entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-08-13T12:12:30.576 app[1781912f515d89] hkg [info] 2023-08-13 20:12:30,576 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-08-13T12:12:30.715 app[1781912f515d89] hkg [info] 2023-08-13 20:12:30,715 INFO exited: agent (exit status 1; not expected) 2023-08-13T12:12:31.718 app[1781912f515d89] hkg [info] 2023-08-13 20:12:31,717 INFO spawned: 'agent' with pid 343 2023-08-13T12:12:33.252 app[1781912f515d89] hkg [info] 2023-08-13 20:12:33,251 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-08-13T12:13:02.866 app[1781912f515d89] hkg [info] 2023-08-13 20:13:02,859 INFO waiting for nezha to stop 2023-08-13T12:13:02.871 app[1781912f515d89] hkg [info] 2023-08-13 20:13:02,871 INFO stopped: nezha (exit status 0) 2023-08-13T12:13:03.404 app[1781912f515d89] hkg [info] 2023-08-13 20:13:03,403 INFO spawned: 'nezha' with pid 368 2023-08-13T12:13:04.408 app[1781912f515d89] hkg [info] 2023-08-13 20:13:04,405 INFO success: nezha entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) ```
Agent端 ``` Aug 13 12:37:08 instance-8 systemd[1]: Stopping Nezha Agent... -- Subject: Unit nezha-agent.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nezha-agent.service has begun shutting down. Aug 13 12:37:08 instance-8 systemd[1]: Stopped Nezha Agent. -- Subject: Unit nezha-agent.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nezha-agent.service has finished shutting down. Aug 13 12:37:08 instance-8 systemd[1]: Started Nezha Agent. -- Subject: Unit nezha-agent.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nezha-agent.service has finished starting up. -- -- The start-up result is done. ```
DullJZ commented 1 year ago

排查出服务均无问题，自动生成的被控端命令有问题。 curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh install_agent nezha-ssh.xxxxx.xxx 443 xxxxxxxxxx --tls 域名中的nezha-ssh 应改为nezha-data

fscarmen2 commented 1 year ago

排查出服务均无问题，自动生成的被控端命令有问题。 curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh install_agent nezha-ssh.xxxxx.xxx 443 xxxxxxxxxx --tls 域名中的nezha-ssh 应改为nezha-data

没有问题的，应该是设置错误了，因为其他用户没有反馈这个问题，可以在面板那里改

image

对于疑问一，argo 是不支持 gRPC，所以过去是http2的流量，之后在面板服务端的nginx反代 gRPC的。