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.

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

宿主机访问Argo域名问题 #124

Open
niuniulin6 opened this issue Dec 2, 2024 · 9 comments
Open

宿主机访问Argo域名问题 #124

niuniulin6 opened this issue Dec 2, 2024 · 9 comments

Comments

@niuniulin6
Copy link

宿主机访问Argo域名提示host error 502,请教下是什么问题?

@fscarmen2
Copy link
Owner

fscarmen2 commented Dec 2, 2024

没部署好,或数据正在恢复中,稍等下看

@ekko440
Copy link

ekko440 commented Dec 2, 2024

我也是这样,重装好几次也是502

@fscarmen2
Copy link
Owner

可能是有的参数没有设置好,导致部署时没有完成,可以看看日志没有报什么,又或者进去webssh看进程。

@ekko440
Copy link

ekko440 commented Dec 2, 2024

2024-12-03 01:29:44 (191 KB/s) - '/dashboard/data/sqlite.db' saved [147456/147456]

Restarting OpenBSD Secure Shell server: sshd.
Certificate request self-signature ok
subject=CN = nezha.oo0oo.us.kg
Restarting periodic command scheduler: cronStopping periodic command scheduler: cron.
Starting periodic command scheduler: cron.
2024-12-03 01:30:07,420 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.
2024-12-03 01:30:07,421 INFO Included extra file "/etc/supervisor/conf.d/damon.conf" during parsing
2024-12-03 01:30:07,615 INFO RPC interface 'supervisor' initialized
2024-12-03 01:30:07,616 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-12-03 01:30:07,617 INFO supervisord started with pid 251
2024-12-03 01:30:07,977 INFO spawned: 'agent' with pid 284
2024-12-03 01:30:07,986 INFO spawned: 'argo' with pid 285
2024-12-03 01:30:07,992 INFO spawned: 'grpcproxy' with pid 286
2024-12-03 01:30:07,999 INFO spawned: 'nezha' with pid 287
2024-12-03 01:30:08,020 INFO waiting for agent to stop
2024-12-03 01:30:08,038 WARN stopped: agent (terminated by SIGTERM)
2024-12-03 01:30:08,047 INFO waiting for nezha to stop
2024-12-03 01:30:08,072 WARN stopped: nezha (terminated by SIGTERM)
2024-12-03 01:30:08,083 INFO waiting for grpcproxy to stop
2024-12-03 01:30:08,089 WARN stopped: grpcproxy (terminated by SIGTERM)
2024-12-03 01:30:09,114 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-12-03 01:30:12,372 INFO spawned: 'agent' with pid 328
2024-12-03 01:30:14,233 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-12-03 01:30:14,242 INFO spawned: 'nezha' with pid 337
2024-12-03 01:30:14,571 WARN exited: nezha (exit status 2; not expected)
2024-12-03 01:30:15,008 INFO spawned: 'grpcproxy' with pid 344
2024-12-03 01:30:16,546 INFO success: grpcproxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-12-03 01:30:16,553 INFO spawned: 'nezha' with pid 353
2024-12-03 01:30:16,927 WARN exited: nezha (exit status 2; not expected)
2024-12-03 01:30:18,935 INFO spawned: 'nezha' with pid 361
2024-12-03 01:30:19,258 WARN exited: nezha (exit status 2; not expected)
2024-12-03 01:30:22,717 INFO spawned: 'nezha' with pid 376
2024-12-03 01:30:23,048 WARN exited: nezha (exit status 2; not expected)
2024-12-03 01:30:24,050 INFO gave up: nezha entered FATAL state, too many start retries too quickly

@ekko440
Copy link

ekko440 commented Dec 2, 2024

几天前还能用,掉线再上不去了。

@fscarmen2
Copy link
Owner

fscarmen2 commented Dec 2, 2024

会不会用了v1的config.yaml文件导致面板启动不了,看这里恢复
#120
可以的话可webssh进去看看 data/config.yaml 文件是不是v0 的

@ekko440
Copy link

ekko440 commented Dec 3, 2024

会不会用了v1的config.yaml文件导致面板启动不了,看这里恢复 #120 可以的话可webssh进去看看 data/config.yaml 文件是不是v0 的

谢谢解决了。

@woshichenghaibo
Copy link

免费容器每次重启都会重新拉取镜像吗?可不可以固定住目前的不动?

@fscarmen2
Copy link
Owner

免费容器每次重启都会重新拉取镜像吗?可不可以固定住目前

这个是平台政策啊,没有得改的,其实有备份数据,重新拉镜像,只需要多几分钟时间还原数据而已,不影响啊。你遇到什么问题了吗?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants