进程守护启动不了，提示是
2024-09-19 19:14:09,543 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-09-19 19:14:09,543 WARN No file matches via include "/www/server/panel/plugin/supervisor/profile/*.ini"
2024-09-19 19:14:09,848 INFO RPC interface 'supervisor' initialized
2024-09-19 19:14:09,848 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-09-19 19:14:09,854 INFO daemonizing the supervisord process
2024-09-19 19:14:09,854 INFO supervisord started with pid 114834
2024-09-22 11:05:32,106 INFO spawned: 'q1000_00' with pid 210298
2024-09-22 11:05:32,117 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:05:33,286 INFO spawned: 'q1000_00' with pid 210302
2024-09-22 11:05:33,291 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:05:35,294 INFO spawned: 'q1000_00' with pid 210303
2024-09-22 11:05:35,300 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:05:38,412 INFO spawned: 'q1000_00' with pid 210307
2024-09-22 11:05:38,418 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:05:39,419 INFO gave up: q1000_00 entered FATAL state, too many start retries too quickly
2024-09-22 11:06:00,080 INFO spawned: 'q1000_00' with pid 210310
2024-09-22 11:06:00,085 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:06:01,088 INFO spawned: 'q1000_00' with pid 210311
2024-09-22 11:06:01,094 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:06:03,098 INFO spawned: 'q1000_00' with pid 210312
2024-09-22 11:06:03,104 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:06:06,109 INFO spawned: 'q1000_00' with pid 210313
2024-09-22 11:06:06,115 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:06:07,116 INFO gave up: q1000_00 entered FATAL state, too many start retries too quickly
2024-09-22 11:13:28,148 INFO spawned: 'q1000_00' with pid 210557
2024-09-22 11:13:28,154 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:13:29,157 INFO spawned: 'q1000_00' with pid 210560
2024-09-22 11:13:29,166 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:13:31,170 INFO spawned: 'q1000_00' with pid 210561
2024-09-22 11:13:31,176 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:13:34,180 INFO spawned: 'q1000_00' with pid 210562
2024-09-22 11:13:34,185 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:13:35,187 INFO gave up: q1000_00 entered FATAL state, too many start retries too quickly
2024-09-22 11:13:46,784 INFO spawned: 'q1000_00' with pid 210567
2024-09-22 11:13:46,790 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:13:47,793 INFO spawned: 'q1000_00' with pid 210568
2024-09-22 11:13:47,799 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:13:49,803 INFO spawned: 'q1000_00' with pid 210569
2024-09-22 11:13:49,809 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:13:52,813 INFO spawned: 'q1000_00' with pid 210570
2024-09-22 11:13:52,819 INFO exited: q1000_00 (exit status 127; not expected)
2024-09-22 11:13:53,820 INFO gave up: q1000_00 entered FATAL state, too many start retries too quickly
2024-09-22 11:17:50,053 WARN received SIGTERM indicating exit request
