2023-12-08 18:02:23,607 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-12-08 18:02:23,607 WARN No file matches via include "/www/server/panel/plugin/supervisor/profile/*.ini"

2023-12-08 18:02:23,911 INFO RPC interface 'supervisor' initialized

2023-12-08 18:02:23,911 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2023-12-08 18:02:23,912 INFO daemonizing the supervisord process

2023-12-08 18:02:23,914 INFO supervisord started with pid 451416

2023-12-08 18:03:01,577 INFO spawnerr: can't find command 'queue:listen'

2023-12-08 18:03:02,772 INFO spawnerr: can't find command 'queue:listen'

2023-12-08 18:03:04,774 INFO spawnerr: can't find command 'queue:listen'

2023-12-08 18:03:07,872 INFO spawnerr: can't find command 'queue:listen'

2023-12-08 18:03:07,872 INFO gave up: crmeb_00 entered FATAL state, too many start retries too quickly

2024-01-18 09:22:24,982 INFO spawned: 'crmeb_00' with pid 3432396

2024-01-18 09:22:28,059 INFO success: crmeb_00 entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)

2024-01-18 09:27:08,000 INFO waiting for crmeb_00 to stop

2024-01-18 09:27:08,001 INFO stopped: crmeb_00 (terminated by SIGTERM)

2024-01-18 09:27:09,782 INFO spawned: 'crmeb_00' with pid 3432873

2024-01-18 09:27:12,858 INFO success: crmeb_00 entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)

2024-01-18 09:38:57,363 INFO waiting for crmeb_00 to stop

2024-01-18 09:38:57,365 INFO stopped: crmeb_00 (terminated by SIGTERM)

2024-01-18 09:38:59,147 INFO spawned: 'crmeb_00' with pid 3434260

2024-01-18 09:39:02,225 INFO success: crmeb_00 entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)

2024-01-18 09:43:14,112 INFO waiting for crmeb_00 to stop

2024-01-18 09:43:14,113 INFO stopped: crmeb_00 (terminated by SIGTERM)

2024-01-18 09:43:15,896 INFO spawned: 'crmeb_00' with pid 3434464

2024-01-18 09:43:18,973 INFO success: crmeb_00 entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)