2023-07-19 15:43:45,123 INFO success: spug-api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-19 15:43:45,123 INFO success: spug-worker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-19 15:43:45,123 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-19 15:43:45,123 INFO success: spug-ws entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-19 15:43:45,123 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-19 15:43:47,024 INFO success: spug-scheduler entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2023-07-19 15:43:47,024 INFO success: spug-monitor entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2023-07-19 15:43:47,271 INFO exited: spug-monitor (exit status 1; not expected)
2023-07-19 15:43:47,303 INFO spawned: 'spug-monitor' with pid 73
2023-07-19 15:43:47,303 INFO exited: spug-scheduler (exit status 1; not expected)
2023-07-19 15:43:48,305 INFO spawned: 'spug-scheduler' with pid 79
2023-07-19 15:43:49,656 INFO exited: spug-monitor (exit status 1; not expected)
2023-07-19 15:43:50,685 INFO spawned: 'spug-monitor' with pid 93
2023-07-19 15:43:50,686 INFO exited: spug-scheduler (exit status 1; not expected)
2023-07-19 15:43:51,688 INFO spawned: 'spug-scheduler' with pid 99
2023-07-19 15:43:53,371 INFO exited: spug-monitor (exit status 1; not expected)
2023-07-19 15:43:54,094 INFO exited: spug-scheduler (exit status 1; not expected)
2023-07-19 15:43:56,097 INFO spawned: 'spug-scheduler' with pid 113
2023-07-19 15:43:56,099 INFO spawned: 'spug-monitor' with pid 114
2023-07-19 15:43:58,488 INFO exited: spug-scheduler (exit status 1; not expected)
2023-07-19 15:43:58,611 INFO exited: spug-monitor (exit status 1; not expected)
2023-07-19 15:44:01,617 INFO spawned: 'spug-scheduler' with pid 133
2023-07-19 15:44:01,620 INFO spawned: 'spug-monitor' with pid 134
2023-07-19 15:44:04,451 INFO exited: spug-monitor (exit status 1; not expected)
2023-07-19 15:44:04,474 INFO gave up: spug-monitor entered FATAL state, too many start retries too quickly
2023-07-19 15:44:04,474 INFO exited: spug-scheduler (exit status 1; not expected)
2023-07-19 15:44:05,476 INFO gave up: spug-scheduler entered FATAL state, too many start retries too quickly
Spug 版本:3.2.7
问题重现步骤
报错/问题截图
2023-07-19 15:43:45,123 INFO success: spug-api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-07-19 15:43:45,123 INFO success: spug-worker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-07-19 15:43:45,123 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-07-19 15:43:45,123 INFO success: spug-ws entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-07-19 15:43:45,123 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-07-19 15:43:47,024 INFO success: spug-scheduler entered RUNNING state, process has stayed up for > than 3 seconds (startsecs) 2023-07-19 15:43:47,024 INFO success: spug-monitor entered RUNNING state, process has stayed up for > than 3 seconds (startsecs) 2023-07-19 15:43:47,271 INFO exited: spug-monitor (exit status 1; not expected) 2023-07-19 15:43:47,303 INFO spawned: 'spug-monitor' with pid 73 2023-07-19 15:43:47,303 INFO exited: spug-scheduler (exit status 1; not expected) 2023-07-19 15:43:48,305 INFO spawned: 'spug-scheduler' with pid 79 2023-07-19 15:43:49,656 INFO exited: spug-monitor (exit status 1; not expected) 2023-07-19 15:43:50,685 INFO spawned: 'spug-monitor' with pid 93 2023-07-19 15:43:50,686 INFO exited: spug-scheduler (exit status 1; not expected) 2023-07-19 15:43:51,688 INFO spawned: 'spug-scheduler' with pid 99 2023-07-19 15:43:53,371 INFO exited: spug-monitor (exit status 1; not expected) 2023-07-19 15:43:54,094 INFO exited: spug-scheduler (exit status 1; not expected) 2023-07-19 15:43:56,097 INFO spawned: 'spug-scheduler' with pid 113 2023-07-19 15:43:56,099 INFO spawned: 'spug-monitor' with pid 114 2023-07-19 15:43:58,488 INFO exited: spug-scheduler (exit status 1; not expected) 2023-07-19 15:43:58,611 INFO exited: spug-monitor (exit status 1; not expected) 2023-07-19 15:44:01,617 INFO spawned: 'spug-scheduler' with pid 133 2023-07-19 15:44:01,620 INFO spawned: 'spug-monitor' with pid 134 2023-07-19 15:44:04,451 INFO exited: spug-monitor (exit status 1; not expected) 2023-07-19 15:44:04,474 INFO gave up: spug-monitor entered FATAL state, too many start retries too quickly 2023-07-19 15:44:04,474 INFO exited: spug-scheduler (exit status 1; not expected) 2023-07-19 15:44:05,476 INFO gave up: spug-scheduler entered FATAL state, too many start retries too quickly
期望的结果
能在arm飞腾和鲲鹏上都无法正常使用