fscarmen2 / Argo-Nezha-Service-Container

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

argo异常退出 #19

Closed e5u closed 1 year ago

e5u commented 1 year ago

在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
fscarmen2 commented 1 year ago

分析不出什么问题,看看环境变量齐不齐呢

e5u commented 1 year ago

image 应该是齐的

e5u commented 1 year ago

image 问题所在 我自己json格式错了