fscarmen2 / argo-nezha-service-container Goto Github PK

部署方式是VPS宿主机，部署完成后能正常访问，但是点登录跳转到 https://域名.com/oauth2/callback 时会 Error code 502，此时整个哪吒面板都会502，就算回到首页也是502，只能reboot vps才能正常。

如果容器重启了，那么哪吒面板里之前添加的服务器会丢失吗？需不需要重新添加服务器。

What is server_json and web_json? how i can import it ?

今天凌晨莫名其妙的全部agent都掉了.....不知道是什么问题

是不是用argo-paas哪吒的主控端，每次新加被监控端是不是不需要填数据端口5555？
因为主控走的是argo隧道，所以被监控端数据端口5555是不是不用填了？
确认一下

error " There are variables that are not set. "，entrypoint.sh这段没考虑使用“ARGO_JSON”参数的情况，造成Service is unhealthy

原先docker模式：github面板网页域名：Argo域名
github回源域名：https://Argo域名/oauth2/callback
数据接口域名：教程里的data域名
安装后，机器会自动配置好，面板服务端的探针。

直装模式：github网页，github回源，数据接口，全部为Argo域名。(注意点，面板复制粘贴给的安装命令端口需要手动改成
443。安装后，服务端的探针没有自动配置。另外，原有的docker的备份好像不通用）

是否可以集成xray？将容器充分利用起来😂😂

In the service back4 what should I enter in the patch if I want to use the main project address in my cloudflare?

win系统下载cloudflared.exe放到windterm默认目录下，这样路径应该不用填了，直接cloudflared.exe access ssh --hostname ssh.xxxx.xxxx，提示输入用户名密码，用户名应该是root，密码就是我填的密码，连接时提示会话已断开

数据有时候会回档

在render上部署成功，试着添加了2个vps，刚开始几分钟可以正常查看监控页面，但几分钟后监控页面就打不开了，然后几分钟后监控页面又能正常打开，但是添加的2个vps也没有了，试了几次都是这样的情况，请问这是什么问题？

使用一键脚本安装好之后都正常，就是连不上主控
在nodeseek看到有朋友反馈了这个问题
我也遇到了这个问题，我的环境如下

1. host/proto.NezhaService/
   浏览器访问正常
2. ip:5000
   端口正常，有响应
3. ip:5002
   端口正常，有响应

表现如下
正常 /opt/nezha/agent/nezha-agent -s ip:5002 -p 密钥
异常 /opt/nezha/agent/nezha-agent -s ip:5000 -p 密钥 --tls
异常 /opt/nezha/agent/nezha-agent -s host:443 -p 密钥 --tls

koybe部署的面板上，每隔几十秒会显示Agent机器已离线， 下一秒有恢复连接。

有人和我一样吗？ vps上安装的哪吒没发现这个问题。 是koybe部署的时候我哪里没设置对吗？

hax Ubuntu备份报错了


用的是宿主机部署，没有安装warp

请教，今天Koyeb部署哪吒，服务器实例启动时出现出错，如下，不知道为何？

2023-09-09 16:17:57,591 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-09 16:17:57,591 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-09 16:17:57,591 INFO success: nezha entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-09 16:17:57,591 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
./entrypoint.sh: line 15: /etc/resolv.conf: Read-only file system
Generating RSA private key, 2048 bit long modulus (2 primes)
.......................................................+++++
...............+++++
e is 65537 (0x010001)
Signature ok
subject=CN = data.langyun.pp.ua
Getting Private key
Instance is healthy

现在哪些paas容器平台比较稳定？365x24小时不掉那种

被监控端也一定需要argo吗？像以前一样用容器布置节点（内置哪吒）直接填行不行

请教一下如何在replit或者其他paas容器中部署？有没有教程？因为现在koyeb需要绑卡才能用，可是我没有卡

问题描述

版本：fscarmen/argo-nezha:latest (近两天更新的

假如有 4 台 server A B C D，将 C D 移除，再添加一个 E，此时面板展示 A B E
如果触发备份（自动备份或者 ./backup.sh ），并且无法连接 github，将会变回 A B C D

复现步骤

1. A B C D => A B => A B E
2. 不允许设备 fq（ban 掉 github）
3. 触发备份

期望结果

A B C D => A B => A B E => 备份失败 => 依然是 A B E

可能的解决方案

1. backup 脚本 git push 增加超时 tag
2. stoped 后，如果发生错误，那么不应该丢失数据

在Back4App部署出现“Dockerfile must expose only one tcp port”错误

2023-04-29T04:40:42.096ZINFOTaking snapshot of full filesystem...

2023-04-29T04:41:03.000ZINFOPushing layer registry.containers.back4app.com/back4app2-ef899b75-a924-4339-ab1c-407db07a4d65/cache:e4d47cee0b85a07ce53a0f3866fd0a31b6110b1ac9439d1e33d2bf2c52d94769 to cache now

2023-04-29T04:41:03.001ZINFOENTRYPOINT ["./entrypoint.sh"]

2023-04-29T04:41:03.002ZINFOPushing image to registry.containers.back4app.com/back4app2-ef899b75-a924-4339-ab1c-407db07a4d65/cache:e4d47cee0b85a07ce53a0f3866fd0a31b6110b1ac9439d1e33d2bf2c52d94769

2023-04-29T04:41:03.003ZINFONo files changed in this command, skipping snapshotting.

2023-04-29T04:41:09.000ZINFOPushed registry.containers.back4app.com/back4app2-ef899b75-a924-4339-ab1c-407db07a4d65/cache@sha256:292d508a975ea7098efcd73144e46abd4ab58eedf5dd123e221cb145cc7a595b

2023-04-29T04:41:09.001ZINFOPushing image to registry.containers.back4app.com/back4app2-ef899b75-a924-4339-ab1c-407db07a4d65:10a04724-28aa-448b-a6ba-3a4bbbd1cc25

2023-04-29T04:41:15.000ZINFOPushed registry.containers.back4app.com/back4app2-ef899b75-a924-4339-ab1c-407db07a4d65@sha256:5e282dde6452cb7415c2949e55ed53b924b04eff51bfc7405e63ab0f83c3328e

2023-04-29T04:41:16.751ZSYSTEMLAUNCHING CONTAINER...

2023-04-29T04:41:26.772ZSYSTEMDockerfile must expose only one tcp port

2023-04-29T04:41:26.773ZSYSTEMdeployment failed

I have been using koyeb.com for 1 month, the service works well
But today the service was stopped for unknown reasons.
I tried redeploy but failed, tried changing datacenter.

我填的域名： data.xxx.xxx
端口:443
密钥：xxxxxxxxx --tls

面板上不行呢

系统:CentOS 7.9.2009 x86_64(Py3.7.9)
CPU：AMD EPYC 7551 32-Core Processor 2 Virtual Core

vps上的argo似乎启动失败，无法访问，cloudflare显示Error 1033
vps上argo的变量有加了两个点
vps上使用了宝塔面板的docker-compose-部署
测试过变量在koyeb上运行正常，可以访问
以下是运行日志

ped 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-05-11 18:01:17,367 INFO Included extra file "/etc/supervisor/conf.d/damon.conf" during parsing
2023-05-11 18:01:17,441 INFO RPC interface 'supervisor' initialized
2023-05-11 18:01:17,441 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-05-11 18:01:17,442 INFO supervisord started with pid 60
2023-05-11 18:01:18,445 INFO spawned: 'agent' with pid 62
2023-05-11 18:01:18,448 INFO spawned: 'argo' with pid 63
2023-05-11 18:01:18,450 INFO spawned: 'nezha' with pid 64
2023-05-11 18:01:18,453 INFO spawned: 'nginx' with pid 65
2023-05-11 18:01:19,272 INFO exited: argo (exit status 1; not expected)
2023-05-11 18:01:20,274 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-05-11 18:01:20,275 INFO spawned: 'argo' with pid 82
2023-05-11 18:01:20,275 INFO success: nezha entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-05-11 18:01:20,275 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-05-11 18:01:20,370 INFO exited: argo (exit status 1; not expected)
2023-05-11 18:01:22,374 INFO spawned: 'argo' with pid 88
2023-05-11 18:01:22,448 INFO exited: argo (exit status 1; not expected)
2023-05-11 18:01:25,452 INFO spawned: 'argo' with pid 96
2023-05-11 18:01:25,560 INFO exited: argo (exit status 1; not expected)
2023-05-11 18:01:26,561 INFO gave up: argo entered FATAL state, too many start retries too quickly

容器哪吒，白嫖走起

NEZHA@2023-09-23 07:20:40>> 上 报 系 统 信 息 失 败 ： rpc error: code = Unknown desc = unexpected HTTP status code received from server: 500 (Internal Server Error); transport: received unexpected content-type "text/plain; charset=utf-8"
NEZHA@2023-09-23 07:20:40>> Error to close connection ...
NEZHA@2023-09-23 07:20:50>> Try to reconnect ...

好改，改得要么沿用原域名需要全部重新部署，要么沿用原来的data域名
改得太好了，不改啥事没有，改了出一堆问题
之前那个ARGO_JSON改成ARGO_AUTH没说啥，动动手的事
这次真忍不了了，直接要改域名了
😃👍🏻

下载 app 失败，安装中止，

如上图，今日凌晨时分不知为何突然Argo Tunnel error了，上Koyeb一看，不知怎么就Unhealthy了，新部署也不行

大佬，昨天我在容器从新部署了一遍，是昨天 v0.15.11.
部署后添加了一个小鸡监控，想看一下自动备份后监控面板会不会清空失去信息。
今天发现面板信息清空了，不知道是不是跟更新版本有关系，今早发现已经是 v0.15.12.
最初使用中遇到的问题是版本更新后会失去面板的信息，然后我想手动修改[README.md]以恢复备份到以前的自动备份。
但是修改后没有自动恢复，而且修改过[README.md]以后就不再自动备份了。当时版本是v0.15.10或者v0.15.11的样子。

目前仓库里的程序是从镜像直接提取的，不兼容alpine，大佬可以看看这个仓库，有编译好的面板程序
https://github.com/applexad/nezha-binary-build

root@9b65acb5:/app# systemctl status nezha-agent
nezha-agent.service - Nezha Agent
Loaded: loaded (/etc/systemd/system/nezha-agent.service, enabled)
Active: active (running)
root@9b65acb5:/app# systemctl stop nezha-agent
root@9b65acb5:/app# /opt/nezha/agent/nezha-agent -s data.xxxxxx.vip:443 -p xxxxxxxxxxx -d
NEZHA@2023-10-16 04:23:56>> 检查更新： 0.15.6
NEZHA@2023-10-16 04:23:56>> 上报系统信息失败： rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: http2: frame too large"
NEZHA@2023-10-16 04:23:56>> Error to close connection ...
NEZHA@2023-10-16 04:24:06>> Try to reconnect ...
NEZHA@2023-10-16 04:24:06>> 上报系统信息失败： rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: http2: frame too large"

I followed the instructions, but when I add the VPS, it shows as offline. I've tried multiple times, including changing the domain and using different Cloudflare accounts

koyeb Log
Instance allocated in nomad
Instance is unhealthy
./entrypoint.sh: line 15: /etc/resolv.conf: Read-only file system
Generating RSA private key, 2048 bit long modulus (2 primes)
.........................................................................+++++

• Restarting periodic command scheduler cron
• Stopping periodic command scheduler cron
  ...................................................+++++
  e is 65537 (0x010001)
  ...done.
  Signature ok
• Starting periodic command scheduler cron
  subject=CN = data.xemgia.pp.ua
  ...done.
  Getting Private key
  2023-09-14 16:20:30,021 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-09-14 16:20:30,021 INFO Included extra file "/etc/supervisor/conf.d/damon.conf" during parsing
  2023-09-14 16:20:30,024 INFO RPC interface 'supervisor' initialized
  2023-09-14 16:20:30,024 CRIT Server 'unix_http_server' running without any HTTP authentication checking
  2023-09-14 16:20:30,025 INFO supervisord started with pid 41
  2023-09-14 16:20:31,027 INFO spawned: 'agent' with pid 43
  2023-09-14 16:20:31,029 INFO spawned: 'argo' with pid 44
  2023-09-14 16:20:31,031 INFO spawned: 'nezha' with pid 45
  2023-09-14 16:20:31,037 INFO spawned: 'nginx' with pid 46
  2023-09-14 16:20:32,170 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  2023-09-14 16:20:32,170 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  2023-09-14 16:20:32,170 INFO success: nezha entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  2023-09-14 16:20:32,170 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  Instance is healthy

VPS log

nezha-agent.service - Nezha Agent
Loaded: loaded (/etc/systemd/system/nezha-agent.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2023-09-14 08:23:02 GMT; 28s ago
Main PID: 13597 (nezha-agent)
Tasks: 4
Memory: 8.7M
CGroup: /system.slice/nezha-agent.service
└─13597 /opt/nezha/agent/nezha-agent -s data.xemgia.pp.ua:443 -p hMPHylW7uC4yVuWGrB --tls

Sep 14 08:23:02 instance-20220513-1644 systemd[1]: Stopped Nezha Agent.
Sep 14 08:23:02 instance-20220513-1644 systemd[1]: Started Nezha Agent.

我这是哪里填错了吗，F佬

如图，日志看似均无问题

但有实时连接已建立的弹窗
环境变量均按照文档配置正确
gRPC开关已打开

疑问1

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

疑问2

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

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

日志

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)

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.

在生成域名界面时，授权后无法获取显示json，不知道这是什么情况。

面板端显示实时通道已建立， 但是所有agent都显示离线。继上次更新之后， 有一次全面掉线

使用github登录后提示 错误信息：http: named cookie not present

换过浏览器和设备，都不行
在用vps部署的哪吒面板可以正常登录

在Northflank上部署的 argo进程异常退出 麻烦f佬看下

2023-06-08T08:31:07.611075362Z stdout F [2023-06-08T08:31:07Z INFO ] Securely fetching environment variables...
2023-06-08T08:31:08.092067644Z stdout F [2023-06-08T08:31:08Z INFO ] Successfully fetched environment variables.
2023-06-08T08:31:08.092094207Z stdout F [2023-06-08T08:31:08Z INFO ] Starting container entrypoint...
2023-06-08T08:31:08.76910291Z stdout F  * Restarting OpenBSD Secure Shell server sshd
2023-06-08T08:31:08.82978724Z stdout F    ...done.
2023-06-08T08:31:08.932537887Z stderr F Generating RSA private key, 2048 bit long modulus (2 primes)
2023-06-08T08:31:09.027653521Z stderr F ....................+++++
2023-06-08T08:31:09.210879782Z stderr F .............................+++++
2023-06-08T08:31:09.211132919Z stderr F e is 65537 (0x010001)
2023-06-08T08:31:09.318750318Z stderr F Signature ok
2023-06-08T08:31:09.318777334Z stderr F subject=CN = data.akamino.cf
2023-06-08T08:31:09.319668096Z stderr F Getting Private key
2023-06-08T08:31:09.513530439Z stdout F  * Restarting periodic command scheduler cron
2023-06-08T08:31:09.518848613Z stdout F  * Stopping periodic command scheduler cron
2023-06-08T08:31:09.533573775Z stdout F    ...done.
2023-06-08T08:31:09.611028397Z stdout F  * Starting periodic command scheduler cron
2023-06-08T08:31:09.617194449Z stdout F    ...done.
2023-06-08T08:31:11.608750068Z stdout F 2023-06-08 16:31:11,591 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-06-08T08:31:11.609180211Z stdout F 2023-06-08 16:31:11,591 INFO Included extra file "/etc/supervisor/conf.d/damon.conf" during parsing
2023-06-08T08:31:11.620474716Z stdout F 2023-06-08 16:31:11,602 INFO RPC interface 'supervisor' initialized
2023-06-08T08:31:11.620490367Z stdout F 2023-06-08 16:31:11,602 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-06-08T08:31:11.621350602Z stdout F 2023-06-08 16:31:11,603 INFO supervisord started with pid 57
2023-06-08T08:31:12.629236795Z stdout F 2023-06-08 16:31:12,610 INFO spawned: 'agent' with pid 59
2023-06-08T08:31:12.70886397Z stdout F 2023-06-08 16:31:12,621 INFO spawned: 'argo' with pid 60
2023-06-08T08:31:12.813800865Z stdout F 2023-06-08 16:31:12,795 INFO spawned: 'nezha' with pid 61
2023-06-08T08:31:13.011060464Z stdout F 2023-06-08 16:31:12,992 INFO spawned: 'nginx' with pid 66
2023-06-08T08:31:14.016262255Z stdout F 2023-06-08 16:31:13,998 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-08T08:31:14.016543015Z stdout F 2023-06-08 16:31:13,998 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-08T08:31:14.016557213Z stdout F 2023-06-08 16:31:13,999 INFO success: nezha entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-08T08:31:14.016955721Z stdout F 2023-06-08 16:31:13,999 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-08T08:31:16.714265885Z stdout F 2023-06-08 16:31:16,695 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:17.720199241Z stdout F 2023-06-08 16:31:17,702 INFO spawned: 'argo' with pid 80
2023-06-08T08:31:18.219237732Z stdout F 2023-06-08 16:31:18,201 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:19.222861514Z stdout F 2023-06-08 16:31:19,205 INFO spawned: 'argo' with pid 85
2023-06-08T08:31:19.625215883Z stdout F 2023-06-08 16:31:19,607 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:21.615395431Z stdout F 2023-06-08 16:31:21,614 INFO spawned: 'argo' with pid 90
2023-06-08T08:31:21.893094794Z stdout F 2023-06-08 16:31:21,892 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:24.996301674Z stdout F 2023-06-08 16:31:24,994 INFO spawned: 'argo' with pid 95
2023-06-08T08:31:26.095300607Z stdout F 2023-06-08 16:31:26,094 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-08T08:31:27.998288846Z stdout F 2023-06-08 16:31:27,997 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:28.436369224Z stdout F 2023-06-08 16:31:28,435 INFO spawned: 'argo' with pid 99
2023-06-08T08:31:28.437151909Z stdout F 2023-06-08 16:31:28,436 INFO exited: agent (exit status 1; not expected)
2023-06-08T08:31:28.704269451Z stdout F 2023-06-08 16:31:28,703 INFO spawned: 'agent' with pid 104
2023-06-08T08:31:28.705461538Z stdout F 2023-06-08 16:31:28,705 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:29.708996258Z stdout F 2023-06-08 16:31:29,708 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-08T08:31:29.713761269Z stdout F 2023-06-08 16:31:29,711 INFO spawned: 'argo' with pid 112
2023-06-08T08:31:31.107753997Z stdout F 2023-06-08 16:31:31,107 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-08T08:31:31.108508803Z stdout F 2023-06-08 16:31:31,108 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:32.114727131Z stdout F 2023-06-08 16:31:32,113 INFO spawned: 'argo' with pid 121
2023-06-08T08:31:32.39336685Z stdout F 2023-06-08 16:31:32,393 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:33.398030939Z stdout F 2023-06-08 16:31:33,397 INFO spawned: 'argo' with pid 127
2023-06-08T08:31:33.601252283Z stdout F 2023-06-08 16:31:33,600 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:35.607387957Z stdout F 2023-06-08 16:31:35,606 INFO spawned: 'argo' with pid 134
2023-06-08T08:31:35.801769147Z stdout F 2023-06-08 16:31:35,801 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:38.809070688Z stdout F 2023-06-08 16:31:38,808 INFO spawned: 'argo' with pid 142
2023-06-08T08:31:40.094886106Z stdout F 2023-06-08 16:31:40,094 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-08T08:31:40.095626006Z stdout F 2023-06-08 16:31:40,095 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:41.100128453Z stdout F 2023-06-08 16:31:41,099 INFO spawned: 'argo' with pid 149
2023-06-08T08:31:41.396096608Z stdout F 2023-06-08 16:31:41,395 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:42.401062536Z stdout F 2023-06-08 16:31:42,400 INFO spawned: 'argo' with pid 156
2023-06-08T08:31:42.602409147Z stdout F 2023-06-08 16:31:42,602 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:44.607947933Z stdout F 2023-06-08 16:31:44,607 INFO spawned: 'argo' with pid 162
2023-06-08T08:31:44.895955337Z stdout F 2023-06-08 16:31:44,895 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:47.902835631Z stdout F 2023-06-08 16:31:47,902 INFO spawned: 'argo' with pid 170
2023-06-08T08:31:48.107529624Z stdout F 2023-06-08 16:31:48,107 INFO exited: argo (exit status 1; not expected)
2023-06-08T08:31:49.109408994Z stdout F 2023-06-08 16:31:49,108 INFO gave up: argo entered FATAL state, too many start retries too quickly

搭建好之后，正常访问了几天，今天早上访问的时候就无法打开了

用容器给的地址打开提示503

使用的容器是Patr。

二十余台机器，因为data和ssh改为共用一个域名，每个都要重新执行命令
尝试data域名CNAME到主域名好像不行

Docker部署最新版本探针后，自动备份正常，手动备份失败。

1. 尝试按教程中手动备份说明，修改README.md为backup，等待15分钟后库的内容没有发生变化。

2. 等待无果，尝试进入容器运行/dashboard/backup.sh，提示没有权限。手动赋予权限后执行成功。

感觉方法1如果能正常使用，其实更加方便，因为无需连入服务器。大佬能否帮忙看看有可能是什么原因？谢谢。