first
This commit is contained in:
@@ -0,0 +1,322 @@
|
||||
2025-11-12 08:50:18,927 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.
|
||||
2025-11-12 08:50:18,927 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-11-12 08:50:18,927 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:19,015 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:19,015 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:19,026 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:20,031 INFO spawned: 'mesh' with pid 18
|
||||
2025-11-12 08:50:20,100 INFO spawned: 'alert_reader' with pid 19
|
||||
2025-11-12 08:50:20,232 INFO spawned: 'alert_writer' with pid 22
|
||||
2025-11-12 08:50:21,237 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,237 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,237 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:25,763 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.
|
||||
2025-11-17 12:01:25,769 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-11-17 12:01:25,770 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:26,157 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:26,157 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:26,157 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:27,172 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-17 12:01:27,256 INFO spawned: 'alert_reader' with pid 27
|
||||
2025-11-17 12:01:27,321 INFO spawned: 'alert_writer' with pid 28
|
||||
2025-11-17 12:01:28,389 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,390 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,390 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:41,534 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.
|
||||
2025-11-21 15:30:41,546 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-11-21 15:30:41,546 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:41,892 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:41,895 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:41,895 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:42,937 INFO spawned: 'mesh' with pid 36
|
||||
2025-11-21 15:30:42,982 INFO spawned: 'alert_reader' with pid 38
|
||||
2025-11-21 15:30:43,068 INFO spawned: 'alert_writer' with pid 41
|
||||
2025-11-21 15:30:44,078 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:44,078 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:44,078 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,514 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.
|
||||
2025-11-22 15:19:48,530 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-11-22 15:19:48,530 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:48,899 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:48,966 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:48,966 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:49,972 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:19:50,056 INFO spawned: 'alert_reader' with pid 18
|
||||
2025-11-22 15:19:50,204 INFO spawned: 'alert_writer' with pid 19
|
||||
2025-11-22 15:19:51,233 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,233 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,233 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:01,891 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:28:01,905 INFO waiting for mesh, alert_reader, alert_writer to die
|
||||
2025-11-22 15:28:01,949 INFO stopped: alert_writer (exit status 0)
|
||||
2025-11-22 15:28:01,976 INFO stopped: alert_reader (exit status 0)
|
||||
2025-11-22 15:28:01,983 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:23,616 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.
|
||||
2025-11-22 15:28:23,616 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-11-22 15:28:23,616 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:23,669 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:23,670 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:23,670 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:24,690 INFO spawned: 'mesh' with pid 19
|
||||
2025-11-22 15:28:24,736 INFO spawned: 'alert_reader' with pid 20
|
||||
2025-11-22 15:28:24,789 INFO spawned: 'alert_writer' with pid 22
|
||||
2025-11-22 15:28:25,796 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,796 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,797 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:52,036 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:52,048 INFO waiting for mesh, alert_reader, alert_writer to die
|
||||
2025-11-22 15:30:52,072 INFO stopped: alert_writer (exit status 0)
|
||||
2025-11-22 15:30:52,086 INFO stopped: alert_reader (exit status 0)
|
||||
2025-11-22 15:30:52,096 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:20,053 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.
|
||||
2025-11-22 15:31:20,053 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-11-22 15:31:20,053 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:20,099 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:20,109 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:20,109 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:21,134 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:31:21,223 INFO spawned: 'alert_reader' with pid 18
|
||||
2025-11-22 15:31:21,274 INFO spawned: 'alert_writer' with pid 19
|
||||
2025-11-22 15:31:22,291 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,291 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,291 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:47,789 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:47,798 INFO waiting for mesh, alert_reader, alert_writer to die
|
||||
2025-11-22 15:37:47,815 INFO stopped: alert_writer (exit status 0)
|
||||
2025-11-22 15:37:47,848 INFO stopped: alert_reader (exit status 0)
|
||||
2025-11-22 15:37:47,858 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:25,108 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.
|
||||
2025-11-22 15:38:25,108 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-11-22 15:38:25,108 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:25,166 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:25,166 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:25,166 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:26,189 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:38:26,275 INFO spawned: 'alert_reader' with pid 18
|
||||
2025-11-22 15:38:26,364 INFO spawned: 'alert_writer' with pid 20
|
||||
2025-11-22 15:38:27,437 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:27,437 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:27,437 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,732 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.
|
||||
2025-11-25 15:48:27,741 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-11-25 15:48:27,744 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:28,101 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:28,123 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:28,124 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:29,148 INFO spawned: 'mesh' with pid 18
|
||||
2025-11-25 15:48:29,214 INFO spawned: 'alert_reader' with pid 19
|
||||
2025-11-25 15:48:29,323 INFO spawned: 'alert_writer' with pid 20
|
||||
2025-11-25 15:48:30,403 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,404 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,404 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:24,361 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.
|
||||
2025-12-07 15:52:24,384 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-12-07 15:52:24,384 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:24,730 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:24,739 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:24,743 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:25,748 INFO spawned: 'mesh' with pid 23
|
||||
2025-12-07 15:52:25,804 INFO spawned: 'alert_reader' with pid 24
|
||||
2025-12-07 15:52:25,876 INFO spawned: 'alert_writer' with pid 25
|
||||
2025-12-07 15:52:26,906 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,906 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,906 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:44,163 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.
|
||||
2025-12-08 11:39:44,165 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-12-08 11:39:44,165 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:44,537 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:44,537 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:44,541 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:45,557 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-08 11:39:45,660 INFO spawned: 'alert_reader' with pid 36
|
||||
2025-12-08 11:39:45,758 INFO spawned: 'alert_writer' with pid 37
|
||||
2025-12-08 11:39:46,807 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:46,814 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:46,814 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:50,819 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.
|
||||
2025-12-11 15:42:50,826 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-12-11 15:42:50,826 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:51,186 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:51,200 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:51,200 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:52,214 INFO spawned: 'mesh' with pid 39
|
||||
2025-12-11 15:42:52,311 INFO spawned: 'alert_reader' with pid 40
|
||||
2025-12-11 15:42:52,382 INFO spawned: 'alert_writer' with pid 41
|
||||
2025-12-11 15:42:53,445 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,445 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,445 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:31,409 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.
|
||||
2025-12-14 06:18:31,418 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-12-14 06:18:31,418 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:31,759 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:31,759 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:31,761 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:32,808 INFO spawned: 'mesh' with pid 38
|
||||
2025-12-14 06:18:32,842 INFO spawned: 'alert_reader' with pid 39
|
||||
2025-12-14 06:18:32,967 INFO spawned: 'alert_writer' with pid 41
|
||||
2025-12-14 06:18:33,973 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:33,973 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:33,973 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:42,070 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.
|
||||
2025-12-15 18:35:42,112 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-12-15 18:35:42,112 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:42,455 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:42,466 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:42,469 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:43,501 INFO spawned: 'mesh' with pid 33
|
||||
2025-12-15 18:35:43,549 INFO spawned: 'alert_reader' with pid 34
|
||||
2025-12-15 18:35:43,672 INFO spawned: 'alert_writer' with pid 38
|
||||
2025-12-15 18:35:44,674 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:44,675 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:44,675 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:08,857 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.
|
||||
2025-12-18 15:23:08,863 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2025-12-18 15:23:08,863 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:09,193 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:09,193 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:09,208 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:10,211 INFO spawned: 'mesh' with pid 38
|
||||
2025-12-18 15:23:10,261 INFO spawned: 'alert_reader' with pid 39
|
||||
2025-12-18 15:23:10,386 INFO spawned: 'alert_writer' with pid 40
|
||||
2025-12-18 15:23:11,389 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,389 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,389 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,512 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,359 INFO spawned: 'mesh' with pid 61
|
||||
2025-12-18 20:53:19,359 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,438 WARN exited: alert_reader (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,438 WARN exited: alert_writer (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,451 INFO reaped unknown pid 50 (terminated by SIGTERM)
|
||||
2025-12-18 20:53:19,462 INFO reaped unknown pid 54 (terminated by SIGTERM)
|
||||
2025-12-18 20:53:19,587 INFO spawned: 'alert_reader' with pid 63
|
||||
2025-12-18 20:53:19,611 INFO spawned: 'alert_writer' with pid 64
|
||||
2025-12-18 20:53:19,653 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,859 INFO spawned: 'mesh' with pid 65
|
||||
2025-12-18 20:53:19,892 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,892 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,893 WARN exited: alert_reader (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,920 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,921 INFO waiting for mesh, alert_writer to die
|
||||
2025-12-18 20:53:19,921 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,941 WARN stopped: alert_writer (terminated by SIGTERM)
|
||||
2025-12-18 20:53:20,106 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:21,048 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.
|
||||
2026-01-25 19:02:21,055 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-01-25 19:02:21,056 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:21,102 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:21,106 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:21,107 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:22,114 INFO spawned: 'mesh' with pid 31
|
||||
2026-01-25 19:02:22,224 INFO spawned: 'alert_reader' with pid 32
|
||||
2026-01-25 19:02:22,282 INFO spawned: 'alert_writer' with pid 34
|
||||
2026-01-25 19:02:23,316 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:23,316 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:23,316 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:41,510 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.
|
||||
2026-02-04 12:30:41,531 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-02-04 12:30:41,531 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:41,868 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:41,868 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:41,896 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:42,903 INFO spawned: 'mesh' with pid 38
|
||||
2026-02-04 12:30:42,996 INFO spawned: 'alert_reader' with pid 40
|
||||
2026-02-04 12:30:43,087 INFO spawned: 'alert_writer' with pid 41
|
||||
2026-02-04 12:30:44,142 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,142 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,142 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,340 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.
|
||||
2026-02-04 14:57:35,343 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-02-04 14:57:35,343 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,709 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:35,709 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:35,710 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:36,751 INFO spawned: 'mesh' with pid 30
|
||||
2026-02-04 14:57:36,789 INFO spawned: 'alert_reader' with pid 31
|
||||
2026-02-04 14:57:36,857 INFO spawned: 'alert_writer' with pid 32
|
||||
2026-02-04 14:57:37,859 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,859 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,859 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:02,602 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.
|
||||
2026-02-04 17:31:02,612 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-02-04 17:31:02,612 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:31:02,948 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:31:02,948 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:31:02,970 INFO supervisord started with pid 1
|
||||
2026-02-04 17:31:03,977 INFO spawned: 'mesh' with pid 32
|
||||
2026-02-04 17:31:04,046 INFO spawned: 'alert_reader' with pid 33
|
||||
2026-02-04 17:31:04,097 INFO spawned: 'alert_writer' with pid 35
|
||||
2026-02-04 17:31:05,101 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:05,102 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:05,102 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:21,026 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.
|
||||
2026-02-07 14:26:21,031 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-02-07 14:26:21,031 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:21,367 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:21,388 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:21,391 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:22,400 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-07 14:26:22,536 INFO spawned: 'alert_reader' with pid 18
|
||||
2026-02-07 14:26:22,654 INFO spawned: 'alert_writer' with pid 21
|
||||
2026-02-07 14:26:23,702 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,702 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,702 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,779 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.
|
||||
2026-02-20 16:02:21,786 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-02-20 16:02:21,786 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:22,130 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:22,136 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:22,140 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:23,154 INFO spawned: 'mesh' with pid 18
|
||||
2026-02-20 16:02:23,267 INFO spawned: 'alert_reader' with pid 19
|
||||
2026-02-20 16:02:23,405 INFO spawned: 'alert_writer' with pid 20
|
||||
2026-02-20 16:02:24,446 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,446 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,446 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:30,903 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.
|
||||
2026-03-04 12:10:30,922 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-03-04 12:10:30,922 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,316 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,317 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,320 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,358 INFO spawned: 'mesh' with pid 30
|
||||
2026-03-04 12:10:32,465 INFO spawned: 'alert_reader' with pid 31
|
||||
2026-03-04 12:10:32,515 INFO spawned: 'alert_writer' with pid 32
|
||||
2026-03-04 12:10:33,564 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,572 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,596 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,418 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.
|
||||
2026-03-23 09:52:48,434 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-03-23 09:52:48,434 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:48,790 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:48,794 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:48,795 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:49,840 INFO spawned: 'mesh' with pid 33
|
||||
2026-03-23 09:52:49,904 INFO spawned: 'alert_reader' with pid 34
|
||||
2026-03-23 09:52:50,028 INFO spawned: 'alert_writer' with pid 35
|
||||
2026-03-23 09:52:51,038 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:51,038 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:51,038 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:28,400 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.
|
||||
2026-03-25 17:35:28,405 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-03-25 17:35:28,405 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:28,751 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:28,751 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:28,758 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:29,783 INFO spawned: 'mesh' with pid 32
|
||||
2026-03-25 17:35:29,902 INFO spawned: 'alert_reader' with pid 33
|
||||
2026-03-25 17:35:29,961 INFO spawned: 'alert_writer' with pid 35
|
||||
2026-03-25 17:35:30,998 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:30,998 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:30,998 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,020 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.
|
||||
2026-03-26 07:04:03,021 INFO Included extra file "/opt/supervisor.d/alert.conf" during parsing
|
||||
2026-03-26 07:04:03,022 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,384 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,385 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,385 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,418 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-26 07:04:04,449 INFO spawned: 'alert_reader' with pid 24
|
||||
2026-03-26 07:04:04,550 INFO spawned: 'alert_writer' with pid 25
|
||||
2026-03-26 07:04:05,552 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,552 INFO success: alert_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,552 INFO success: alert_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,867 @@
|
||||
2025-11-12 08:50:25,681 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.
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,681 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-11-12 08:50:25,752 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:25,756 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:25,756 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:26,765 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-12 08:50:26,804 INFO spawned: 'diag_alert' with pid 18
|
||||
2025-11-12 08:50:26,903 INFO spawned: 'dss_alert' with pid 19
|
||||
2025-11-12 08:50:27,005 INFO spawned: 'server_bidning_alert' with pid 24
|
||||
2025-11-12 08:50:27,082 INFO spawned: 'server_component_alert' with pid 25
|
||||
2025-11-12 08:50:27,221 INFO spawned: 'server_profile_alert' with pid 26
|
||||
2025-11-12 08:50:27,297 INFO spawned: 'server_sensor_alert' with pid 27
|
||||
2025-11-12 08:50:27,406 INFO spawned: 'unit_reservation_alert' with pid 28
|
||||
2025-11-12 08:50:27,555 INFO spawned: 'warehouse_reservation_alert' with pid 30
|
||||
2025-11-12 08:50:27,729 INFO spawned: 'warehouse_warranty_alert' with pid 32
|
||||
2025-11-12 08:50:28,877 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:28,877 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:25,109 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.
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,111 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-11-17 12:01:25,462 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:25,463 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:25,463 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:26,487 INFO spawned: 'mesh' with pid 23
|
||||
2025-11-17 12:01:26,588 INFO spawned: 'diag_alert' with pid 24
|
||||
2025-11-17 12:01:26,640 INFO spawned: 'dss_alert' with pid 25
|
||||
2025-11-17 12:01:26,844 INFO spawned: 'server_bidning_alert' with pid 26
|
||||
2025-11-17 12:01:26,967 INFO spawned: 'server_component_alert' with pid 28
|
||||
2025-11-17 12:01:27,116 INFO spawned: 'server_profile_alert' with pid 30
|
||||
2025-11-17 12:01:27,225 INFO spawned: 'server_sensor_alert' with pid 31
|
||||
2025-11-17 12:01:27,486 INFO spawned: 'unit_reservation_alert' with pid 32
|
||||
2025-11-17 12:01:27,633 INFO spawned: 'warehouse_reservation_alert' with pid 34
|
||||
2025-11-17 12:01:28,008 INFO spawned: 'warehouse_warranty_alert' with pid 35
|
||||
2025-11-17 12:01:29,083 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,083 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,083 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,083 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,083 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,083 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,084 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,084 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,084 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,084 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:36,168 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.
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,176 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-11-21 15:30:36,516 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:36,516 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:36,522 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:37,532 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-21 15:30:37,581 INFO spawned: 'diag_alert' with pid 27
|
||||
2025-11-21 15:30:37,770 INFO spawned: 'dss_alert' with pid 29
|
||||
2025-11-21 15:30:37,859 INFO spawned: 'server_bidning_alert' with pid 30
|
||||
2025-11-21 15:30:37,964 INFO spawned: 'server_component_alert' with pid 34
|
||||
2025-11-21 15:30:38,063 INFO spawned: 'server_profile_alert' with pid 35
|
||||
2025-11-21 15:30:38,266 INFO spawned: 'server_sensor_alert' with pid 36
|
||||
2025-11-21 15:30:38,397 INFO spawned: 'unit_reservation_alert' with pid 37
|
||||
2025-11-21 15:30:38,626 INFO spawned: 'warehouse_reservation_alert' with pid 39
|
||||
2025-11-21 15:30:38,839 INFO spawned: 'warehouse_warranty_alert' with pid 41
|
||||
2025-11-21 15:30:39,986 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,986 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:47,000 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.
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,179 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-11-22 15:19:47,609 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,609 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,631 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,708 INFO spawned: 'mesh' with pid 32
|
||||
2025-11-22 15:19:48,741 INFO spawned: 'diag_alert' with pid 33
|
||||
2025-11-22 15:19:48,820 INFO spawned: 'dss_alert' with pid 34
|
||||
2025-11-22 15:19:49,011 INFO spawned: 'server_bidning_alert' with pid 35
|
||||
2025-11-22 15:19:49,115 INFO spawned: 'server_component_alert' with pid 36
|
||||
2025-11-22 15:19:49,297 INFO spawned: 'server_profile_alert' with pid 37
|
||||
2025-11-22 15:19:49,452 INFO spawned: 'server_sensor_alert' with pid 40
|
||||
2025-11-22 15:19:49,665 INFO spawned: 'unit_reservation_alert' with pid 43
|
||||
2025-11-22 15:19:49,939 INFO spawned: 'warehouse_reservation_alert' with pid 45
|
||||
2025-11-22 15:19:50,281 INFO spawned: 'warehouse_warranty_alert' with pid 46
|
||||
2025-11-22 15:19:51,457 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,479 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,479 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,479 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,479 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,501 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,505 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,505 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,505 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,505 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:57,030 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:57,035 INFO waiting for mesh, diag_alert, dss_alert, server_bidning_alert, server_component_alert, server_profile_alert, server_sensor_alert, unit_reservation_alert, warehouse_reservation_alert, warehouse_warranty_alert to die
|
||||
2025-11-22 15:27:57,097 WARN stopped: warehouse_warranty_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:27:57,153 WARN stopped: warehouse_reservation_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:27:57,209 WARN stopped: unit_reservation_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:27:57,671 INFO stopped: server_sensor_alert (exit status 0)
|
||||
2025-11-22 15:27:57,697 WARN stopped: server_profile_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:27:57,749 WARN stopped: server_component_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:27:57,792 WARN stopped: server_bidning_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:27:58,409 INFO stopped: dss_alert (exit status 0)
|
||||
2025-11-22 15:27:58,445 WARN stopped: diag_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:27:58,726 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:34,282 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.
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,283 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-11-22 15:28:34,312 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:34,312 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:34,313 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:35,346 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:28:35,404 INFO spawned: 'diag_alert' with pid 18
|
||||
2025-11-22 15:28:35,517 INFO spawned: 'dss_alert' with pid 19
|
||||
2025-11-22 15:28:35,603 INFO spawned: 'server_bidning_alert' with pid 21
|
||||
2025-11-22 15:28:35,666 INFO spawned: 'server_component_alert' with pid 24
|
||||
2025-11-22 15:28:35,743 INFO spawned: 'server_profile_alert' with pid 25
|
||||
2025-11-22 15:28:35,858 INFO spawned: 'server_sensor_alert' with pid 27
|
||||
2025-11-22 15:28:36,013 INFO spawned: 'unit_reservation_alert' with pid 29
|
||||
2025-11-22 15:28:36,114 INFO spawned: 'warehouse_reservation_alert' with pid 30
|
||||
2025-11-22 15:28:36,459 INFO spawned: 'warehouse_warranty_alert' with pid 32
|
||||
2025-11-22 15:28:37,560 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:37,560 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:46,335 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,346 INFO waiting for mesh, diag_alert, dss_alert, server_bidning_alert, server_component_alert, server_profile_alert, server_sensor_alert, unit_reservation_alert, warehouse_reservation_alert, warehouse_warranty_alert to die
|
||||
2025-11-22 15:30:47,372 WARN stopped: warehouse_warranty_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:30:47,430 WARN stopped: warehouse_reservation_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:30:47,462 WARN stopped: unit_reservation_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:30:47,984 INFO stopped: server_sensor_alert (exit status 0)
|
||||
2025-11-22 15:30:49,023 WARN stopped: server_profile_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:30:49,038 WARN stopped: server_component_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:30:49,045 WARN stopped: server_bidning_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:30:49,222 INFO stopped: dss_alert (exit status 0)
|
||||
2025-11-22 15:30:50,244 WARN stopped: diag_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:30:50,244 INFO waiting for mesh to die
|
||||
2025-11-22 15:30:50,274 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:25,011 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.
|
||||
2025-11-22 15:31:25,021 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,025 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,025 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:25,025 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,025 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,026 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,026 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,027 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,034 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,034 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-11-22 15:31:25,059 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:25,073 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:25,079 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:26,092 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:31:26,135 INFO spawned: 'diag_alert' with pid 18
|
||||
2025-11-22 15:31:26,216 INFO spawned: 'dss_alert' with pid 19
|
||||
2025-11-22 15:31:26,267 INFO spawned: 'server_bidning_alert' with pid 20
|
||||
2025-11-22 15:31:26,367 INFO spawned: 'server_component_alert' with pid 22
|
||||
2025-11-22 15:31:26,637 INFO spawned: 'server_profile_alert' with pid 26
|
||||
2025-11-22 15:31:26,725 INFO spawned: 'server_sensor_alert' with pid 27
|
||||
2025-11-22 15:31:26,922 INFO spawned: 'unit_reservation_alert' with pid 29
|
||||
2025-11-22 15:31:27,022 INFO spawned: 'warehouse_reservation_alert' with pid 32
|
||||
2025-11-22 15:31:27,255 INFO spawned: 'warehouse_warranty_alert' with pid 34
|
||||
2025-11-22 15:31:28,366 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,366 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,366 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,366 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,366 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,366 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,367 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,367 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,367 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:28,367 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:43,051 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:43,060 INFO waiting for mesh, diag_alert, dss_alert, server_bidning_alert, server_component_alert, server_profile_alert, server_sensor_alert, unit_reservation_alert, warehouse_reservation_alert, warehouse_warranty_alert to die
|
||||
2025-11-22 15:37:43,295 WARN stopped: warehouse_warranty_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:37:43,472 WARN stopped: warehouse_reservation_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:37:43,664 WARN stopped: unit_reservation_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:37:45,050 INFO stopped: server_sensor_alert (exit status 0)
|
||||
2025-11-22 15:37:45,075 WARN stopped: server_profile_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:37:45,102 WARN stopped: server_component_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:37:45,116 WARN stopped: server_bidning_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:37:45,353 INFO stopped: dss_alert (exit status 0)
|
||||
2025-11-22 15:37:45,375 WARN stopped: diag_alert (terminated by SIGTERM)
|
||||
2025-11-22 15:37:45,447 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:35,082 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.
|
||||
2025-11-22 15:38:35,104 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,105 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-11-22 15:38:35,135 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:35,135 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:35,160 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:36,181 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:38:36,260 INFO spawned: 'diag_alert' with pid 17
|
||||
2025-11-22 15:38:36,324 INFO spawned: 'dss_alert' with pid 18
|
||||
2025-11-22 15:38:36,382 INFO spawned: 'server_bidning_alert' with pid 19
|
||||
2025-11-22 15:38:36,566 INFO spawned: 'server_component_alert' with pid 21
|
||||
2025-11-22 15:38:36,683 INFO spawned: 'server_profile_alert' with pid 24
|
||||
2025-11-22 15:38:36,818 INFO spawned: 'server_sensor_alert' with pid 26
|
||||
2025-11-22 15:38:36,938 INFO spawned: 'unit_reservation_alert' with pid 27
|
||||
2025-11-22 15:38:37,211 INFO spawned: 'warehouse_reservation_alert' with pid 30
|
||||
2025-11-22 15:38:37,413 INFO spawned: 'warehouse_warranty_alert' with pid 33
|
||||
2025-11-22 15:38:38,529 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:38,529 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:24,694 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.
|
||||
2025-11-25 15:48:24,695 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-11-25 15:48:24,695 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-11-25 15:48:24,697 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:24,698 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-11-25 15:48:24,698 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-11-25 15:48:24,698 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-11-25 15:48:24,698 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-11-25 15:48:24,698 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-11-25 15:48:24,698 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-11-25 15:48:24,698 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-11-25 15:48:25,036 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:25,037 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:25,041 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:26,051 INFO spawned: 'mesh' with pid 20
|
||||
2025-11-25 15:48:26,089 INFO spawned: 'diag_alert' with pid 21
|
||||
2025-11-25 15:48:26,133 INFO spawned: 'dss_alert' with pid 22
|
||||
2025-11-25 15:48:26,195 INFO spawned: 'server_bidning_alert' with pid 24
|
||||
2025-11-25 15:48:26,254 INFO spawned: 'server_component_alert' with pid 27
|
||||
2025-11-25 15:48:26,333 INFO spawned: 'server_profile_alert' with pid 29
|
||||
2025-11-25 15:48:26,433 INFO spawned: 'server_sensor_alert' with pid 30
|
||||
2025-11-25 15:48:26,540 INFO spawned: 'unit_reservation_alert' with pid 32
|
||||
2025-11-25 15:48:26,643 INFO spawned: 'warehouse_reservation_alert' with pid 34
|
||||
2025-11-25 15:48:26,861 INFO spawned: 'warehouse_warranty_alert' with pid 37
|
||||
2025-11-25 15:48:27,998 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,998 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:22,893 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.
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-12-07 15:52:22,920 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-12-07 15:52:23,291 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:23,291 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:23,291 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:24,316 INFO spawned: 'mesh' with pid 20
|
||||
2025-12-07 15:52:24,369 INFO spawned: 'diag_alert' with pid 21
|
||||
2025-12-07 15:52:24,412 INFO spawned: 'dss_alert' with pid 22
|
||||
2025-12-07 15:52:24,569 INFO spawned: 'server_bidning_alert' with pid 23
|
||||
2025-12-07 15:52:24,674 INFO spawned: 'server_component_alert' with pid 24
|
||||
2025-12-07 15:52:24,733 INFO spawned: 'server_profile_alert' with pid 25
|
||||
2025-12-07 15:52:24,852 INFO spawned: 'server_sensor_alert' with pid 26
|
||||
2025-12-07 15:52:25,003 INFO spawned: 'unit_reservation_alert' with pid 28
|
||||
2025-12-07 15:52:25,117 INFO spawned: 'warehouse_reservation_alert' with pid 32
|
||||
2025-12-07 15:52:25,354 INFO spawned: 'warehouse_warranty_alert' with pid 34
|
||||
2025-12-07 15:52:26,475 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,475 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:31,139 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.
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,141 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-12-08 11:39:31,469 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:31,469 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:31,470 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:32,482 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-08 11:39:32,527 INFO spawned: 'diag_alert' with pid 18
|
||||
2025-12-08 11:39:32,585 INFO spawned: 'dss_alert' with pid 19
|
||||
2025-12-08 11:39:32,622 INFO spawned: 'server_bidning_alert' with pid 20
|
||||
2025-12-08 11:39:32,677 INFO spawned: 'server_component_alert' with pid 21
|
||||
2025-12-08 11:39:32,736 INFO spawned: 'server_profile_alert' with pid 22
|
||||
2025-12-08 11:39:32,838 INFO spawned: 'server_sensor_alert' with pid 23
|
||||
2025-12-08 11:39:32,925 INFO spawned: 'unit_reservation_alert' with pid 25
|
||||
2025-12-08 11:39:33,087 INFO spawned: 'warehouse_reservation_alert' with pid 30
|
||||
2025-12-08 11:39:33,333 INFO spawned: 'warehouse_warranty_alert' with pid 31
|
||||
2025-12-08 11:39:34,397 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,397 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,571 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.
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,592 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-12-11 15:42:42,937 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:42,937 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:42,938 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:43,949 INFO spawned: 'mesh' with pid 20
|
||||
2025-12-11 15:42:44,031 INFO spawned: 'diag_alert' with pid 21
|
||||
2025-12-11 15:42:44,058 INFO spawned: 'dss_alert' with pid 22
|
||||
2025-12-11 15:42:44,204 INFO spawned: 'server_bidning_alert' with pid 23
|
||||
2025-12-11 15:42:44,338 INFO spawned: 'server_component_alert' with pid 27
|
||||
2025-12-11 15:42:44,491 INFO spawned: 'server_profile_alert' with pid 29
|
||||
2025-12-11 15:42:44,647 INFO spawned: 'server_sensor_alert' with pid 30
|
||||
2025-12-11 15:42:44,828 INFO spawned: 'unit_reservation_alert' with pid 31
|
||||
2025-12-11 15:42:45,078 INFO spawned: 'warehouse_reservation_alert' with pid 34
|
||||
2025-12-11 15:42:45,296 INFO spawned: 'warehouse_warranty_alert' with pid 35
|
||||
2025-12-11 15:42:46,391 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,392 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:25,878 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.
|
||||
2025-12-14 06:18:25,883 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-12-14 06:18:25,884 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-12-14 06:18:26,220 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:26,221 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:26,221 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:27,227 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-14 06:18:27,337 INFO spawned: 'diag_alert' with pid 18
|
||||
2025-12-14 06:18:27,383 INFO spawned: 'dss_alert' with pid 20
|
||||
2025-12-14 06:18:27,471 INFO spawned: 'server_bidning_alert' with pid 21
|
||||
2025-12-14 06:18:27,668 INFO spawned: 'server_component_alert' with pid 24
|
||||
2025-12-14 06:18:27,759 INFO spawned: 'server_profile_alert' with pid 26
|
||||
2025-12-14 06:18:27,914 INFO spawned: 'server_sensor_alert' with pid 27
|
||||
2025-12-14 06:18:28,007 INFO spawned: 'unit_reservation_alert' with pid 28
|
||||
2025-12-14 06:18:28,217 INFO spawned: 'warehouse_reservation_alert' with pid 29
|
||||
2025-12-14 06:18:28,354 INFO spawned: 'warehouse_warranty_alert' with pid 30
|
||||
2025-12-14 06:18:29,455 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:29,455 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:35,042 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.
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,055 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-12-15 18:35:35,411 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:35,411 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:35,412 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:36,434 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-15 18:35:36,460 INFO spawned: 'diag_alert' with pid 18
|
||||
2025-12-15 18:35:36,578 INFO spawned: 'dss_alert' with pid 20
|
||||
2025-12-15 18:35:36,668 INFO spawned: 'server_bidning_alert' with pid 21
|
||||
2025-12-15 18:35:36,772 INFO spawned: 'server_component_alert' with pid 25
|
||||
2025-12-15 18:35:36,892 INFO spawned: 'server_profile_alert' with pid 26
|
||||
2025-12-15 18:35:37,043 INFO spawned: 'server_sensor_alert' with pid 27
|
||||
2025-12-15 18:35:37,157 INFO spawned: 'unit_reservation_alert' with pid 28
|
||||
2025-12-15 18:35:37,378 INFO spawned: 'warehouse_reservation_alert' with pid 31
|
||||
2025-12-15 18:35:37,690 INFO spawned: 'warehouse_warranty_alert' with pid 32
|
||||
2025-12-15 18:35:38,738 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,738 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:00,726 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.
|
||||
2025-12-18 15:23:00,734 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2025-12-18 15:23:00,735 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2025-12-18 15:23:01,088 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:01,088 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:01,089 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:02,096 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-18 15:23:02,178 INFO spawned: 'diag_alert' with pid 18
|
||||
2025-12-18 15:23:02,266 INFO spawned: 'dss_alert' with pid 21
|
||||
2025-12-18 15:23:02,294 INFO spawned: 'server_bidning_alert' with pid 22
|
||||
2025-12-18 15:23:02,471 INFO spawned: 'server_component_alert' with pid 23
|
||||
2025-12-18 15:23:02,584 INFO spawned: 'server_profile_alert' with pid 25
|
||||
2025-12-18 15:23:02,717 INFO spawned: 'server_sensor_alert' with pid 27
|
||||
2025-12-18 15:23:02,863 INFO spawned: 'unit_reservation_alert' with pid 29
|
||||
2025-12-18 15:23:03,046 INFO spawned: 'warehouse_reservation_alert' with pid 32
|
||||
2025-12-18 15:23:03,222 INFO spawned: 'warehouse_warranty_alert' with pid 33
|
||||
2025-12-18 15:23:04,371 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,372 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,050 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,056 INFO waiting for mesh, diag_alert, dss_alert, server_bidning_alert, server_component_alert, server_profile_alert, server_sensor_alert, unit_reservation_alert, warehouse_reservation_alert, warehouse_warranty_alert to die
|
||||
2025-12-18 20:53:20,121 WARN exited: server_bidning_alert (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:20,183 WARN exited: diag_alert (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:20,184 WARN stopped: warehouse_warranty_alert (terminated by SIGTERM)
|
||||
2025-12-18 20:53:20,235 WARN exited: server_profile_alert (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:20,235 WARN exited: unit_reservation_alert (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:20,235 WARN stopped: warehouse_reservation_alert (terminated by SIGTERM)
|
||||
2025-12-18 20:53:20,503 WARN exited: server_component_alert (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:23,680 INFO waiting for mesh, dss_alert, server_sensor_alert to die
|
||||
2025-12-18 20:53:26,685 INFO waiting for mesh, dss_alert, server_sensor_alert to die
|
||||
2025-12-18 20:53:29,692 INFO waiting for mesh, dss_alert, server_sensor_alert to die
|
||||
2025-12-18 20:53:30,694 WARN killing 'server_sensor_alert' (27) with SIGKILL
|
||||
2025-12-18 20:53:30,695 WARN stopped: server_sensor_alert (terminated by SIGKILL)
|
||||
2026-01-25 19:02:18,558 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.
|
||||
2026-01-25 19:02:18,563 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,563 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,563 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:18,563 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,564 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,564 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,564 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,564 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,564 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,564 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-01-25 19:02:18,922 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:18,922 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:18,926 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:19,939 INFO spawned: 'mesh' with pid 23
|
||||
2026-01-25 19:02:20,041 INFO spawned: 'diag_alert' with pid 24
|
||||
2026-01-25 19:02:20,087 INFO spawned: 'dss_alert' with pid 25
|
||||
2026-01-25 19:02:20,234 INFO spawned: 'server_bidning_alert' with pid 26
|
||||
2026-01-25 19:02:20,336 INFO spawned: 'server_component_alert' with pid 27
|
||||
2026-01-25 19:02:20,598 INFO spawned: 'server_profile_alert' with pid 32
|
||||
2026-01-25 19:02:20,757 INFO spawned: 'server_sensor_alert' with pid 33
|
||||
2026-01-25 19:02:20,963 INFO spawned: 'unit_reservation_alert' with pid 35
|
||||
2026-01-25 19:02:21,170 INFO spawned: 'warehouse_reservation_alert' with pid 37
|
||||
2026-01-25 19:02:21,744 INFO spawned: 'warehouse_warranty_alert' with pid 40
|
||||
2026-01-25 19:02:22,917 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,917 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,917 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,917 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,917 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,917 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,917 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,917 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,917 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,918 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:22,789 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.
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-02-04 12:30:22,793 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-02-04 12:30:23,114 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:23,115 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:23,117 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:24,129 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 12:30:24,154 INFO spawned: 'diag_alert' with pid 18
|
||||
2026-02-04 12:30:24,180 INFO spawned: 'dss_alert' with pid 19
|
||||
2026-02-04 12:30:24,260 INFO spawned: 'server_bidning_alert' with pid 21
|
||||
2026-02-04 12:30:24,299 INFO spawned: 'server_component_alert' with pid 24
|
||||
2026-02-04 12:30:24,374 INFO spawned: 'server_profile_alert' with pid 26
|
||||
2026-02-04 12:30:24,444 INFO spawned: 'server_sensor_alert' with pid 27
|
||||
2026-02-04 12:30:24,563 INFO spawned: 'unit_reservation_alert' with pid 31
|
||||
2026-02-04 12:30:24,624 INFO spawned: 'warehouse_reservation_alert' with pid 32
|
||||
2026-02-04 12:30:24,707 INFO spawned: 'warehouse_warranty_alert' with pid 34
|
||||
2026-02-04 12:30:25,780 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,780 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,780 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,780 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,780 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,780 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,781 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,781 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,781 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,781 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,826 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.
|
||||
2026-02-04 14:57:35,828 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-02-04 14:57:35,829 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-02-04 14:57:36,162 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,162 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,162 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,195 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 14:57:37,295 INFO spawned: 'diag_alert' with pid 18
|
||||
2026-02-04 14:57:37,358 INFO spawned: 'dss_alert' with pid 20
|
||||
2026-02-04 14:57:37,423 INFO spawned: 'server_bidning_alert' with pid 21
|
||||
2026-02-04 14:57:37,543 INFO spawned: 'server_component_alert' with pid 23
|
||||
2026-02-04 14:57:37,662 INFO spawned: 'server_profile_alert' with pid 24
|
||||
2026-02-04 14:57:37,742 INFO spawned: 'server_sensor_alert' with pid 25
|
||||
2026-02-04 14:57:37,871 INFO spawned: 'unit_reservation_alert' with pid 26
|
||||
2026-02-04 14:57:38,005 INFO spawned: 'warehouse_reservation_alert' with pid 27
|
||||
2026-02-04 14:57:38,167 INFO spawned: 'warehouse_warranty_alert' with pid 31
|
||||
2026-02-04 14:57:39,359 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,360 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:49,807 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.
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-02-04 17:30:49,810 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-02-04 17:30:50,131 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:50,131 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:50,131 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:51,147 INFO spawned: 'mesh' with pid 26
|
||||
2026-02-04 17:30:51,200 INFO spawned: 'diag_alert' with pid 27
|
||||
2026-02-04 17:30:51,270 INFO spawned: 'dss_alert' with pid 28
|
||||
2026-02-04 17:30:51,367 INFO spawned: 'server_bidning_alert' with pid 29
|
||||
2026-02-04 17:30:51,458 INFO spawned: 'server_component_alert' with pid 30
|
||||
2026-02-04 17:30:51,561 INFO spawned: 'server_profile_alert' with pid 31
|
||||
2026-02-04 17:30:51,714 INFO spawned: 'server_sensor_alert' with pid 33
|
||||
2026-02-04 17:30:51,978 INFO spawned: 'unit_reservation_alert' with pid 34
|
||||
2026-02-04 17:30:52,185 INFO spawned: 'warehouse_reservation_alert' with pid 38
|
||||
2026-02-04 17:30:52,521 INFO spawned: 'warehouse_warranty_alert' with pid 40
|
||||
2026-02-04 17:30:53,734 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,734 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:20,562 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.
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,571 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-02-07 14:26:20,899 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,899 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,899 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,910 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-07 14:26:21,988 INFO spawned: 'diag_alert' with pid 18
|
||||
2026-02-07 14:26:22,078 INFO spawned: 'dss_alert' with pid 19
|
||||
2026-02-07 14:26:22,229 INFO spawned: 'server_bidning_alert' with pid 20
|
||||
2026-02-07 14:26:22,327 INFO spawned: 'server_component_alert' with pid 22
|
||||
2026-02-07 14:26:22,407 INFO spawned: 'server_profile_alert' with pid 24
|
||||
2026-02-07 14:26:22,675 INFO spawned: 'server_sensor_alert' with pid 25
|
||||
2026-02-07 14:26:22,779 INFO spawned: 'unit_reservation_alert' with pid 28
|
||||
2026-02-07 14:26:22,843 INFO spawned: 'warehouse_reservation_alert' with pid 29
|
||||
2026-02-07 14:26:23,028 INFO spawned: 'warehouse_warranty_alert' with pid 31
|
||||
2026-02-07 14:26:24,209 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,211 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,211 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,236 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,236 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,236 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,283 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,283 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,283 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,283 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:20,797 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.
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-02-20 16:02:20,829 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-02-20 16:02:21,171 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,171 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,172 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,191 INFO spawned: 'mesh' with pid 26
|
||||
2026-02-20 16:02:22,237 INFO spawned: 'diag_alert' with pid 27
|
||||
2026-02-20 16:02:22,285 INFO spawned: 'dss_alert' with pid 28
|
||||
2026-02-20 16:02:22,392 INFO spawned: 'server_bidning_alert' with pid 29
|
||||
2026-02-20 16:02:22,617 INFO spawned: 'server_component_alert' with pid 31
|
||||
2026-02-20 16:02:22,802 INFO spawned: 'server_profile_alert' with pid 34
|
||||
2026-02-20 16:02:22,984 INFO spawned: 'server_sensor_alert' with pid 36
|
||||
2026-02-20 16:02:23,138 INFO spawned: 'unit_reservation_alert' with pid 37
|
||||
2026-02-20 16:02:23,422 INFO spawned: 'warehouse_reservation_alert' with pid 38
|
||||
2026-02-20 16:02:23,667 INFO spawned: 'warehouse_warranty_alert' with pid 40
|
||||
2026-02-20 16:02:24,765 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,765 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:31,347 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.
|
||||
2026-03-04 12:10:31,357 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,358 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,363 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,363 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,363 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,363 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,363 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,363 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,363 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,363 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-03-04 12:10:31,710 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,715 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,715 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,758 INFO spawned: 'mesh' with pid 26
|
||||
2026-03-04 12:10:32,863 INFO spawned: 'diag_alert' with pid 27
|
||||
2026-03-04 12:10:32,961 INFO spawned: 'dss_alert' with pid 28
|
||||
2026-03-04 12:10:33,128 INFO spawned: 'server_bidning_alert' with pid 30
|
||||
2026-03-04 12:10:33,239 INFO spawned: 'server_component_alert' with pid 32
|
||||
2026-03-04 12:10:33,465 INFO spawned: 'server_profile_alert' with pid 35
|
||||
2026-03-04 12:10:33,751 INFO spawned: 'server_sensor_alert' with pid 36
|
||||
2026-03-04 12:10:33,954 INFO spawned: 'unit_reservation_alert' with pid 37
|
||||
2026-03-04 12:10:34,083 INFO spawned: 'warehouse_reservation_alert' with pid 38
|
||||
2026-03-04 12:10:34,410 INFO spawned: 'warehouse_warranty_alert' with pid 40
|
||||
2026-03-04 12:10:35,556 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,560 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:44,965 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.
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-03-23 09:52:44,967 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-03-23 09:52:45,302 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:45,303 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:45,303 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:46,329 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-23 09:52:46,408 INFO spawned: 'diag_alert' with pid 24
|
||||
2026-03-23 09:52:46,522 INFO spawned: 'dss_alert' with pid 25
|
||||
2026-03-23 09:52:46,710 INFO spawned: 'server_bidning_alert' with pid 27
|
||||
2026-03-23 09:52:46,801 INFO spawned: 'server_component_alert' with pid 28
|
||||
2026-03-23 09:52:46,908 INFO spawned: 'server_profile_alert' with pid 30
|
||||
2026-03-23 09:52:47,123 INFO spawned: 'server_sensor_alert' with pid 33
|
||||
2026-03-23 09:52:47,371 INFO spawned: 'unit_reservation_alert' with pid 34
|
||||
2026-03-23 09:52:47,561 INFO spawned: 'warehouse_reservation_alert' with pid 35
|
||||
2026-03-23 09:52:47,730 INFO spawned: 'warehouse_warranty_alert' with pid 37
|
||||
2026-03-23 09:52:48,772 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,772 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:15,113 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.
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,115 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-03-25 17:35:15,429 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:15,430 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:15,430 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:16,435 INFO spawned: 'mesh' with pid 16
|
||||
2026-03-25 17:35:16,477 INFO spawned: 'diag_alert' with pid 17
|
||||
2026-03-25 17:35:16,524 INFO spawned: 'dss_alert' with pid 18
|
||||
2026-03-25 17:35:16,575 INFO spawned: 'server_bidning_alert' with pid 22
|
||||
2026-03-25 17:35:16,656 INFO spawned: 'server_component_alert' with pid 23
|
||||
2026-03-25 17:35:16,770 INFO spawned: 'server_profile_alert' with pid 25
|
||||
2026-03-25 17:35:16,872 INFO spawned: 'server_sensor_alert' with pid 26
|
||||
2026-03-25 17:35:16,956 INFO spawned: 'unit_reservation_alert' with pid 28
|
||||
2026-03-25 17:35:17,079 INFO spawned: 'warehouse_reservation_alert' with pid 31
|
||||
2026-03-25 17:35:17,276 INFO spawned: 'warehouse_warranty_alert' with pid 33
|
||||
2026-03-25 17:35:18,372 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:18,372 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,058 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.
|
||||
2026-03-26 07:04:03,074 INFO Included extra file "/opt/supervisor.d/diag_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,074 INFO Included extra file "/opt/supervisor.d/dss_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,074 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,074 INFO Included extra file "/opt/supervisor.d/server_binding_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,075 INFO Included extra file "/opt/supervisor.d/server_component_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,075 INFO Included extra file "/opt/supervisor.d/server_profile_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,075 INFO Included extra file "/opt/supervisor.d/server_sensor_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,075 INFO Included extra file "/opt/supervisor.d/unit_reservation_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,075 INFO Included extra file "/opt/supervisor.d/warehouse_reservation_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,075 INFO Included extra file "/opt/supervisor.d/warehouse_warranty_alert.conf" during parsing
|
||||
2026-03-26 07:04:03,409 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,409 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,440 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,442 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-26 07:04:04,511 INFO spawned: 'diag_alert' with pid 25
|
||||
2026-03-26 07:04:04,597 INFO spawned: 'dss_alert' with pid 26
|
||||
2026-03-26 07:04:04,787 INFO spawned: 'server_bidning_alert' with pid 27
|
||||
2026-03-26 07:04:04,857 INFO spawned: 'server_component_alert' with pid 31
|
||||
2026-03-26 07:04:04,980 INFO spawned: 'server_profile_alert' with pid 32
|
||||
2026-03-26 07:04:05,062 INFO spawned: 'server_sensor_alert' with pid 33
|
||||
2026-03-26 07:04:05,275 INFO spawned: 'unit_reservation_alert' with pid 34
|
||||
2026-03-26 07:04:05,465 INFO spawned: 'warehouse_reservation_alert' with pid 36
|
||||
2026-03-26 07:04:05,737 INFO spawned: 'warehouse_warranty_alert' with pid 37
|
||||
2026-03-26 07:04:06,855 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: diag_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: dss_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: server_bidning_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: server_component_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: server_profile_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: server_sensor_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: unit_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: warehouse_reservation_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,917 INFO success: warehouse_warranty_alert entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,271 @@
|
||||
2025-11-22 15:38:24,964 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.
|
||||
2025-11-22 15:38:24,964 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2025-11-22 15:38:24,964 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:25,024 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:25,040 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:25,041 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:26,045 INFO spawned: 'mesh' with pid 18
|
||||
2025-11-22 15:38:26,157 INFO spawned: 'compat_auth_reader' with pid 19
|
||||
2025-11-22 15:38:26,235 INFO spawned: 'compat_auth_writer' with pid 20
|
||||
2025-11-22 15:38:27,251 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:27,279 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:27,279 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,899 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.
|
||||
2025-11-25 15:48:27,903 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2025-11-25 15:48:27,903 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:28,281 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:28,281 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:28,281 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:29,297 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-25 15:48:29,412 INFO spawned: 'compat_auth_reader' with pid 29
|
||||
2025-11-25 15:48:29,499 INFO spawned: 'compat_auth_writer' with pid 30
|
||||
2025-11-25 15:48:30,591 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,591 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,591 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:24,440 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.
|
||||
2025-12-07 15:52:24,445 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2025-12-07 15:52:24,445 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:24,805 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:24,815 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:24,818 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:25,849 INFO spawned: 'mesh' with pid 33
|
||||
2025-12-07 15:52:25,912 INFO spawned: 'compat_auth_reader' with pid 34
|
||||
2025-12-07 15:52:26,000 INFO spawned: 'compat_auth_writer' with pid 35
|
||||
2025-12-07 15:52:27,054 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,054 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,054 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:44,311 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.
|
||||
2025-12-08 11:39:44,313 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2025-12-08 11:39:44,313 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:44,676 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:44,676 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:44,677 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:45,687 INFO spawned: 'mesh' with pid 40
|
||||
2025-12-08 11:39:45,818 INFO spawned: 'compat_auth_reader' with pid 41
|
||||
2025-12-08 11:39:45,923 INFO spawned: 'compat_auth_writer' with pid 42
|
||||
2025-12-08 11:39:47,006 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:47,006 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:47,006 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:50,508 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.
|
||||
2025-12-11 15:42:50,518 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2025-12-11 15:42:50,530 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:50,947 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:50,947 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:50,952 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:51,964 INFO spawned: 'mesh' with pid 40
|
||||
2025-12-11 15:42:52,006 INFO spawned: 'compat_auth_reader' with pid 41
|
||||
2025-12-11 15:42:52,076 INFO spawned: 'compat_auth_writer' with pid 42
|
||||
2025-12-11 15:42:53,151 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,151 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,151 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:31,372 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.
|
||||
2025-12-14 06:18:31,377 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2025-12-14 06:18:31,379 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:31,741 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:31,741 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:31,755 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:32,763 INFO spawned: 'mesh' with pid 41
|
||||
2025-12-14 06:18:32,833 INFO spawned: 'compat_auth_reader' with pid 42
|
||||
2025-12-14 06:18:32,918 INFO spawned: 'compat_auth_writer' with pid 43
|
||||
2025-12-14 06:18:33,919 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:33,919 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:33,919 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:40,644 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.
|
||||
2025-12-15 18:35:40,646 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2025-12-15 18:35:40,646 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:40,965 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:40,984 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:40,984 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:41,988 INFO spawned: 'mesh' with pid 47
|
||||
2025-12-15 18:35:42,098 INFO spawned: 'compat_auth_reader' with pid 48
|
||||
2025-12-15 18:35:42,167 INFO spawned: 'compat_auth_writer' with pid 49
|
||||
2025-12-15 18:35:43,243 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:43,243 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:43,243 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:06,579 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.
|
||||
2025-12-18 15:23:06,580 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2025-12-18 15:23:06,580 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:06,893 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:06,894 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:06,894 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:07,932 INFO spawned: 'mesh' with pid 38
|
||||
2025-12-18 15:23:07,964 INFO spawned: 'compat_auth_reader' with pid 39
|
||||
2025-12-18 15:23:08,055 INFO spawned: 'compat_auth_writer' with pid 40
|
||||
2025-12-18 15:23:09,066 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:09,066 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:09,066 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,108 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:16,612 INFO spawned: 'mesh' with pid 63
|
||||
2025-12-18 20:53:16,895 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,923 WARN exited: compat_auth_writer (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:16,923 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,923 INFO reaped unknown pid 52 (exit status 0)
|
||||
2025-12-18 20:53:17,934 INFO spawned: 'mesh' with pid 65
|
||||
2025-12-18 20:53:18,008 INFO spawned: 'compat_auth_writer' with pid 66
|
||||
2025-12-18 20:53:18,026 WARN exited: compat_auth_reader (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:18,097 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,153 INFO spawned: 'compat_auth_reader' with pid 68
|
||||
2025-12-18 20:53:18,153 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,158 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,205 INFO spawned: 'mesh' with pid 69
|
||||
2025-12-18 20:53:18,246 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,285 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,366 WARN exited: compat_auth_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,369 WARN exited: compat_auth_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,409 INFO spawned: 'compat_auth_reader' with pid 73
|
||||
2025-12-18 20:53:18,458 INFO spawned: 'compat_auth_writer' with pid 74
|
||||
2025-12-18 20:53:18,518 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,583 INFO spawned: 'mesh' with pid 76
|
||||
2025-12-18 20:53:18,611 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,640 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,641 WARN exited: compat_auth_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,641 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,768 INFO spawned: 'compat_auth_reader' with pid 78
|
||||
2025-12-18 20:53:18,769 WARN exited: compat_auth_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,769 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,865 INFO spawned: 'compat_auth_writer' with pid 80
|
||||
2025-12-18 20:53:18,870 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,962 INFO spawned: 'mesh' with pid 82
|
||||
2025-12-18 20:53:18,963 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,966 WARN exited: compat_auth_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,966 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,020 INFO spawned: 'compat_auth_reader' with pid 84
|
||||
2025-12-18 20:53:19,112 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,120 WARN exited: compat_auth_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,219 INFO spawned: 'compat_auth_writer' with pid 86
|
||||
2025-12-18 20:53:19,346 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,346 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,397 INFO spawned: 'mesh' with pid 88
|
||||
2025-12-18 20:53:19,440 WARN exited: compat_auth_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,570 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,623 INFO spawned: 'compat_auth_reader' with pid 90
|
||||
2025-12-18 20:53:19,642 WARN exited: compat_auth_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,778 WARN exited: mesh (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,843 INFO spawned: 'mesh' with pid 92
|
||||
2025-12-18 20:53:20,052 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,089 INFO spawned: 'compat_auth_writer' with pid 95
|
||||
2025-12-18 20:53:20,155 WARN exited: compat_auth_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:20,213 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:20,239 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,239 INFO waiting for compat_auth_writer to die
|
||||
2025-12-18 20:53:20,321 WARN stopped: compat_auth_writer (terminated by SIGTERM)
|
||||
2026-01-25 19:02:20,575 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.
|
||||
2026-01-25 19:02:20,580 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-01-25 19:02:20,581 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:20,633 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:20,633 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:20,634 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:21,655 INFO spawned: 'mesh' with pid 23
|
||||
2026-01-25 19:02:21,772 INFO spawned: 'compat_auth_reader' with pid 24
|
||||
2026-01-25 19:02:21,884 INFO spawned: 'compat_auth_writer' with pid 25
|
||||
2026-01-25 19:02:22,900 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,900 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,900 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:41,095 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.
|
||||
2026-02-04 12:30:41,102 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-02-04 12:30:41,102 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:41,476 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:41,476 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:41,496 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:42,504 INFO spawned: 'mesh' with pid 42
|
||||
2026-02-04 12:30:42,607 INFO spawned: 'compat_auth_reader' with pid 43
|
||||
2026-02-04 12:30:42,682 INFO spawned: 'compat_auth_writer' with pid 44
|
||||
2026-02-04 12:30:43,725 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:43,730 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:43,730 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,644 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.
|
||||
2026-02-04 14:57:35,651 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-02-04 14:57:35,651 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:36,031 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,031 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,048 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,050 INFO spawned: 'mesh' with pid 32
|
||||
2026-02-04 14:57:37,102 INFO spawned: 'compat_auth_reader' with pid 33
|
||||
2026-02-04 14:57:37,170 INFO spawned: 'compat_auth_writer' with pid 34
|
||||
2026-02-04 14:57:38,219 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,219 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,219 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:03,023 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.
|
||||
2026-02-04 17:31:03,026 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-02-04 17:31:03,026 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:31:03,398 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:31:03,398 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:31:03,399 INFO supervisord started with pid 1
|
||||
2026-02-04 17:31:04,412 INFO spawned: 'mesh' with pid 45
|
||||
2026-02-04 17:31:04,484 INFO spawned: 'compat_auth_reader' with pid 46
|
||||
2026-02-04 17:31:04,592 INFO spawned: 'compat_auth_writer' with pid 47
|
||||
2026-02-04 17:31:05,604 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:05,604 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:05,604 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:20,156 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.
|
||||
2026-02-07 14:26:20,162 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-02-07 14:26:20,167 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:20,522 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,522 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,523 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,534 INFO spawned: 'mesh' with pid 27
|
||||
2026-02-07 14:26:21,640 INFO spawned: 'compat_auth_reader' with pid 28
|
||||
2026-02-07 14:26:21,708 INFO spawned: 'compat_auth_writer' with pid 29
|
||||
2026-02-07 14:26:22,749 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,749 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,749 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,919 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.
|
||||
2026-02-20 16:02:21,926 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-02-20 16:02:21,926 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:22,271 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:22,271 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:22,272 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:23,286 INFO spawned: 'mesh' with pid 18
|
||||
2026-02-20 16:02:23,393 INFO spawned: 'compat_auth_reader' with pid 19
|
||||
2026-02-20 16:02:23,509 INFO spawned: 'compat_auth_writer' with pid 20
|
||||
2026-02-20 16:02:24,560 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,561 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,561 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:30,957 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.
|
||||
2026-03-04 12:10:30,971 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-03-04 12:10:30,971 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,332 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,332 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,335 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,341 INFO spawned: 'mesh' with pid 21
|
||||
2026-03-04 12:10:32,410 INFO spawned: 'compat_auth_reader' with pid 22
|
||||
2026-03-04 12:10:32,477 INFO spawned: 'compat_auth_writer' with pid 23
|
||||
2026-03-04 12:10:33,508 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,509 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,509 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,395 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.
|
||||
2026-03-23 09:52:48,401 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-03-23 09:52:48,402 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:48,750 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:48,750 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:48,750 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:49,799 INFO spawned: 'mesh' with pid 32
|
||||
2026-03-23 09:52:49,908 INFO spawned: 'compat_auth_reader' with pid 33
|
||||
2026-03-23 09:52:49,958 INFO spawned: 'compat_auth_writer' with pid 34
|
||||
2026-03-23 09:52:51,014 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:51,015 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:51,015 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:27,447 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.
|
||||
2026-03-25 17:35:27,456 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-03-25 17:35:27,457 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:27,797 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:27,814 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:27,817 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:28,828 INFO spawned: 'mesh' with pid 30
|
||||
2026-03-25 17:35:28,892 INFO spawned: 'compat_auth_reader' with pid 31
|
||||
2026-03-25 17:35:28,949 INFO spawned: 'compat_auth_writer' with pid 32
|
||||
2026-03-25 17:35:29,985 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:29,985 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:29,986 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,035 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.
|
||||
2026-03-26 07:04:03,064 INFO Included extra file "/opt/supervisor.d/compat_auth.conf" during parsing
|
||||
2026-03-26 07:04:03,073 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,440 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,440 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,444 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,457 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-26 07:04:04,513 INFO spawned: 'compat_auth_reader' with pid 24
|
||||
2026-03-26 07:04:04,597 INFO spawned: 'compat_auth_writer' with pid 25
|
||||
2026-03-26 07:04:05,687 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,687 INFO success: compat_auth_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,687 INFO success: compat_auth_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,493 @@
|
||||
2025-11-12 08:50:19,203 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.
|
||||
2025-11-12 08:50:19,203 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-11-12 08:50:19,203 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-12 08:50:19,203 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:19,203 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-11-12 08:50:19,232 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:19,232 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:19,233 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:20,280 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-12 08:50:20,405 INFO spawned: 'backup' with pid 20
|
||||
2025-11-12 08:50:20,456 INFO spawned: 'cron' with pid 21
|
||||
2025-11-12 08:50:20,491 INFO spawned: 'task_sync' with pid 22
|
||||
2025-11-12 08:50:21,511 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,511 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,511 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,511 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-12 08:50:28,979 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:50:29,987 INFO spawned: 'task_sync' with pid 32
|
||||
2025-11-12 08:50:31,012 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-12 08:50:35,869 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:50:36,886 INFO spawned: 'task_sync' with pid 39
|
||||
2025-11-12 08:50:37,910 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-12 08:50:42,883 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:50:43,887 INFO spawned: 'task_sync' with pid 46
|
||||
2025-11-12 08:50:44,889 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-12 08:50:46,444 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:50:47,447 INFO spawned: 'task_sync' with pid 53
|
||||
2025-11-12 08:50:48,468 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-12 08:50:50,909 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:50:51,923 INFO spawned: 'task_sync' with pid 60
|
||||
2025-11-12 08:50:52,937 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-12 08:50:54,314 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:50:55,320 INFO spawned: 'task_sync' with pid 67
|
||||
2025-11-12 08:50:56,333 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-12 08:50:57,712 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:50:58,728 INFO spawned: 'task_sync' with pid 74
|
||||
2025-11-12 08:50:59,531 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:51:00,533 INFO spawned: 'task_sync' with pid 81
|
||||
2025-11-12 08:51:01,304 WARN exited: task_sync (exit status 1; not expected)
|
||||
2025-11-12 08:51:02,311 INFO gave up: task_sync entered FATAL state, too many start retries too quickly
|
||||
2025-11-17 12:01:25,263 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.
|
||||
2025-11-17 12:01:25,284 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-11-17 12:01:25,284 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-17 12:01:25,284 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:25,284 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-11-17 12:01:25,644 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:25,644 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:25,644 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:26,674 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-17 12:01:26,715 INFO spawned: 'backup' with pid 17
|
||||
2025-11-17 12:01:26,807 INFO spawned: 'cron' with pid 18
|
||||
2025-11-17 12:01:26,938 INFO spawned: 'task_sync' with pid 19
|
||||
2025-11-17 12:01:27,972 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:27,986 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:27,986 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:27,986 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-17 12:01:37,413 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-11-21 15:30:35,605 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.
|
||||
2025-11-21 15:30:35,612 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-11-21 15:30:35,612 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-21 15:30:35,612 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:35,612 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-11-21 15:30:35,960 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:35,960 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:35,960 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:36,977 INFO spawned: 'mesh' with pid 24
|
||||
2025-11-21 15:30:37,031 INFO spawned: 'backup' with pid 25
|
||||
2025-11-21 15:30:37,078 INFO spawned: 'cron' with pid 26
|
||||
2025-11-21 15:30:37,121 INFO spawned: 'task_sync' with pid 28
|
||||
2025-11-21 15:30:38,188 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,188 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,189 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,189 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-21 15:30:45,778 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-11-22 15:19:46,679 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.
|
||||
2025-11-22 15:19:46,682 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-11-22 15:19:46,682 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-22 15:19:46,682 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:46,682 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-11-22 15:19:47,162 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,162 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,162 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,184 INFO spawned: 'mesh' with pid 19
|
||||
2025-11-22 15:19:48,259 INFO spawned: 'backup' with pid 20
|
||||
2025-11-22 15:19:48,341 INFO spawned: 'cron' with pid 21
|
||||
2025-11-22 15:19:48,473 INFO spawned: 'task_sync' with pid 22
|
||||
2025-11-22 15:19:49,520 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,520 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,521 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,521 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-22 15:19:57,703 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-11-22 15:27:58,292 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:58,309 INFO waiting for mesh, backup, cron to die
|
||||
2025-11-22 15:27:59,325 WARN stopped: cron (terminated by SIGTERM)
|
||||
2025-11-22 15:27:59,460 INFO stopped: backup (exit status 0)
|
||||
2025-11-22 15:27:59,542 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:23,198 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.
|
||||
2025-11-22 15:28:23,198 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-11-22 15:28:23,198 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-22 15:28:23,198 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:23,198 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-11-22 15:28:23,226 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:23,226 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:23,226 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:24,234 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:28:24,257 INFO spawned: 'backup' with pid 17
|
||||
2025-11-22 15:28:24,285 INFO spawned: 'cron' with pid 18
|
||||
2025-11-22 15:28:24,304 INFO spawned: 'task_sync' with pid 19
|
||||
2025-11-22 15:28:25,318 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,318 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,318 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,318 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-22 15:28:33,265 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-11-22 15:30:46,469 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,483 INFO waiting for mesh, backup, cron to die
|
||||
2025-11-22 15:30:47,499 WARN stopped: cron (terminated by SIGTERM)
|
||||
2025-11-22 15:30:47,702 INFO stopped: backup (exit status 0)
|
||||
2025-11-22 15:30:47,898 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:17,689 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.
|
||||
2025-11-22 15:31:17,689 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-11-22 15:31:17,690 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-22 15:31:17,690 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:17,690 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-11-22 15:31:17,714 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:17,717 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:17,717 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:18,733 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:31:18,798 INFO spawned: 'backup' with pid 17
|
||||
2025-11-22 15:31:18,852 INFO spawned: 'cron' with pid 18
|
||||
2025-11-22 15:31:18,928 INFO spawned: 'task_sync' with pid 22
|
||||
2025-11-22 15:31:19,996 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,996 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,996 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,996 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-22 15:31:29,387 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-11-22 15:37:42,805 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:42,810 INFO waiting for mesh, backup, cron to die
|
||||
2025-11-22 15:37:43,844 WARN stopped: cron (terminated by SIGTERM)
|
||||
2025-11-22 15:37:44,282 INFO stopped: backup (exit status 0)
|
||||
2025-11-22 15:37:44,432 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:26,089 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.
|
||||
2025-11-22 15:38:26,090 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-11-22 15:38:26,090 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-22 15:38:26,090 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:26,090 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-11-22 15:38:26,128 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:26,141 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:26,141 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:27,160 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:38:27,224 INFO spawned: 'backup' with pid 17
|
||||
2025-11-22 15:38:27,299 INFO spawned: 'cron' with pid 18
|
||||
2025-11-22 15:38:27,386 INFO spawned: 'task_sync' with pid 19
|
||||
2025-11-22 15:38:28,435 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:28,435 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:28,435 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:28,435 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-22 15:38:37,310 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-11-25 15:48:29,675 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.
|
||||
2025-11-25 15:48:29,691 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-11-25 15:48:29,691 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-25 15:48:29,692 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:29,692 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-11-25 15:48:30,033 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:30,050 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:30,053 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:31,083 INFO spawned: 'mesh' with pid 15
|
||||
2025-11-25 15:48:31,134 INFO spawned: 'backup' with pid 16
|
||||
2025-11-25 15:48:31,195 INFO spawned: 'cron' with pid 17
|
||||
2025-11-25 15:48:31,347 INFO spawned: 'task_sync' with pid 18
|
||||
2025-11-25 15:48:32,409 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:32,410 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:32,410 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:32,410 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-11-25 15:48:40,556 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-12-07 15:52:24,291 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.
|
||||
2025-12-07 15:52:24,298 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-12-07 15:52:24,298 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-07 15:52:24,298 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:24,298 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-12-07 15:52:24,627 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:24,628 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:24,644 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:25,651 INFO spawned: 'mesh' with pid 19
|
||||
2025-12-07 15:52:25,696 INFO spawned: 'backup' with pid 20
|
||||
2025-12-07 15:52:25,804 INFO spawned: 'cron' with pid 21
|
||||
2025-12-07 15:52:25,882 INFO spawned: 'task_sync' with pid 23
|
||||
2025-12-07 15:52:26,895 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,896 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,899 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,905 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-12-07 15:52:33,970 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-12-08 11:39:37,386 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.
|
||||
2025-12-08 11:39:37,394 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-12-08 11:39:37,394 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-08 11:39:37,394 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:37,394 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-12-08 11:39:37,745 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:37,746 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:37,746 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:38,774 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-08 11:39:38,806 INFO spawned: 'backup' with pid 17
|
||||
2025-12-08 11:39:38,909 INFO spawned: 'cron' with pid 18
|
||||
2025-12-08 11:39:38,940 INFO spawned: 'task_sync' with pid 19
|
||||
2025-12-08 11:39:40,021 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:40,021 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:40,021 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:40,021 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-12-08 11:39:49,929 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-12-11 15:42:41,847 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.
|
||||
2025-12-11 15:42:41,853 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-12-11 15:42:41,853 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-11 15:42:41,853 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:41,853 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-12-11 15:42:42,196 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:42,217 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:42,217 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:43,242 INFO spawned: 'mesh' with pid 21
|
||||
2025-12-11 15:42:43,293 INFO spawned: 'backup' with pid 22
|
||||
2025-12-11 15:42:43,334 INFO spawned: 'cron' with pid 23
|
||||
2025-12-11 15:42:43,409 INFO spawned: 'task_sync' with pid 25
|
||||
2025-12-11 15:42:44,441 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,441 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,441 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,441 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-12-11 15:42:53,066 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-12-14 06:18:25,295 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.
|
||||
2025-12-14 06:18:25,305 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-12-14 06:18:25,305 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-14 06:18:25,305 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,305 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-12-14 06:18:25,638 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:25,639 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:25,639 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:26,663 INFO spawned: 'mesh' with pid 22
|
||||
2025-12-14 06:18:26,745 INFO spawned: 'backup' with pid 23
|
||||
2025-12-14 06:18:26,806 INFO spawned: 'cron' with pid 24
|
||||
2025-12-14 06:18:26,922 INFO spawned: 'task_sync' with pid 25
|
||||
2025-12-14 06:18:27,974 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,974 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,974 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,975 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-12-14 06:18:35,914 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-12-15 18:35:33,240 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.
|
||||
2025-12-15 18:35:33,258 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-12-15 18:35:33,258 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-15 18:35:33,258 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:33,258 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-12-15 18:35:33,625 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:33,625 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:33,625 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:34,639 INFO spawned: 'mesh' with pid 28
|
||||
2025-12-15 18:35:34,745 INFO spawned: 'backup' with pid 29
|
||||
2025-12-15 18:35:34,833 INFO spawned: 'cron' with pid 30
|
||||
2025-12-15 18:35:34,862 INFO spawned: 'task_sync' with pid 32
|
||||
2025-12-15 18:35:35,994 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:35,994 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:35,994 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:35,994 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-12-15 18:35:45,688 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-12-18 15:22:57,531 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.
|
||||
2025-12-18 15:22:57,543 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2025-12-18 15:22:57,544 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-18 15:22:57,544 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:57,544 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2025-12-18 15:22:57,887 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:57,887 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:57,887 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:58,919 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-18 15:22:58,983 INFO spawned: 'backup' with pid 17
|
||||
2025-12-18 15:22:59,103 INFO spawned: 'cron' with pid 18
|
||||
2025-12-18 15:22:59,306 INFO spawned: 'task_sync' with pid 22
|
||||
2025-12-18 15:23:00,317 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:00,336 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:00,336 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:00,336 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2025-12-18 15:23:08,739 INFO exited: task_sync (exit status 0; expected)
|
||||
2025-12-18 20:53:17,040 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:17,287 INFO spawned: 'mesh' with pid 47
|
||||
2025-12-18 20:53:17,288 WARN exited: backup (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:17,322 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,332 INFO spawned: 'backup' with pid 48
|
||||
2025-12-18 20:53:17,654 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,663 WARN exited: backup (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,667 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,676 INFO spawned: 'mesh' with pid 51
|
||||
2025-12-18 20:53:17,714 INFO spawned: 'backup' with pid 52
|
||||
2025-12-18 20:53:17,897 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,897 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,900 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,947 INFO spawned: 'mesh' with pid 55
|
||||
2025-12-18 20:53:18,064 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,064 WARN exited: backup (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,103 INFO spawned: 'backup' with pid 57
|
||||
2025-12-18 20:53:18,288 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,333 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,344 INFO spawned: 'mesh' with pid 59
|
||||
2025-12-18 20:53:18,373 WARN exited: backup (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,579 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,676 INFO spawned: 'backup' with pid 61
|
||||
2025-12-18 20:53:18,698 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,770 INFO spawned: 'mesh' with pid 62
|
||||
2025-12-18 20:53:18,788 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,033 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,034 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,107 INFO spawned: 'mesh' with pid 65
|
||||
2025-12-18 20:53:19,111 WARN exited: backup (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,119 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,172 INFO spawned: 'backup' with pid 66
|
||||
2025-12-18 20:53:19,433 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,434 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,624 INFO spawned: 'mesh' with pid 69
|
||||
2025-12-18 20:53:19,655 WARN exited: backup (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,720 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,819 INFO spawned: 'backup' with pid 70
|
||||
2025-12-18 20:53:19,883 WARN exited: cron (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,883 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,883 INFO waiting for mesh, backup to die
|
||||
2025-12-18 20:53:20,330 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,330 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:20,438 WARN exited: backup (exit status 1; not expected)
|
||||
2026-01-25 19:02:22,142 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.
|
||||
2026-01-25 19:02:22,154 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-01-25 19:02:22,154 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-01-25 19:02:22,154 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:22,154 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-01-25 19:02:22,184 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:22,184 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:22,184 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:23,214 INFO spawned: 'mesh' with pid 15
|
||||
2026-01-25 19:02:23,295 INFO spawned: 'backup' with pid 17
|
||||
2026-01-25 19:02:23,343 INFO spawned: 'cron' with pid 18
|
||||
2026-01-25 19:02:23,387 INFO spawned: 'task_sync' with pid 19
|
||||
2026-01-25 19:02:24,446 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,446 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,446 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,446 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-01-25 19:02:30,813 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-02-04 12:30:31,221 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.
|
||||
2026-02-04 12:30:31,226 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-02-04 12:30:31,226 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-04 12:30:31,226 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:31,226 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-02-04 12:30:31,567 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:31,567 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:31,567 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:32,575 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 12:30:32,645 INFO spawned: 'backup' with pid 17
|
||||
2026-02-04 12:30:32,702 INFO spawned: 'cron' with pid 19
|
||||
2026-02-04 12:30:32,785 INFO spawned: 'task_sync' with pid 20
|
||||
2026-02-04 12:30:33,805 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:33,805 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:33,805 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:33,805 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-02-04 12:30:43,187 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-02-04 14:57:35,614 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.
|
||||
2026-02-04 14:57:35,686 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-02-04 14:57:35,686 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-04 14:57:35,686 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,686 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-02-04 14:57:36,052 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,052 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,055 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,065 INFO spawned: 'mesh' with pid 25
|
||||
2026-02-04 14:57:37,116 INFO spawned: 'backup' with pid 26
|
||||
2026-02-04 14:57:37,167 INFO spawned: 'cron' with pid 27
|
||||
2026-02-04 14:57:37,290 INFO spawned: 'task_sync' with pid 28
|
||||
2026-02-04 14:57:38,333 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,333 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,333 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,333 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-02-04 14:57:45,761 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-02-04 17:30:56,252 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.
|
||||
2026-02-04 17:30:56,266 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-02-04 17:30:56,266 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-04 17:30:56,266 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:56,266 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-02-04 17:30:56,613 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:56,614 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:56,614 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:57,624 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 17:30:57,692 INFO spawned: 'backup' with pid 17
|
||||
2026-02-04 17:30:57,724 INFO spawned: 'cron' with pid 19
|
||||
2026-02-04 17:30:57,854 INFO spawned: 'task_sync' with pid 21
|
||||
2026-02-04 17:30:58,947 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:58,947 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:58,947 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:58,947 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-02-04 17:31:08,073 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-02-07 14:26:21,908 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.
|
||||
2026-02-07 14:26:21,927 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-02-07 14:26:21,927 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-07 14:26:21,927 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:21,927 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-02-07 14:26:22,267 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:22,267 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:22,267 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:23,285 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-07 14:26:23,367 INFO spawned: 'backup' with pid 17
|
||||
2026-02-07 14:26:23,430 INFO spawned: 'cron' with pid 19
|
||||
2026-02-07 14:26:23,496 INFO spawned: 'task_sync' with pid 20
|
||||
2026-02-07 14:26:24,531 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,531 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,531 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:24,531 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-02-07 14:26:33,502 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-02-20 16:02:21,168 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.
|
||||
2026-02-20 16:02:21,175 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-02-20 16:02:21,175 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-20 16:02:21,175 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:21,175 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-02-20 16:02:21,516 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,521 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,523 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,538 INFO spawned: 'mesh' with pid 15
|
||||
2026-02-20 16:02:22,622 INFO spawned: 'backup' with pid 16
|
||||
2026-02-20 16:02:22,700 INFO spawned: 'cron' with pid 17
|
||||
2026-02-20 16:02:22,804 INFO spawned: 'task_sync' with pid 19
|
||||
2026-02-20 16:02:23,820 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,820 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,820 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,820 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-02-20 16:02:32,241 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-03-04 12:10:30,634 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.
|
||||
2026-03-04 12:10:30,649 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-03-04 12:10:30,649 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-03-04 12:10:30,649 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:30,649 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-03-04 12:10:30,977 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:30,995 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:30,995 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:31,998 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-04 12:10:32,037 INFO spawned: 'backup' with pid 23
|
||||
2026-03-04 12:10:32,101 INFO spawned: 'cron' with pid 27
|
||||
2026-03-04 12:10:32,205 INFO spawned: 'task_sync' with pid 28
|
||||
2026-03-04 12:10:33,266 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,266 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,266 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,266 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-03-04 12:10:40,705 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-03-23 09:52:44,831 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.
|
||||
2026-03-23 09:52:44,849 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-03-23 09:52:44,849 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-03-23 09:52:44,849 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,849 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-03-23 09:52:45,196 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:45,196 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:45,196 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:46,210 INFO spawned: 'mesh' with pid 25
|
||||
2026-03-23 09:52:46,342 INFO spawned: 'backup' with pid 26
|
||||
2026-03-23 09:52:46,412 INFO spawned: 'cron' with pid 31
|
||||
2026-03-23 09:52:46,552 INFO spawned: 'task_sync' with pid 32
|
||||
2026-03-23 09:52:47,641 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,641 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,641 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,641 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-03-23 09:52:55,859 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-03-25 17:35:12,414 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.
|
||||
2026-03-25 17:35:12,416 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-03-25 17:35:12,416 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-03-25 17:35:12,416 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:12,416 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-03-25 17:35:12,737 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:12,737 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:12,737 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:13,745 INFO spawned: 'mesh' with pid 16
|
||||
2026-03-25 17:35:13,774 INFO spawned: 'backup' with pid 17
|
||||
2026-03-25 17:35:13,806 INFO spawned: 'cron' with pid 18
|
||||
2026-03-25 17:35:13,852 INFO spawned: 'task_sync' with pid 19
|
||||
2026-03-25 17:35:14,875 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:14,875 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:14,875 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:14,875 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-03-25 17:35:24,335 WARN exited: task_sync (exit status 1; not expected)
|
||||
2026-03-25 17:35:25,339 INFO spawned: 'task_sync' with pid 32
|
||||
2026-03-25 17:35:26,371 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-03-25 17:35:33,922 INFO exited: task_sync (exit status 0; expected)
|
||||
2026-03-26 07:04:02,981 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.
|
||||
2026-03-26 07:04:02,998 INFO Included extra file "/opt/supervisor.d/backup.conf" during parsing
|
||||
2026-03-26 07:04:02,998 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-03-26 07:04:02,998 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:02,998 INFO Included extra file "/opt/supervisor.d/task_sync.conf" during parsing
|
||||
2026-03-26 07:04:03,361 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,383 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,383 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,390 INFO spawned: 'mesh' with pid 25
|
||||
2026-03-26 07:04:04,451 INFO spawned: 'backup' with pid 26
|
||||
2026-03-26 07:04:04,492 INFO spawned: 'cron' with pid 28
|
||||
2026-03-26 07:04:04,569 INFO spawned: 'task_sync' with pid 30
|
||||
2026-03-26 07:04:05,703 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,778 INFO success: backup entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,778 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,778 INFO success: task_sync entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
|
||||
2026-03-26 07:04:14,865 INFO exited: task_sync (exit status 0; expected)
|
||||
@@ -0,0 +1,726 @@
|
||||
2025-08-30 21:13:24,052 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.
|
||||
2025-08-30 21:13:24,052 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-08-30 21:13:24,052 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-08-30 21:13:24,096 INFO RPC interface 'supervisor' initialized
|
||||
2025-08-30 21:13:24,096 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-08-30 21:13:24,096 INFO supervisord started with pid 1
|
||||
2025-08-30 21:13:25,159 INFO spawned: 'mesh' with pid 17
|
||||
2025-08-30 21:13:25,210 INFO spawned: 'batch' with pid 18
|
||||
2025-08-30 21:13:26,257 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:13:26,257 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,032 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-08-30 21:38:46,161 INFO spawned: 'mesh' with pid 27
|
||||
2025-08-30 21:38:46,234 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,245 WARN exited: batch (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-08-30 21:38:46,245 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:46,245 INFO reaped unknown pid 26 (exit status 0)
|
||||
2025-08-30 21:38:46,252 INFO spawned: 'mesh' with pid 29
|
||||
2025-08-30 21:38:46,273 INFO spawned: 'batch' with pid 30
|
||||
2025-08-30 21:38:46,314 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,315 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,315 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:46,360 INFO spawned: 'mesh' with pid 33
|
||||
2025-08-30 21:38:46,369 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:46,384 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,400 INFO spawned: 'batch' with pid 34
|
||||
2025-08-30 21:38:46,444 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,448 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:46,484 INFO spawned: 'mesh' with pid 37
|
||||
2025-08-30 21:38:46,498 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:46,516 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,534 INFO spawned: 'batch' with pid 38
|
||||
2025-08-30 21:38:46,601 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,620 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:46,625 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:46,640 INFO spawned: 'mesh' with pid 41
|
||||
2025-08-30 21:38:46,684 INFO spawned: 'batch' with pid 42
|
||||
2025-08-30 21:38:46,742 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,742 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,742 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:46,775 INFO spawned: 'mesh' with pid 45
|
||||
2025-08-30 21:38:46,787 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:46,787 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,828 INFO spawned: 'batch' with pid 46
|
||||
2025-08-30 21:38:46,867 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,870 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:46,886 INFO spawned: 'mesh' with pid 49
|
||||
2025-08-30 21:38:46,899 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:46,899 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,912 INFO spawned: 'batch' with pid 50
|
||||
2025-08-30 21:38:46,964 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:46,964 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:46,975 INFO spawned: 'mesh' with pid 53
|
||||
2025-08-30 21:38:46,986 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:46,997 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,020 INFO spawned: 'batch' with pid 54
|
||||
2025-08-30 21:38:47,054 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,092 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:47,092 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:47,122 INFO spawned: 'mesh' with pid 57
|
||||
2025-08-30 21:38:47,130 INFO spawned: 'batch' with pid 58
|
||||
2025-08-30 21:38:47,187 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,188 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,188 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:47,214 INFO spawned: 'mesh' with pid 61
|
||||
2025-08-30 21:38:47,232 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:47,234 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,283 INFO spawned: 'batch' with pid 62
|
||||
2025-08-30 21:38:47,297 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,357 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:47,357 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:47,373 INFO spawned: 'mesh' with pid 65
|
||||
2025-08-30 21:38:47,406 INFO spawned: 'batch' with pid 66
|
||||
2025-08-30 21:38:47,497 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,497 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,497 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:47,536 INFO spawned: 'batch' with pid 69
|
||||
2025-08-30 21:38:47,536 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:47,555 INFO spawned: 'mesh' with pid 70
|
||||
2025-08-30 21:38:47,556 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,600 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,600 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:47,624 INFO spawned: 'batch' with pid 73
|
||||
2025-08-30 21:38:47,652 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,705 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:47,705 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:47,724 INFO spawned: 'mesh' with pid 75
|
||||
2025-08-30 21:38:47,770 INFO spawned: 'batch' with pid 76
|
||||
2025-08-30 21:38:47,821 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,821 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,821 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:47,843 INFO spawned: 'mesh' with pid 79
|
||||
2025-08-30 21:38:47,851 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:47,860 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,877 INFO spawned: 'batch' with pid 80
|
||||
2025-08-30 21:38:47,931 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,932 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:47,961 INFO spawned: 'mesh' with pid 83
|
||||
2025-08-30 21:38:47,962 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:47,965 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:47,987 INFO spawned: 'batch' with pid 84
|
||||
2025-08-30 21:38:48,035 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,039 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,062 INFO spawned: 'mesh' with pid 87
|
||||
2025-08-30 21:38:48,063 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,069 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,077 INFO spawned: 'batch' with pid 88
|
||||
2025-08-30 21:38:48,147 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,148 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,158 INFO spawned: 'mesh' with pid 91
|
||||
2025-08-30 21:38:48,169 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,173 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,206 INFO spawned: 'batch' with pid 92
|
||||
2025-08-30 21:38:48,231 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,232 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,277 INFO spawned: 'mesh' with pid 95
|
||||
2025-08-30 21:38:48,278 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,288 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,295 INFO spawned: 'batch' with pid 96
|
||||
2025-08-30 21:38:48,355 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,356 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,376 INFO spawned: 'mesh' with pid 99
|
||||
2025-08-30 21:38:48,379 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,379 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,421 INFO spawned: 'batch' with pid 100
|
||||
2025-08-30 21:38:48,469 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,471 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,492 INFO spawned: 'mesh' with pid 103
|
||||
2025-08-30 21:38:48,509 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,511 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,542 INFO spawned: 'batch' with pid 104
|
||||
2025-08-30 21:38:48,595 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,598 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,618 INFO spawned: 'mesh' with pid 107
|
||||
2025-08-30 21:38:48,633 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,634 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,666 INFO spawned: 'batch' with pid 108
|
||||
2025-08-30 21:38:48,707 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,708 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,749 INFO spawned: 'mesh' with pid 111
|
||||
2025-08-30 21:38:48,763 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,764 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,786 INFO spawned: 'batch' with pid 112
|
||||
2025-08-30 21:38:48,834 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,840 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,855 INFO spawned: 'mesh' with pid 115
|
||||
2025-08-30 21:38:48,863 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,864 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,879 INFO spawned: 'batch' with pid 116
|
||||
2025-08-30 21:38:48,918 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,920 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:48,949 INFO spawned: 'mesh' with pid 119
|
||||
2025-08-30 21:38:48,951 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:48,956 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:48,975 INFO spawned: 'batch' with pid 120
|
||||
2025-08-30 21:38:49,027 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,028 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:49,045 INFO spawned: 'mesh' with pid 123
|
||||
2025-08-30 21:38:49,059 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:49,059 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,074 INFO spawned: 'batch' with pid 124
|
||||
2025-08-30 21:38:49,143 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,148 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:49,180 INFO spawned: 'mesh' with pid 127
|
||||
2025-08-30 21:38:49,189 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:49,194 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,226 INFO spawned: 'batch' with pid 128
|
||||
2025-08-30 21:38:49,252 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,289 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:49,306 INFO spawned: 'mesh' with pid 131
|
||||
2025-08-30 21:38:49,316 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:49,331 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,353 INFO spawned: 'batch' with pid 132
|
||||
2025-08-30 21:38:49,416 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,417 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:49,431 INFO spawned: 'mesh' with pid 135
|
||||
2025-08-30 21:38:49,452 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:49,453 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,471 INFO spawned: 'batch' with pid 136
|
||||
2025-08-30 21:38:49,514 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,515 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:49,547 INFO spawned: 'mesh' with pid 139
|
||||
2025-08-30 21:38:49,550 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:49,558 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,580 INFO spawned: 'batch' with pid 140
|
||||
2025-08-30 21:38:49,625 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,627 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:49,669 INFO spawned: 'mesh' with pid 143
|
||||
2025-08-30 21:38:49,678 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:49,678 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,703 INFO spawned: 'batch' with pid 144
|
||||
2025-08-30 21:38:49,753 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,753 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:49,798 INFO spawned: 'mesh' with pid 147
|
||||
2025-08-30 21:38:49,812 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:49,812 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,846 INFO spawned: 'batch' with pid 148
|
||||
2025-08-30 21:38:49,902 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:49,933 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:49,934 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:49,948 INFO spawned: 'mesh' with pid 151
|
||||
2025-08-30 21:38:49,982 INFO spawned: 'batch' with pid 152
|
||||
2025-08-30 21:38:50,058 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,058 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,058 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:50,081 INFO spawned: 'mesh' with pid 155
|
||||
2025-08-30 21:38:50,090 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:50,099 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,130 INFO spawned: 'batch' with pid 156
|
||||
2025-08-30 21:38:50,181 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,181 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:50,204 INFO spawned: 'mesh' with pid 159
|
||||
2025-08-30 21:38:50,210 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:50,215 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,227 INFO spawned: 'batch' with pid 160
|
||||
2025-08-30 21:38:50,280 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,297 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:50,302 INFO spawned: 'mesh' with pid 163
|
||||
2025-08-30 21:38:50,315 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:50,329 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,342 INFO spawned: 'batch' with pid 164
|
||||
2025-08-30 21:38:50,433 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,446 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:50,461 INFO spawned: 'mesh' with pid 167
|
||||
2025-08-30 21:38:50,469 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:50,472 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,490 INFO spawned: 'batch' with pid 168
|
||||
2025-08-30 21:38:50,541 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,546 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:50,599 INFO spawned: 'mesh' with pid 171
|
||||
2025-08-30 21:38:50,612 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:50,614 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,633 INFO spawned: 'batch' with pid 172
|
||||
2025-08-30 21:38:50,692 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,692 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:50,717 INFO spawned: 'mesh' with pid 175
|
||||
2025-08-30 21:38:50,733 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:50,751 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,767 INFO spawned: 'batch' with pid 176
|
||||
2025-08-30 21:38:50,836 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,842 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:50,878 INFO spawned: 'mesh' with pid 179
|
||||
2025-08-30 21:38:50,886 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:50,902 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:50,925 INFO spawned: 'batch' with pid 180
|
||||
2025-08-30 21:38:50,990 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,020 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:51,045 INFO spawned: 'mesh' with pid 183
|
||||
2025-08-30 21:38:51,046 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:51,046 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,090 INFO spawned: 'batch' with pid 185
|
||||
2025-08-30 21:38:51,091 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:51,114 INFO spawned: 'mesh' with pid 186
|
||||
2025-08-30 21:38:51,114 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,176 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,181 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:51,194 INFO spawned: 'batch' with pid 188
|
||||
2025-08-30 21:38:51,265 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,268 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:51,293 INFO spawned: 'mesh' with pid 191
|
||||
2025-08-30 21:38:51,303 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:51,303 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,325 INFO spawned: 'batch' with pid 192
|
||||
2025-08-30 21:38:51,373 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,373 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:51,401 INFO spawned: 'mesh' with pid 195
|
||||
2025-08-30 21:38:51,419 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:51,419 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,457 INFO spawned: 'batch' with pid 196
|
||||
2025-08-30 21:38:51,518 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,518 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:51,530 INFO spawned: 'batch' with pid 199
|
||||
2025-08-30 21:38:51,541 INFO exited: mesh (exit status 0; expected)
|
||||
2025-08-30 21:38:51,564 INFO spawned: 'mesh' with pid 200
|
||||
2025-08-30 21:38:51,573 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,621 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:51,626 WARN exited: batch (exit status 1; not expected)
|
||||
2025-08-30 21:38:51,756 INFO spawned: 'batch' with pid 203
|
||||
2025-08-30 21:38:51,835 WARN exited: mesh (terminated by SIGTERM; not expected)
|
||||
2025-08-30 21:38:51,835 WARN received SIGTERM indicating exit request
|
||||
2025-08-30 21:38:51,861 INFO waiting for batch to die
|
||||
2025-08-30 21:38:52,040 WARN stopped: batch (exit status 1)
|
||||
2025-09-02 13:52:18,866 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.
|
||||
2025-09-02 13:52:18,888 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-09-02 13:52:18,888 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-09-02 13:52:18,943 INFO RPC interface 'supervisor' initialized
|
||||
2025-09-02 13:52:18,951 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-09-02 13:52:18,955 INFO supervisord started with pid 1
|
||||
2025-09-02 13:52:19,970 INFO spawned: 'mesh' with pid 17
|
||||
2025-09-02 13:52:20,009 INFO spawned: 'batch' with pid 18
|
||||
2025-09-02 13:52:21,010 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-09-02 13:52:21,010 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-09-14 11:45:59,056 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.
|
||||
2025-09-14 11:45:59,061 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-09-14 11:45:59,061 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-09-14 11:45:59,463 INFO RPC interface 'supervisor' initialized
|
||||
2025-09-14 11:45:59,463 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-09-14 11:45:59,463 INFO supervisord started with pid 1
|
||||
2025-09-14 11:46:00,488 INFO spawned: 'mesh' with pid 24
|
||||
2025-09-14 11:46:00,544 INFO spawned: 'batch' with pid 25
|
||||
2025-09-14 11:46:01,598 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-09-14 11:46:01,598 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-20 16:49:45,583 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.
|
||||
2025-10-20 16:49:45,598 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-10-20 16:49:45,598 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-10-20 16:49:45,947 INFO RPC interface 'supervisor' initialized
|
||||
2025-10-20 16:49:45,948 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-10-20 16:49:45,948 INFO supervisord started with pid 1
|
||||
2025-10-20 16:49:46,970 INFO spawned: 'mesh' with pid 26
|
||||
2025-10-20 16:49:47,047 INFO spawned: 'batch' with pid 27
|
||||
2025-10-20 16:49:48,063 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-20 16:49:48,063 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-21 16:46:08,620 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.
|
||||
2025-10-21 16:46:08,639 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-10-21 16:46:08,639 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-10-21 16:46:09,007 INFO RPC interface 'supervisor' initialized
|
||||
2025-10-21 16:46:09,016 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-10-21 16:46:09,028 INFO supervisord started with pid 1
|
||||
2025-10-21 16:46:10,041 INFO spawned: 'mesh' with pid 23
|
||||
2025-10-21 16:46:10,137 INFO spawned: 'batch' with pid 24
|
||||
2025-10-21 16:46:11,166 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-21 16:46:11,166 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-30 10:40:51,228 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.
|
||||
2025-10-30 10:40:51,257 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-10-30 10:40:51,257 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-10-30 10:40:51,648 INFO RPC interface 'supervisor' initialized
|
||||
2025-10-30 10:40:51,651 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-10-30 10:40:51,657 INFO supervisord started with pid 1
|
||||
2025-10-30 10:40:52,681 INFO spawned: 'mesh' with pid 23
|
||||
2025-10-30 10:40:52,721 INFO spawned: 'batch' with pid 24
|
||||
2025-10-30 10:40:53,763 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-30 10:40:53,763 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-05 09:21:55,953 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.
|
||||
2025-11-05 09:21:55,972 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-05 09:21:55,972 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-05 09:21:56,356 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-05 09:21:56,356 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-05 09:21:56,356 INFO supervisord started with pid 1
|
||||
2025-11-05 09:21:57,385 INFO spawned: 'mesh' with pid 29
|
||||
2025-11-05 09:21:57,443 INFO spawned: 'batch' with pid 30
|
||||
2025-11-05 09:21:58,474 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-05 09:21:58,474 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:43:04,721 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.
|
||||
2025-11-12 08:43:04,721 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-12 08:43:04,722 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:43:05,046 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:43:05,046 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:43:05,047 INFO supervisord started with pid 1
|
||||
2025-11-12 08:43:06,081 INFO spawned: 'mesh' with pid 29
|
||||
2025-11-12 08:43:06,223 INFO spawned: 'batch' with pid 30
|
||||
2025-11-12 08:43:07,233 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:43:07,233 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,230 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.
|
||||
2025-11-17 12:01:28,234 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-17 12:01:28,234 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:28,599 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:28,599 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:28,599 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:29,629 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-17 12:01:29,734 INFO spawned: 'batch' with pid 18
|
||||
2025-11-17 12:01:30,747 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:30,747 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:35,807 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.
|
||||
2025-11-21 15:30:35,818 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-21 15:30:35,818 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:36,177 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:36,178 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:36,182 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:37,200 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-21 15:30:37,258 INFO spawned: 'batch' with pid 27
|
||||
2025-11-21 15:30:38,292 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,292 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:46,876 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.
|
||||
2025-11-22 15:19:46,892 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-22 15:19:46,892 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:47,244 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,255 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,255 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,287 INFO spawned: 'mesh' with pid 20
|
||||
2025-11-22 15:19:48,408 INFO spawned: 'batch' with pid 21
|
||||
2025-11-22 15:19:49,414 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,441 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:58,055 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:58,093 INFO waiting for mesh, batch to die
|
||||
2025-11-22 15:27:58,514 INFO stopped: batch (exit status 0)
|
||||
2025-11-22 15:27:58,712 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:18,803 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.
|
||||
2025-11-22 15:28:18,803 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-22 15:28:18,803 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:18,822 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:18,822 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:18,822 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:19,831 INFO spawned: 'mesh' with pid 20
|
||||
2025-11-22 15:28:19,864 INFO spawned: 'batch' with pid 21
|
||||
2025-11-22 15:28:20,866 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:20,866 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:46,132 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,158 INFO waiting for mesh, batch to die
|
||||
2025-11-22 15:30:46,574 INFO stopped: batch (exit status 0)
|
||||
2025-11-22 15:30:47,051 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:10,110 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.
|
||||
2025-11-22 15:31:10,110 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-22 15:31:10,110 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:10,141 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:10,144 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:10,144 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:11,148 INFO spawned: 'mesh' with pid 19
|
||||
2025-11-22 15:31:11,150 INFO spawned: 'batch' with pid 20
|
||||
2025-11-22 15:31:12,154 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:12,154 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:42,661 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:42,672 INFO waiting for mesh, batch to die
|
||||
2025-11-22 15:37:42,838 INFO stopped: batch (exit status 0)
|
||||
2025-11-22 15:37:43,005 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:16,981 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.
|
||||
2025-11-22 15:38:16,981 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-22 15:38:16,981 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:17,011 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:17,011 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:17,011 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:18,015 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:38:18,027 INFO spawned: 'batch' with pid 18
|
||||
2025-11-22 15:38:19,028 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:19,028 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,777 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.
|
||||
2025-11-25 15:48:30,796 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-11-25 15:48:30,796 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:31,153 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:31,153 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:31,154 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:32,174 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-25 15:48:32,248 INFO spawned: 'batch' with pid 18
|
||||
2025-11-25 15:48:33,289 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:33,289 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:22,680 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.
|
||||
2025-12-07 15:52:22,706 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-12-07 15:52:22,706 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:23,079 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:23,079 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:23,091 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:24,113 INFO spawned: 'mesh' with pid 28
|
||||
2025-12-07 15:52:24,175 INFO spawned: 'batch' with pid 29
|
||||
2025-12-07 15:52:25,185 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,185 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:32,354 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.
|
||||
2025-12-08 11:39:32,358 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-12-08 11:39:32,358 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:32,685 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:32,685 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:32,689 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:33,704 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-08 11:39:33,769 INFO spawned: 'batch' with pid 18
|
||||
2025-12-08 11:39:34,798 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,798 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:43,324 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.
|
||||
2025-12-11 15:42:43,332 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-12-11 15:42:43,332 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:43,675 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:43,675 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:43,676 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:44,707 INFO spawned: 'mesh' with pid 22
|
||||
2025-12-11 15:42:44,789 INFO spawned: 'batch' with pid 23
|
||||
2025-12-11 15:42:45,794 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,794 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:25,867 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.
|
||||
2025-12-14 06:18:25,876 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-12-14 06:18:25,876 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:26,240 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:26,240 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:26,240 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:27,269 INFO spawned: 'mesh' with pid 26
|
||||
2025-12-14 06:18:27,345 INFO spawned: 'batch' with pid 27
|
||||
2025-12-14 06:18:28,382 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:28,384 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:33,449 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.
|
||||
2025-12-15 18:35:33,480 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-12-15 18:35:33,480 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:33,876 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:33,876 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:33,876 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:34,910 INFO spawned: 'mesh' with pid 29
|
||||
2025-12-15 18:35:34,984 INFO spawned: 'batch' with pid 30
|
||||
2025-12-15 18:35:36,031 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:36,031 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:52,432 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.
|
||||
2025-12-18 15:22:52,435 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2025-12-18 15:22:52,435 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:52,762 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:52,762 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:52,763 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:53,781 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-18 15:22:53,825 INFO spawned: 'batch' with pid 18
|
||||
2025-12-18 15:22:54,894 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:54,894 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,946 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:13,261 INFO spawned: 'mesh' with pid 27
|
||||
2025-12-18 20:53:13,300 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,396 WARN exited: batch (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:14,396 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,396 INFO reaped unknown pid 26 (exit status 0)
|
||||
2025-12-18 20:53:15,405 INFO spawned: 'mesh' with pid 29
|
||||
2025-12-18 20:53:15,455 INFO spawned: 'batch' with pid 30
|
||||
2025-12-18 20:53:15,545 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,545 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,547 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,572 INFO spawned: 'mesh' with pid 33
|
||||
2025-12-18 20:53:15,617 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,617 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,643 INFO spawned: 'batch' with pid 35
|
||||
2025-12-18 20:53:15,697 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,704 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,706 INFO spawned: 'mesh' with pid 36
|
||||
2025-12-18 20:53:15,784 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,793 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,797 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,805 INFO spawned: 'mesh' with pid 39
|
||||
2025-12-18 20:53:15,837 INFO spawned: 'batch' with pid 40
|
||||
2025-12-18 20:53:15,909 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,911 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,915 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,917 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,924 INFO spawned: 'mesh' with pid 43
|
||||
2025-12-18 20:53:15,953 INFO spawned: 'batch' with pid 44
|
||||
2025-12-18 20:53:16,066 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,066 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,070 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,127 INFO spawned: 'mesh' with pid 47
|
||||
2025-12-18 20:53:16,132 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,145 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,164 INFO spawned: 'batch' with pid 48
|
||||
2025-12-18 20:53:16,212 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,215 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,240 INFO spawned: 'mesh' with pid 51
|
||||
2025-12-18 20:53:16,274 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,274 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,300 INFO spawned: 'batch' with pid 52
|
||||
2025-12-18 20:53:16,330 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,337 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,466 INFO spawned: 'mesh' with pid 55
|
||||
2025-12-18 20:53:16,487 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,487 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,523 INFO spawned: 'batch' with pid 56
|
||||
2025-12-18 20:53:16,612 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,613 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,665 INFO spawned: 'mesh' with pid 59
|
||||
2025-12-18 20:53:16,669 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,669 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,733 INFO spawned: 'batch' with pid 60
|
||||
2025-12-18 20:53:16,800 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,800 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,874 INFO spawned: 'mesh' with pid 63
|
||||
2025-12-18 20:53:16,900 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,901 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,967 INFO spawned: 'batch' with pid 65
|
||||
2025-12-18 20:53:16,968 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,029 INFO spawned: 'mesh' with pid 66
|
||||
2025-12-18 20:53:17,031 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,125 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,125 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,147 INFO spawned: 'batch' with pid 69
|
||||
2025-12-18 20:53:17,195 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,195 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,261 INFO spawned: 'mesh' with pid 71
|
||||
2025-12-18 20:53:17,282 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,288 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,325 INFO spawned: 'batch' with pid 72
|
||||
2025-12-18 20:53:17,407 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,411 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,459 INFO spawned: 'mesh' with pid 75
|
||||
2025-12-18 20:53:17,488 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,491 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,523 INFO spawned: 'batch' with pid 76
|
||||
2025-12-18 20:53:17,578 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,582 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,621 INFO spawned: 'mesh' with pid 78
|
||||
2025-12-18 20:53:17,709 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,709 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,732 INFO spawned: 'batch' with pid 81
|
||||
2025-12-18 20:53:17,826 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,827 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,858 INFO spawned: 'batch' with pid 83
|
||||
2025-12-18 20:53:17,859 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,888 INFO spawned: 'mesh' with pid 84
|
||||
2025-12-18 20:53:17,914 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,999 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,999 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,015 INFO spawned: 'batch' with pid 86
|
||||
2025-12-18 20:53:18,120 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,123 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,203 INFO spawned: 'mesh' with pid 89
|
||||
2025-12-18 20:53:18,210 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,222 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,249 INFO spawned: 'batch' with pid 90
|
||||
2025-12-18 20:53:18,371 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,371 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,413 INFO spawned: 'mesh' with pid 93
|
||||
2025-12-18 20:53:18,431 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,432 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,467 INFO spawned: 'batch' with pid 94
|
||||
2025-12-18 20:53:18,612 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,663 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,670 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,681 INFO spawned: 'mesh' with pid 97
|
||||
2025-12-18 20:53:18,765 INFO spawned: 'batch' with pid 98
|
||||
2025-12-18 20:53:18,838 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,838 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,839 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,964 INFO spawned: 'mesh' with pid 101
|
||||
2025-12-18 20:53:18,965 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,965 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,037 INFO spawned: 'batch' with pid 102
|
||||
2025-12-18 20:53:19,215 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,215 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,258 INFO spawned: 'mesh' with pid 105
|
||||
2025-12-18 20:53:19,292 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,293 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,340 INFO spawned: 'batch' with pid 106
|
||||
2025-12-18 20:53:19,487 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,529 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,638 INFO spawned: 'mesh' with pid 109
|
||||
2025-12-18 20:53:19,639 WARN exited: batch (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,640 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,737 INFO spawned: 'batch' with pid 110
|
||||
2025-12-18 20:53:19,834 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,907 INFO waiting for mesh, batch to die
|
||||
2025-12-18 20:53:19,977 WARN stopped: batch (terminated by SIGTERM)
|
||||
2025-12-18 20:53:19,986 WARN stopped: mesh (terminated by SIGTERM)
|
||||
2026-01-25 19:02:20,373 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.
|
||||
2026-01-25 19:02:20,390 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-01-25 19:02:20,390 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:20,453 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:20,453 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:20,453 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:21,489 INFO spawned: 'mesh' with pid 17
|
||||
2026-01-25 19:02:21,590 INFO spawned: 'batch' with pid 18
|
||||
2026-01-25 19:02:22,597 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,598 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,283 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.
|
||||
2026-02-04 12:30:25,289 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-02-04 12:30:25,289 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:25,620 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:25,620 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:25,621 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:26,642 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 12:30:26,696 INFO spawned: 'batch' with pid 18
|
||||
2026-02-04 12:30:27,700 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:27,700 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:36,302 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.
|
||||
2026-02-04 14:57:36,303 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-02-04 14:57:36,304 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:36,654 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,657 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,659 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,677 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 14:57:37,755 INFO spawned: 'batch' with pid 18
|
||||
2026-02-04 14:57:38,765 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,765 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,659 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.
|
||||
2026-02-04 17:30:57,670 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-02-04 17:30:57,670 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:58,029 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:58,029 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:58,037 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:59,051 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 17:30:59,110 INFO spawned: 'batch' with pid 17
|
||||
2026-02-04 17:31:00,174 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:00,174 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:20,242 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.
|
||||
2026-02-07 14:26:20,255 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-02-07 14:26:20,255 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:20,621 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,621 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,632 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,648 INFO spawned: 'mesh' with pid 19
|
||||
2026-02-07 14:26:21,721 INFO spawned: 'batch' with pid 20
|
||||
2026-02-07 14:26:22,785 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,785 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:20,883 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.
|
||||
2026-02-20 16:02:20,914 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-02-20 16:02:20,914 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:21,286 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,286 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,298 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,314 INFO spawned: 'mesh' with pid 20
|
||||
2026-02-20 16:02:22,390 INFO spawned: 'batch' with pid 21
|
||||
2026-02-20 16:02:23,392 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,392 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:31,024 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.
|
||||
2026-03-04 12:10:31,041 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-03-04 12:10:31,041 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,406 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,406 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,406 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,443 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-04 12:10:32,508 INFO spawned: 'batch' with pid 23
|
||||
2026-03-04 12:10:33,561 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,562 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:44,500 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.
|
||||
2026-03-23 09:52:44,536 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-03-23 09:52:44,536 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,899 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:44,899 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:44,899 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:45,923 INFO spawned: 'mesh' with pid 20
|
||||
2026-03-23 09:52:45,956 INFO spawned: 'batch' with pid 21
|
||||
2026-03-23 09:52:46,988 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,988 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:22,390 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.
|
||||
2026-03-25 17:35:22,405 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-03-25 17:35:22,405 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:22,776 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:22,776 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:22,776 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:23,832 INFO spawned: 'mesh' with pid 16
|
||||
2026-03-25 17:35:23,895 INFO spawned: 'batch' with pid 17
|
||||
2026-03-25 17:35:24,967 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:24,967 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,747 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.
|
||||
2026-03-26 07:04:03,759 INFO Included extra file "/opt/supervisor.d/batch.conf" during parsing
|
||||
2026-03-26 07:04:03,759 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:04,163 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:04,164 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:04,166 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:05,187 INFO spawned: 'mesh' with pid 26
|
||||
2026-03-26 07:04:05,254 INFO spawned: 'batch' with pid 27
|
||||
2026-03-26 07:04:06,284 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,284 INFO success: batch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
52535
DCIManager6/output_data/isp_not_number_2026-03-26_07-18/config.json
Normal file
52535
DCIManager6/output_data/isp_not_number_2026-03-26_07-18/config.json
Normal file
File diff suppressed because one or more lines are too long
@@ -0,0 +1,627 @@
|
||||
2025-11-12 08:50:19,817 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.
|
||||
2025-11-12 08:50:19,830 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-11-12 08:50:19,830 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:19,830 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-12 08:50:19,913 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:19,913 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:19,913 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:20,924 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-12 08:50:20,987 INFO spawned: 'customizer_reader' with pid 28
|
||||
2025-11-12 08:50:21,232 INFO spawned: 'customizer_writer' with pid 33
|
||||
2025-11-12 08:50:21,320 INFO spawned: 'nginx' with pid 35
|
||||
2025-11-12 08:50:22,165 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:22,166 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:22,166 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:22,166 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:34,441 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.
|
||||
2025-11-17 12:01:34,445 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-11-17 12:01:34,445 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:34,445 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-17 12:01:34,776 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:34,776 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:34,788 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:35,804 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-17 12:01:35,866 INFO spawned: 'customizer_reader' with pid 27
|
||||
2025-11-17 12:01:35,943 INFO spawned: 'customizer_writer' with pid 28
|
||||
2025-11-17 12:01:36,067 INFO spawned: 'nginx' with pid 30
|
||||
2025-11-17 12:01:36,961 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:36,961 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:36,961 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:36,961 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:36,161 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.
|
||||
2025-11-21 15:30:36,170 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-11-21 15:30:36,170 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:36,170 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-21 15:30:36,490 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:36,499 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:36,499 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:37,510 INFO spawned: 'mesh' with pid 34
|
||||
2025-11-21 15:30:37,531 INFO spawned: 'customizer_reader' with pid 35
|
||||
2025-11-21 15:30:37,586 INFO spawned: 'customizer_writer' with pid 36
|
||||
2025-11-21 15:30:37,648 INFO spawned: 'nginx' with pid 40
|
||||
2025-11-21 15:30:38,680 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,683 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,683 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,683 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,362 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.
|
||||
2025-11-22 15:19:48,383 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-11-22 15:19:48,383 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:48,383 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-22 15:19:48,746 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:48,753 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:48,753 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:49,785 INFO spawned: 'mesh' with pid 29
|
||||
2025-11-22 15:19:49,841 INFO spawned: 'customizer_reader' with pid 30
|
||||
2025-11-22 15:19:49,917 INFO spawned: 'customizer_writer' with pid 31
|
||||
2025-11-22 15:19:50,018 INFO spawned: 'nginx' with pid 33
|
||||
2025-11-22 15:19:51,019 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,019 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,019 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,019 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:57,448 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:57,460 INFO waiting for mesh, customizer_reader, customizer_writer, nginx to die
|
||||
2025-11-22 15:27:57,532 INFO stopped: nginx (exit status 0)
|
||||
2025-11-22 15:27:58,371 INFO stopped: customizer_writer (exit status 0)
|
||||
2025-11-22 15:27:58,540 INFO stopped: customizer_reader (exit status 0)
|
||||
2025-11-22 15:27:58,684 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:29,780 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.
|
||||
2025-11-22 15:28:29,784 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-11-22 15:28:29,784 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:29,784 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-22 15:28:29,821 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:29,821 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:29,822 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:30,846 INFO spawned: 'mesh' with pid 25
|
||||
2025-11-22 15:28:30,879 INFO spawned: 'customizer_reader' with pid 26
|
||||
2025-11-22 15:28:30,941 INFO spawned: 'customizer_writer' with pid 28
|
||||
2025-11-22 15:28:30,999 INFO spawned: 'nginx' with pid 30
|
||||
2025-11-22 15:28:31,881 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:31,885 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:31,891 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:31,891 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:46,557 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,563 INFO waiting for mesh, customizer_reader, customizer_writer, nginx to die
|
||||
2025-11-22 15:30:46,631 INFO stopped: nginx (exit status 0)
|
||||
2025-11-22 15:30:48,013 INFO stopped: customizer_writer (exit status 0)
|
||||
2025-11-22 15:30:48,053 INFO stopped: customizer_reader (exit status 0)
|
||||
2025-11-22 15:30:48,099 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:14,817 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.
|
||||
2025-11-22 15:31:14,817 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-11-22 15:31:14,817 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:14,817 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-22 15:31:14,843 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:14,845 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:14,846 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:15,865 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-22 15:31:15,893 INFO spawned: 'customizer_reader' with pid 27
|
||||
2025-11-22 15:31:15,949 INFO spawned: 'customizer_writer' with pid 28
|
||||
2025-11-22 15:31:15,994 INFO spawned: 'nginx' with pid 29
|
||||
2025-11-22 15:31:16,597 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,603 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,606 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,606 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:42,571 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:42,581 INFO waiting for mesh, customizer_reader, customizer_writer, nginx to die
|
||||
2025-11-22 15:37:42,606 INFO stopped: nginx (exit status 0)
|
||||
2025-11-22 15:37:42,734 INFO stopped: customizer_writer (exit status 0)
|
||||
2025-11-22 15:37:42,928 INFO stopped: customizer_reader (exit status 0)
|
||||
2025-11-22 15:37:43,462 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:26,903 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.
|
||||
2025-11-22 15:38:26,903 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-11-22 15:38:26,903 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:26,903 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-22 15:38:26,977 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:26,977 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:27,008 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:28,012 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-22 15:38:28,065 INFO spawned: 'customizer_reader' with pid 27
|
||||
2025-11-22 15:38:28,168 INFO spawned: 'customizer_writer' with pid 28
|
||||
2025-11-22 15:38:28,234 INFO spawned: 'nginx' with pid 30
|
||||
2025-11-22 15:38:29,244 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:29,245 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:29,245 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:29,245 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:28,955 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.
|
||||
2025-11-25 15:48:28,961 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-11-25 15:48:28,961 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:28,961 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-25 15:48:29,313 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:29,331 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:29,332 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:30,343 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-25 15:48:30,422 INFO spawned: 'customizer_reader' with pid 27
|
||||
2025-11-25 15:48:30,499 INFO spawned: 'customizer_writer' with pid 28
|
||||
2025-11-25 15:48:30,608 INFO spawned: 'nginx' with pid 30
|
||||
2025-11-25 15:48:31,647 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,653 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,663 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,666 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:24,211 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.
|
||||
2025-12-07 15:52:24,232 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-12-07 15:52:24,232 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:24,232 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-07 15:52:24,577 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:24,583 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:24,585 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:25,598 INFO spawned: 'mesh' with pid 33
|
||||
2025-12-07 15:52:25,651 INFO spawned: 'customizer_reader' with pid 34
|
||||
2025-12-07 15:52:25,704 INFO spawned: 'customizer_writer' with pid 35
|
||||
2025-12-07 15:52:25,780 INFO spawned: 'nginx' with pid 37
|
||||
2025-12-07 15:52:26,820 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,820 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,820 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,820 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:28,785 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.
|
||||
2025-12-08 11:39:28,785 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-12-08 11:39:28,786 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:28,786 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-08 11:39:29,103 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:29,104 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:29,106 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:30,109 INFO spawned: 'mesh' with pid 29
|
||||
2025-12-08 11:39:30,135 INFO spawned: 'customizer_reader' with pid 30
|
||||
2025-12-08 11:39:30,171 INFO spawned: 'customizer_writer' with pid 31
|
||||
2025-12-08 11:39:30,201 INFO spawned: 'nginx' with pid 32
|
||||
2025-12-08 11:39:30,596 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:30,597 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:30,597 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:30,597 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,592 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.
|
||||
2025-12-11 15:42:42,600 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-12-11 15:42:42,600 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:42,600 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-11 15:42:42,971 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:42,971 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:42,971 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:44,034 INFO spawned: 'mesh' with pid 32
|
||||
2025-12-11 15:42:44,092 INFO spawned: 'customizer_reader' with pid 33
|
||||
2025-12-11 15:42:44,146 INFO spawned: 'customizer_writer' with pid 34
|
||||
2025-12-11 15:42:44,264 INFO spawned: 'nginx' with pid 36
|
||||
2025-12-11 15:42:45,188 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,188 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,188 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,188 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:25,495 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.
|
||||
2025-12-14 06:18:25,501 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-12-14 06:18:25,501 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,501 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-14 06:18:25,834 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:25,835 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:25,835 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:26,840 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-14 06:18:26,953 INFO spawned: 'customizer_reader' with pid 36
|
||||
2025-12-14 06:18:27,074 INFO spawned: 'customizer_writer' with pid 38
|
||||
2025-12-14 06:18:27,144 INFO spawned: 'nginx' with pid 40
|
||||
2025-12-14 06:18:28,233 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:28,233 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:28,233 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:28,233 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,903 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.
|
||||
2025-12-15 18:35:34,952 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-12-15 18:35:34,952 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:34,952 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-15 18:35:35,299 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:35,299 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:35,304 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:36,341 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-15 18:35:36,372 INFO spawned: 'customizer_reader' with pid 36
|
||||
2025-12-15 18:35:36,463 INFO spawned: 'customizer_writer' with pid 37
|
||||
2025-12-15 18:35:36,558 INFO spawned: 'nginx' with pid 38
|
||||
2025-12-15 18:35:37,562 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:37,562 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:37,562 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:37,562 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:00,609 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.
|
||||
2025-12-18 15:23:00,616 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2025-12-18 15:23:00,616 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:00,616 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-18 15:23:00,961 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:00,961 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:00,961 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:01,979 INFO spawned: 'mesh' with pid 26
|
||||
2025-12-18 15:23:02,012 INFO spawned: 'customizer_reader' with pid 27
|
||||
2025-12-18 15:23:02,070 INFO spawned: 'customizer_writer' with pid 28
|
||||
2025-12-18 15:23:02,154 INFO spawned: 'nginx' with pid 30
|
||||
2025-12-18 15:23:02,901 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:02,902 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:02,902 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:02,902 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,955 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:11,113 INFO spawned: 'mesh' with pid 55
|
||||
2025-12-18 20:53:11,215 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,215 WARN exited: customizer_reader (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:11,215 INFO reaped unknown pid 52 (exit status 0)
|
||||
2025-12-18 20:53:11,467 INFO spawned: 'customizer_reader' with pid 57
|
||||
2025-12-18 20:53:11,477 WARN exited: customizer_writer (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:11,477 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,477 INFO reaped unknown pid 41 (exit status 0)
|
||||
2025-12-18 20:53:11,519 INFO spawned: 'mesh' with pid 58
|
||||
2025-12-18 20:53:11,520 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,551 INFO spawned: 'customizer_writer' with pid 59
|
||||
2025-12-18 20:53:11,662 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,663 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,672 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,679 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,707 INFO spawned: 'mesh' with pid 63
|
||||
2025-12-18 20:53:11,752 INFO spawned: 'customizer_reader' with pid 64
|
||||
2025-12-18 20:53:11,753 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,753 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,753 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,830 INFO spawned: 'customizer_writer' with pid 66
|
||||
2025-12-18 20:53:11,899 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,899 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,951 INFO spawned: 'mesh' with pid 69
|
||||
2025-12-18 20:53:11,951 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,952 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,016 INFO spawned: 'customizer_reader' with pid 70
|
||||
2025-12-18 20:53:12,016 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,017 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,062 INFO spawned: 'customizer_writer' with pid 72
|
||||
2025-12-18 20:53:12,083 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,121 INFO spawned: 'mesh' with pid 74
|
||||
2025-12-18 20:53:12,129 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,150 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,151 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,198 INFO spawned: 'customizer_reader' with pid 76
|
||||
2025-12-18 20:53:12,226 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,226 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,263 INFO spawned: 'customizer_writer' with pid 78
|
||||
2025-12-18 20:53:12,315 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,315 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,371 INFO spawned: 'mesh' with pid 81
|
||||
2025-12-18 20:53:12,372 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,372 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,372 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,419 INFO spawned: 'customizer_reader' with pid 82
|
||||
2025-12-18 20:53:12,470 INFO spawned: 'customizer_writer' with pid 84
|
||||
2025-12-18 20:53:12,482 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,530 INFO spawned: 'mesh' with pid 85
|
||||
2025-12-18 20:53:12,531 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,531 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,563 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,563 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,607 INFO spawned: 'customizer_reader' with pid 88
|
||||
2025-12-18 20:53:12,632 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,633 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,656 INFO spawned: 'customizer_writer' with pid 90
|
||||
2025-12-18 20:53:12,679 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,690 INFO spawned: 'mesh' with pid 91
|
||||
2025-12-18 20:53:12,732 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,758 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,758 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,792 INFO spawned: 'customizer_reader' with pid 94
|
||||
2025-12-18 20:53:12,830 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,830 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,858 INFO spawned: 'customizer_writer' with pid 96
|
||||
2025-12-18 20:53:12,859 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,933 INFO spawned: 'mesh' with pid 98
|
||||
2025-12-18 20:53:12,934 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,962 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,962 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,991 INFO spawned: 'customizer_reader' with pid 100
|
||||
2025-12-18 20:53:13,025 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,027 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,074 INFO spawned: 'customizer_writer' with pid 102
|
||||
2025-12-18 20:53:13,083 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,119 INFO spawned: 'mesh' with pid 104
|
||||
2025-12-18 20:53:13,150 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,163 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,165 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,201 INFO spawned: 'customizer_reader' with pid 106
|
||||
2025-12-18 20:53:13,259 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,264 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,484 INFO spawned: 'customizer_writer' with pid 109
|
||||
2025-12-18 20:53:13,571 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,571 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,571 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,589 INFO spawned: 'mesh' with pid 111
|
||||
2025-12-18 20:53:13,630 INFO spawned: 'customizer_reader' with pid 112
|
||||
2025-12-18 20:53:13,716 INFO spawned: 'customizer_writer' with pid 113
|
||||
2025-12-18 20:53:13,998 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,998 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,999 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,999 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,999 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,031 INFO spawned: 'mesh' with pid 117
|
||||
2025-12-18 20:53:14,208 INFO spawned: 'customizer_reader' with pid 118
|
||||
2025-12-18 20:53:14,235 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,236 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,236 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,325 INFO spawned: 'customizer_writer' with pid 120
|
||||
2025-12-18 20:53:14,435 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,447 INFO spawned: 'mesh' with pid 122
|
||||
2025-12-18 20:53:14,448 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,528 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,528 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,628 INFO spawned: 'customizer_reader' with pid 124
|
||||
2025-12-18 20:53:14,779 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,786 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,811 INFO spawned: 'mesh' with pid 126
|
||||
2025-12-18 20:53:14,865 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,866 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,961 INFO spawned: 'customizer_writer' with pid 128
|
||||
2025-12-18 20:53:15,052 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,099 INFO spawned: 'customizer_reader' with pid 130
|
||||
2025-12-18 20:53:15,118 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,156 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,190 INFO spawned: 'mesh' with pid 132
|
||||
2025-12-18 20:53:15,223 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,223 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,259 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,345 INFO spawned: 'customizer_writer' with pid 134
|
||||
2025-12-18 20:53:15,361 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,441 INFO spawned: 'customizer_reader' with pid 136
|
||||
2025-12-18 20:53:15,441 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,479 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,480 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,480 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,526 INFO spawned: 'mesh' with pid 138
|
||||
2025-12-18 20:53:15,615 INFO spawned: 'customizer_writer' with pid 139
|
||||
2025-12-18 20:53:15,674 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,674 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,695 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,750 INFO spawned: 'customizer_reader' with pid 142
|
||||
2025-12-18 20:53:15,850 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,850 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,893 INFO spawned: 'mesh' with pid 145
|
||||
2025-12-18 20:53:15,922 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,941 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,967 INFO spawned: 'customizer_writer' with pid 146
|
||||
2025-12-18 20:53:16,023 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,144 INFO spawned: 'customizer_reader' with pid 148
|
||||
2025-12-18 20:53:16,144 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,171 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,240 INFO spawned: 'mesh' with pid 150
|
||||
2025-12-18 20:53:16,264 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,299 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,299 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,366 INFO spawned: 'customizer_writer' with pid 153
|
||||
2025-12-18 20:53:16,392 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,444 INFO spawned: 'customizer_reader' with pid 154
|
||||
2025-12-18 20:53:16,461 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,496 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,531 INFO spawned: 'mesh' with pid 156
|
||||
2025-12-18 20:53:16,580 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,595 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,595 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,657 INFO spawned: 'customizer_writer' with pid 158
|
||||
2025-12-18 20:53:16,704 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,706 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,745 INFO spawned: 'customizer_reader' with pid 160
|
||||
2025-12-18 20:53:16,773 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,840 INFO spawned: 'mesh' with pid 162
|
||||
2025-12-18 20:53:16,840 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,931 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,931 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,997 INFO spawned: 'customizer_writer' with pid 165
|
||||
2025-12-18 20:53:17,002 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,057 INFO spawned: 'mesh' with pid 166
|
||||
2025-12-18 20:53:17,061 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,065 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,065 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,168 INFO spawned: 'customizer_reader' with pid 167
|
||||
2025-12-18 20:53:17,288 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,289 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,363 INFO spawned: 'customizer_writer' with pid 170
|
||||
2025-12-18 20:53:17,383 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,383 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,415 INFO spawned: 'mesh' with pid 172
|
||||
2025-12-18 20:53:17,443 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,443 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,485 INFO spawned: 'customizer_reader' with pid 173
|
||||
2025-12-18 20:53:17,566 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,567 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,658 INFO spawned: 'mesh' with pid 176
|
||||
2025-12-18 20:53:17,659 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,660 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,701 INFO spawned: 'customizer_writer' with pid 178
|
||||
2025-12-18 20:53:17,768 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,829 INFO spawned: 'customizer_reader' with pid 180
|
||||
2025-12-18 20:53:17,838 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,851 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,918 INFO spawned: 'mesh' with pid 182
|
||||
2025-12-18 20:53:17,936 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,978 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,992 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,033 INFO spawned: 'customizer_writer' with pid 184
|
||||
2025-12-18 20:53:18,061 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,129 INFO spawned: 'customizer_reader' with pid 185
|
||||
2025-12-18 20:53:18,130 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,254 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,254 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,254 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,289 INFO spawned: 'mesh' with pid 189
|
||||
2025-12-18 20:53:18,339 INFO spawned: 'customizer_writer' with pid 190
|
||||
2025-12-18 20:53:18,412 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,412 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,460 INFO spawned: 'customizer_reader' with pid 192
|
||||
2025-12-18 20:53:18,460 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,512 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,515 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,584 INFO spawned: 'mesh' with pid 194
|
||||
2025-12-18 20:53:18,615 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,615 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,675 INFO spawned: 'customizer_writer' with pid 196
|
||||
2025-12-18 20:53:18,676 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,774 INFO spawned: 'customizer_reader' with pid 198
|
||||
2025-12-18 20:53:18,791 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,821 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,822 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,945 INFO spawned: 'mesh' with pid 201
|
||||
2025-12-18 20:53:18,975 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,975 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,975 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,016 INFO spawned: 'customizer_reader' with pid 202
|
||||
2025-12-18 20:53:19,154 INFO spawned: 'customizer_writer' with pid 204
|
||||
2025-12-18 20:53:19,155 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,240 INFO spawned: 'mesh' with pid 206
|
||||
2025-12-18 20:53:19,240 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,240 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,338 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,338 WARN exited: customizer_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,403 INFO spawned: 'customizer_reader' with pid 208
|
||||
2025-12-18 20:53:19,451 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,451 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,583 INFO spawned: 'customizer_writer' with pid 210
|
||||
2025-12-18 20:53:19,584 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,584 WARN exited: customizer_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,653 INFO spawned: 'mesh' with pid 213
|
||||
2025-12-18 20:53:19,952 INFO spawned: 'customizer_writer' with pid 214
|
||||
2025-12-18 20:53:19,983 WARN exited: customizer_reader (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,984 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,984 INFO waiting for mesh, customizer_writer, nginx to die
|
||||
2025-12-18 20:53:20,019 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,019 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,019 INFO stopped: nginx (exit status 0)
|
||||
2025-12-18 20:53:20,180 WARN stopped: customizer_writer (exit status 1)
|
||||
2025-12-18 20:53:20,212 WARN stopped: mesh (terminated by SIGTERM)
|
||||
2026-01-25 19:02:19,701 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.
|
||||
2026-01-25 19:02:19,709 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-01-25 19:02:19,709 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:19,709 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-01-25 19:02:19,775 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:19,776 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:19,776 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:20,798 INFO spawned: 'mesh' with pid 32
|
||||
2026-01-25 19:02:20,866 INFO spawned: 'customizer_reader' with pid 33
|
||||
2026-01-25 19:02:20,944 INFO spawned: 'customizer_writer' with pid 34
|
||||
2026-01-25 19:02:21,121 INFO spawned: 'nginx' with pid 35
|
||||
2026-01-25 19:02:22,100 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,100 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,100 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,100 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:21,869 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.
|
||||
2026-02-04 12:30:21,871 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-02-04 12:30:21,871 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:21,871 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-04 12:30:22,181 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:22,181 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:22,187 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:23,194 INFO spawned: 'mesh' with pid 26
|
||||
2026-02-04 12:30:23,231 INFO spawned: 'customizer_reader' with pid 27
|
||||
2026-02-04 12:30:23,257 INFO spawned: 'customizer_writer' with pid 28
|
||||
2026-02-04 12:30:23,323 INFO spawned: 'nginx' with pid 30
|
||||
2026-02-04 12:30:23,766 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,766 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,766 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,766 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,379 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.
|
||||
2026-02-04 14:57:35,394 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-02-04 14:57:35,394 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,394 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-04 14:57:35,769 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:35,769 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:35,770 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:36,795 INFO spawned: 'mesh' with pid 32
|
||||
2026-02-04 14:57:36,849 INFO spawned: 'customizer_reader' with pid 33
|
||||
2026-02-04 14:57:36,960 INFO spawned: 'customizer_writer' with pid 34
|
||||
2026-02-04 14:57:37,070 INFO spawned: 'nginx' with pid 37
|
||||
2026-02-04 14:57:38,125 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,126 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,127 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,128 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:49,819 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.
|
||||
2026-02-04 17:30:49,827 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-02-04 17:30:49,827 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:49,827 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-04 17:30:50,143 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:50,143 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:50,152 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:51,167 INFO spawned: 'mesh' with pid 25
|
||||
2026-02-04 17:30:51,221 INFO spawned: 'customizer_reader' with pid 26
|
||||
2026-02-04 17:30:51,319 INFO spawned: 'customizer_writer' with pid 27
|
||||
2026-02-04 17:30:51,378 INFO spawned: 'nginx' with pid 29
|
||||
2026-02-04 17:30:52,427 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,427 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,427 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,427 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,662 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.
|
||||
2026-02-07 14:26:22,674 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-02-07 14:26:22,677 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:22,677 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-07 14:26:23,020 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:23,021 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:23,021 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:24,054 INFO spawned: 'mesh' with pid 35
|
||||
2026-02-07 14:26:24,129 INFO spawned: 'customizer_reader' with pid 36
|
||||
2026-02-07 14:26:24,174 INFO spawned: 'customizer_writer' with pid 37
|
||||
2026-02-07 14:26:24,331 INFO spawned: 'nginx' with pid 39
|
||||
2026-02-07 14:26:25,368 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:25,369 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:25,369 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:25,369 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:19,525 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.
|
||||
2026-02-20 16:02:19,537 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-02-20 16:02:19,537 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:19,537 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-20 16:02:19,927 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:19,927 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:19,927 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:20,951 INFO spawned: 'mesh' with pid 29
|
||||
2026-02-20 16:02:21,108 INFO spawned: 'customizer_reader' with pid 30
|
||||
2026-02-20 16:02:21,248 INFO spawned: 'customizer_writer' with pid 32
|
||||
2026-02-20 16:02:21,407 INFO spawned: 'nginx' with pid 33
|
||||
2026-02-20 16:02:22,094 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,094 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,095 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,097 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:31,585 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.
|
||||
2026-03-04 12:10:31,592 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-03-04 12:10:31,592 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,592 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-03-04 12:10:31,916 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,920 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,921 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,953 INFO spawned: 'mesh' with pid 31
|
||||
2026-03-04 12:10:33,000 INFO spawned: 'customizer_reader' with pid 32
|
||||
2026-03-04 12:10:33,082 INFO spawned: 'customizer_writer' with pid 33
|
||||
2026-03-04 12:10:33,210 INFO spawned: 'nginx' with pid 35
|
||||
2026-03-04 12:10:34,269 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,270 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,270 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,270 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:45,248 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.
|
||||
2026-03-23 09:52:45,252 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-03-23 09:52:45,254 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:45,254 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-03-23 09:52:45,585 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:45,588 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:45,588 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:46,609 INFO spawned: 'mesh' with pid 32
|
||||
2026-03-23 09:52:46,703 INFO spawned: 'customizer_reader' with pid 33
|
||||
2026-03-23 09:52:46,768 INFO spawned: 'customizer_writer' with pid 34
|
||||
2026-03-23 09:52:46,972 INFO spawned: 'nginx' with pid 36
|
||||
2026-03-23 09:52:47,978 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,978 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,978 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,978 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:23,220 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.
|
||||
2026-03-25 17:35:23,225 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-03-25 17:35:23,226 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:23,226 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-03-25 17:35:23,587 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:23,590 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:23,591 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:24,620 INFO spawned: 'mesh' with pid 25
|
||||
2026-03-25 17:35:24,693 INFO spawned: 'customizer_reader' with pid 26
|
||||
2026-03-25 17:35:24,795 INFO spawned: 'customizer_writer' with pid 27
|
||||
2026-03-25 17:35:24,856 INFO spawned: 'nginx' with pid 29
|
||||
2026-03-25 17:35:25,716 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:25,716 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:25,716 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:25,716 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,360 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.
|
||||
2026-03-26 07:04:03,378 INFO Included extra file "/opt/supervisor.d/customizer.conf" during parsing
|
||||
2026-03-26 07:04:03,378 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,378 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-03-26 07:04:03,733 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,733 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,733 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,761 INFO spawned: 'mesh' with pid 32
|
||||
2026-03-26 07:04:04,832 INFO spawned: 'customizer_reader' with pid 33
|
||||
2026-03-26 07:04:04,877 INFO spawned: 'customizer_writer' with pid 34
|
||||
2026-03-26 07:04:04,984 INFO spawned: 'nginx' with pid 35
|
||||
2026-03-26 07:04:05,988 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,988 INFO success: customizer_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,988 INFO success: customizer_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,988 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because one or more lines are too long
@@ -0,0 +1,647 @@
|
||||
INFO: 2026/03/26 07:18:45 main.go:49: =====================СТАРТ СБОРА ДАННЫХ=====================
|
||||
INFO: 2026/03/26 07:18:45 main.go:53: Уточняем, что утилита запущена на сервере с платформой
|
||||
INFO: 2026/03/26 07:18:45 main.go:55: Получаем информацию о BIOS : bios_info
|
||||
INFO: 2026/03/26 07:18:45 main.go:61: Получаем информацию об операционной системе: os_info
|
||||
WARN: 2026/03/26 07:18:45 main.go:66: ошибка чтения asrta_version
|
||||
INFO: 2026/03/26 07:18:45 main.go:70: Получаем информацию об установленных пакетах: installed_packages
|
||||
INFO: 2026/03/26 07:18:45 main.go:84: Получаем содержимое файла /root/.bash_history
|
||||
INFO: 2026/03/26 07:18:45 main.go:90: Получаем информацию о файловой системе сервера: fs_informations
|
||||
INFO: 2026/03/26 07:18:45 main.go:96: Получаем информацию о средней загрзке сервера: load_average
|
||||
INFO: 2026/03/26 07:18:45 main.go:102: Получаем информацию о процессоре: cpu
|
||||
INFO: 2026/03/26 07:18:45 main.go:108: Получаем информацию о памяти: ram
|
||||
INFO: 2026/03/26 07:18:45 main.go:114: Получаем информацию об аптайме: uptime
|
||||
INFO: 2026/03/26 07:18:45 main.go:120: Получаем информацию о службе времени: time_service
|
||||
INFO: 2026/03/26 07:18:46 main.go:126: Получаем информацию о записях в journalctl xe p4 since 1 day ago: journalctl_entries
|
||||
WARN: 2026/03/26 07:18:46 main.go:129: Ошибка десериализации данных: json: cannot unmarshal array into Go struct field journalctlEntry.MESSAGE of type string в итерации {
|
||||
"_SYSTEMD_SLICE" : "system.slice",
|
||||
"_CMDLINE" : "python3 /opt/ispsystem/dci/service/repochecker.py -m dci -v v3",
|
||||
"SYSLOG_IDENTIFIER" : "repochecker",
|
||||
"__REALTIME_TIMESTAMP" : "1774508722505416",
|
||||
"_RUNTIME_SCOPE" : "system",
|
||||
"REQUEST_INFO" : "**NO INFO**",
|
||||
"PRIORITY" : "4",
|
||||
"_UID" : "0",
|
||||
"_SYSTEMD_CGROUP" : "/system.slice/docker-839b53394c62b7ac0d649eb34f48c2f12a7bc18deb11b433b8db44af91a7d86a.scope",
|
||||
"_EXE" : "/usr/bin/python3.9",
|
||||
"__CURSOR" : "s=659ff0cd80b246a38a391a7b8193fe2e;i=1e9c8041;b=2f88a318cf86482a9fbf2f51b92169a1;m=62f5484;t=64de8020e46c8;x=892761909d44a230",
|
||||
"_PID" : "7244",
|
||||
"CODE" : "repochecker.get_repositories /opt/ispsystem/dci/service/repochecker.py:86",
|
||||
"__SEQNUM" : "513572929",
|
||||
"_COMM" : "python3",
|
||||
"_SYSTEMD_INVOCATION_ID" : "fbdaf18364774a75b73d5c65d1822e40",
|
||||
"__SEQNUM_ID" : "659ff0cd80b246a38a391a7b8193fe2e",
|
||||
"_TRANSPORT" : "journal",
|
||||
"_SYSTEMD_UNIT" : "docker-839b53394c62b7ac0d649eb34f48c2f12a7bc18deb11b433b8db44af91a7d86a.scope",
|
||||
"_MACHINE_ID" : "c7025f8e20cfa4a59321e1cd6e27e0f5",
|
||||
"_GID" : "0",
|
||||
"__MONOTONIC_TIMESTAMP" : "103765124",
|
||||
"_CAP_EFFECTIVE" : "a80425fb",
|
||||
"_BOOT_ID" : "2f88a318cf86482a9fbf2f51b92169a1",
|
||||
"_HOSTNAME" : "dci-1",
|
||||
"CREATED" : "2026-03-26 07:05:22.504140",
|
||||
"_SELINUX_CONTEXT" : "docker-default (enforce)\n",
|
||||
"_SOURCE_REALTIME_TIMESTAMP" : "1774508722504532",
|
||||
"PRODUCT" : "dci",
|
||||
"MESSAGE" : [
|
||||
71,
|
||||
111,
|
||||
116,
|
||||
32,
|
||||
101,
|
||||
114,
|
||||
114,
|
||||
111,
|
||||
114,
|
||||
58,
|
||||
32,
|
||||
84,
|
||||
114,
|
||||
97,
|
||||
99,
|
||||
101,
|
||||
98,
|
||||
97,
|
||||
99,
|
||||
107,
|
||||
32,
|
||||
40,
|
||||
109,
|
||||
111,
|
||||
115,
|
||||
116,
|
||||
32,
|
||||
114,
|
||||
101,
|
||||
99,
|
||||
101,
|
||||
110,
|
||||
116,
|
||||
32,
|
||||
99,
|
||||
97,
|
||||
108,
|
||||
108,
|
||||
32,
|
||||
108,
|
||||
97,
|
||||
115,
|
||||
116,
|
||||
41,
|
||||
58,
|
||||
10,
|
||||
32,
|
||||
32,
|
||||
70,
|
||||
105,
|
||||
108,
|
||||
101,
|
||||
32,
|
||||
34,
|
||||
47,
|
||||
111,
|
||||
112,
|
||||
116,
|
||||
47,
|
||||
105,
|
||||
115,
|
||||
112,
|
||||
115,
|
||||
121,
|
||||
115,
|
||||
116,
|
||||
101,
|
||||
109,
|
||||
47,
|
||||
100,
|
||||
99,
|
||||
105,
|
||||
47,
|
||||
115,
|
||||
101,
|
||||
114,
|
||||
118,
|
||||
105,
|
||||
99,
|
||||
101,
|
||||
47,
|
||||
114,
|
||||
101,
|
||||
112,
|
||||
111,
|
||||
99,
|
||||
104,
|
||||
101,
|
||||
99,
|
||||
107,
|
||||
101,
|
||||
114,
|
||||
46,
|
||||
112,
|
||||
121,
|
||||
34,
|
||||
44,
|
||||
32,
|
||||
108,
|
||||
105,
|
||||
110,
|
||||
101,
|
||||
32,
|
||||
56,
|
||||
49,
|
||||
44,
|
||||
32,
|
||||
105,
|
||||
110,
|
||||
32,
|
||||
103,
|
||||
101,
|
||||
116,
|
||||
95,
|
||||
114,
|
||||
101,
|
||||
112,
|
||||
111,
|
||||
115,
|
||||
105,
|
||||
116,
|
||||
111,
|
||||
114,
|
||||
105,
|
||||
101,
|
||||
115,
|
||||
10,
|
||||
32,
|
||||
32,
|
||||
32,
|
||||
32,
|
||||
114,
|
||||
101,
|
||||
115,
|
||||
112,
|
||||
111,
|
||||
110,
|
||||
115,
|
||||
101,
|
||||
46,
|
||||
114,
|
||||
97,
|
||||
105,
|
||||
115,
|
||||
101,
|
||||
95,
|
||||
102,
|
||||
111,
|
||||
114,
|
||||
95,
|
||||
115,
|
||||
116,
|
||||
97,
|
||||
116,
|
||||
117,
|
||||
115,
|
||||
40,
|
||||
41,
|
||||
10,
|
||||
32,
|
||||
32,
|
||||
70,
|
||||
105,
|
||||
108,
|
||||
101,
|
||||
32,
|
||||
34,
|
||||
47,
|
||||
117,
|
||||
115,
|
||||
114,
|
||||
47,
|
||||
108,
|
||||
111,
|
||||
99,
|
||||
97,
|
||||
108,
|
||||
47,
|
||||
108,
|
||||
105,
|
||||
98,
|
||||
47,
|
||||
112,
|
||||
121,
|
||||
116,
|
||||
104,
|
||||
111,
|
||||
110,
|
||||
51,
|
||||
46,
|
||||
57,
|
||||
47,
|
||||
115,
|
||||
105,
|
||||
116,
|
||||
101,
|
||||
45,
|
||||
112,
|
||||
97,
|
||||
99,
|
||||
107,
|
||||
97,
|
||||
103,
|
||||
101,
|
||||
115,
|
||||
47,
|
||||
112,
|
||||
121,
|
||||
100,
|
||||
99,
|
||||
105,
|
||||
95,
|
||||
105,
|
||||
115,
|
||||
112,
|
||||
95,
|
||||
99,
|
||||
108,
|
||||
105,
|
||||
101,
|
||||
110,
|
||||
116,
|
||||
47,
|
||||
114,
|
||||
101,
|
||||
115,
|
||||
112,
|
||||
111,
|
||||
110,
|
||||
115,
|
||||
101,
|
||||
46,
|
||||
112,
|
||||
121,
|
||||
34,
|
||||
44,
|
||||
32,
|
||||
108,
|
||||
105,
|
||||
110,
|
||||
101,
|
||||
32,
|
||||
51,
|
||||
52,
|
||||
44,
|
||||
32,
|
||||
105,
|
||||
110,
|
||||
32,
|
||||
114,
|
||||
97,
|
||||
105,
|
||||
115,
|
||||
101,
|
||||
95,
|
||||
102,
|
||||
111,
|
||||
114,
|
||||
95,
|
||||
115,
|
||||
116,
|
||||
97,
|
||||
116,
|
||||
117,
|
||||
115,
|
||||
10,
|
||||
32,
|
||||
32,
|
||||
32,
|
||||
32,
|
||||
114,
|
||||
97,
|
||||
105,
|
||||
115,
|
||||
101,
|
||||
32,
|
||||
82,
|
||||
117,
|
||||
110,
|
||||
116,
|
||||
105,
|
||||
109,
|
||||
101,
|
||||
69,
|
||||
114,
|
||||
114,
|
||||
111,
|
||||
114,
|
||||
40,
|
||||
102,
|
||||
34,
|
||||
78,
|
||||
111,
|
||||
116,
|
||||
32,
|
||||
115,
|
||||
117,
|
||||
99,
|
||||
99,
|
||||
101,
|
||||
115,
|
||||
115,
|
||||
32,
|
||||
114,
|
||||
101,
|
||||
116,
|
||||
117,
|
||||
114,
|
||||
110,
|
||||
32,
|
||||
99,
|
||||
111,
|
||||
100,
|
||||
101,
|
||||
32,
|
||||
39,
|
||||
123,
|
||||
115,
|
||||
101,
|
||||
108,
|
||||
102,
|
||||
46,
|
||||
115,
|
||||
116,
|
||||
97,
|
||||
116,
|
||||
117,
|
||||
115,
|
||||
95,
|
||||
99,
|
||||
111,
|
||||
100,
|
||||
101,
|
||||
125,
|
||||
39,
|
||||
58,
|
||||
32,
|
||||
39,
|
||||
123,
|
||||
115,
|
||||
101,
|
||||
108,
|
||||
102,
|
||||
46,
|
||||
116,
|
||||
101,
|
||||
120,
|
||||
116,
|
||||
125,
|
||||
39,
|
||||
34,
|
||||
41,
|
||||
10,
|
||||
82,
|
||||
117,
|
||||
110,
|
||||
116,
|
||||
105,
|
||||
109,
|
||||
101,
|
||||
69,
|
||||
114,
|
||||
114,
|
||||
111,
|
||||
114,
|
||||
58,
|
||||
32,
|
||||
78,
|
||||
111,
|
||||
116,
|
||||
32,
|
||||
115,
|
||||
117,
|
||||
99,
|
||||
99,
|
||||
101,
|
||||
115,
|
||||
115,
|
||||
32,
|
||||
114,
|
||||
101,
|
||||
116,
|
||||
117,
|
||||
114,
|
||||
110,
|
||||
32,
|
||||
99,
|
||||
111,
|
||||
100,
|
||||
101,
|
||||
32,
|
||||
39,
|
||||
53,
|
||||
48,
|
||||
50,
|
||||
39,
|
||||
58,
|
||||
32,
|
||||
39,
|
||||
60,
|
||||
104,
|
||||
116,
|
||||
109,
|
||||
108,
|
||||
62,
|
||||
13,
|
||||
10,
|
||||
60,
|
||||
104,
|
||||
101,
|
||||
97,
|
||||
100,
|
||||
62,
|
||||
60,
|
||||
116,
|
||||
105,
|
||||
116,
|
||||
108,
|
||||
101,
|
||||
62,
|
||||
53,
|
||||
48,
|
||||
50,
|
||||
32,
|
||||
66,
|
||||
97,
|
||||
100,
|
||||
32,
|
||||
71,
|
||||
97,
|
||||
116,
|
||||
101,
|
||||
119,
|
||||
97,
|
||||
121,
|
||||
60,
|
||||
47,
|
||||
116,
|
||||
105,
|
||||
116,
|
||||
108,
|
||||
101,
|
||||
62,
|
||||
60,
|
||||
47,
|
||||
104,
|
||||
101,
|
||||
97,
|
||||
100,
|
||||
62,
|
||||
13,
|
||||
10,
|
||||
60,
|
||||
98,
|
||||
111,
|
||||
100,
|
||||
121,
|
||||
62,
|
||||
13,
|
||||
10,
|
||||
60,
|
||||
99,
|
||||
101,
|
||||
110,
|
||||
116,
|
||||
101,
|
||||
114,
|
||||
62,
|
||||
60,
|
||||
104,
|
||||
49,
|
||||
62,
|
||||
53,
|
||||
48,
|
||||
50,
|
||||
32,
|
||||
66,
|
||||
97,
|
||||
100,
|
||||
32,
|
||||
71,
|
||||
97,
|
||||
116,
|
||||
101,
|
||||
119,
|
||||
97,
|
||||
121,
|
||||
60,
|
||||
47,
|
||||
104,
|
||||
49,
|
||||
62,
|
||||
60,
|
||||
47,
|
||||
99,
|
||||
101,
|
||||
110,
|
||||
116,
|
||||
101,
|
||||
114,
|
||||
62,
|
||||
13,
|
||||
10,
|
||||
60,
|
||||
104,
|
||||
114,
|
||||
62,
|
||||
60,
|
||||
99,
|
||||
101,
|
||||
110,
|
||||
116,
|
||||
101,
|
||||
114,
|
||||
62,
|
||||
110,
|
||||
103,
|
||||
105,
|
||||
110,
|
||||
120,
|
||||
60,
|
||||
47,
|
||||
99,
|
||||
101,
|
||||
110,
|
||||
116,
|
||||
101,
|
||||
114,
|
||||
62,
|
||||
13,
|
||||
10,
|
||||
60,
|
||||
47,
|
||||
98,
|
||||
111,
|
||||
100,
|
||||
121,
|
||||
62,
|
||||
13,
|
||||
10,
|
||||
60,
|
||||
47,
|
||||
104,
|
||||
116,
|
||||
109,
|
||||
108,
|
||||
62,
|
||||
13,
|
||||
10,
|
||||
39,
|
||||
10
|
||||
]
|
||||
}
|
||||
INFO: 2026/03/26 07:18:46 main.go:132: Получаем информацию о фаерволах: firewalls
|
||||
INFO: 2026/03/26 07:18:46 main.go:138: Получаем информацию о правилах nftables nft list ruleset
|
||||
INFO: 2026/03/26 07:18:46 main.go:147: Получаем информацию о сетевых настройках: network_config
|
||||
WARN: 2026/03/26 07:18:46 main.go:150: Ошибка при получении содержимого run NetworkManager
|
||||
INFO: 2026/03/26 07:18:46 main.go:153: Получаем информацию о доступности необходимых интернет-ресурсов: internet_required
|
||||
WARN: 2026/03/26 07:18:47 main.go:158: %!s(<nil>) Ошибка HTTPS http://license.ispsystem.com :: Get "https://license.ispsystem.com": dial tcp 62.109.29.191:443: connect: connection refused
|
||||
INFO: 2026/03/26 07:18:48 main.go:164: Получаем информацию о настройках безопасности
|
||||
INFO: 2026/03/26 07:18:48 main.go:182: Получаем информацию docker ps -a
|
||||
INFO: 2026/03/26 07:18:48 main.go:188: Информация о ресурсах контейнеров docker stats -a --no-stream
|
||||
INFO: 2026/03/26 07:18:51 main.go:194: Получаем логи и статус supervisord
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере swagger
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: ошибка supervisorctl status в dci_back: exit status 3
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере graphite_carbonapi
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: ошибка supervisorctl status в ipmi_proxy_client: exit status 3
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере carbon_clickhouse
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере vector_master
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере graphite_clickhouse
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: ошибка supervisorctl status в updater: exit status 3
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере dci_front
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: ошибка supervisorctl status в search: exit status 3
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере clickhouse_server
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере auth_front
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: ошибка supervisorctl status в backup: exit status 3
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере vmalert
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: ошибка supervisorctl status в input: exit status 3
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере msg_queue
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере consul
|
||||
WARN: 2026/03/26 07:19:21 main.go:197: supervisord.log не найден в контейнере mysql
|
||||
INFO: 2026/03/26 07:19:21 main.go:224: Начинаем сбор данных по ПЛАТФОРМЕ
|
||||
INFO: 2026/03/26 07:19:21 main.go:245: Получаем информацию из таблицы dci_location
|
||||
INFO: 2026/03/26 07:19:21 main.go:251: Получаем base64 docker-compose из таблицы dci_location
|
||||
INFO: 2026/03/26 07:19:21 main.go:258: Получаем информацию о задачах с ошибками за месяц
|
||||
INFO: 2026/03/26 07:19:21 main.go:266: Получаем информацию о количестве оборудования по локациям
|
||||
INFO: 2026/03/26 07:19:21 main.go:272: Получаем информацию об установленных плагинах
|
||||
INFO: 2026/03/26 07:19:21 main.go:279: Получаем количество пользователей
|
||||
INFO: 2026/03/26 07:19:21 main.go:287: Проверяем наличие настроек ldap
|
||||
INFO: 2026/03/26 07:19:21 main.go:294: Получаем информацию о репозиториях операционных систем
|
||||
INFO: 2026/03/26 07:19:21 main.go:300: Получаем шаблоны ОС из репозиториев не ispsystem
|
||||
WARN: 2026/03/26 07:19:21 main.go:303: Ошибка при выполнении запроса к dci_os_template : Ошибка выполнения запроса SELECT id,name,filename,macro,metainfo,directory_name,repository,size from dci_os_template where repository not it (1);: Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'it (1)' at line 1
|
||||
INFO: 2026/03/26 07:19:21 main.go:307: Получаем инфорамцию о доверенных серверах в Real IP
|
||||
INFO: 2026/03/26 07:19:21 main.go:314: Получаем информацию о заданиях резервного копирования платформы
|
||||
INFO: 2026/03/26 07:19:21 main.go:322: Получаем информацию о лицензии
|
||||
WARN: 2026/03/26 07:19:22 main.go:325: Ошибка выполнения команды dci license info : exit status 2
|
||||
INFO: 2026/03/26 07:19:22 main.go:331: Копируем config.json
|
||||
INFO: 2026/03/26 07:19:22 main.go:340: Копируем install.log
|
||||
INFO: 2026/03/26 07:19:22 main.go:349: Копируем docker-compose.yaml
|
||||
INFO: 2026/03/26 07:19:22 main.go:357: Собираем названия файлов из директории /opt/ispsystem/
|
||||
INFO: 2026/03/26 07:19:22 main.go:366: =====================КОНЕЦ СБОРА ДАННЫХ=====================
|
||||
ERROR: 2026/03/26 07:19:22 main.go:385: Оборудование указано неверно. Правильный формат оборудования " -hw switch:13 " где switch тип оборудования (switch, pdu, server, ups, san), а 13 его id
|
||||
@@ -0,0 +1,899 @@
|
||||
version: "3.7"
|
||||
services:
|
||||
alert:
|
||||
container_name: alert
|
||||
image: docker-registry.ispsystem.com/team/common/alert-settings/alma:1.0.15
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
PRODUCT: dci
|
||||
PROXY_MODE: saas
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_alert_settings
|
||||
auth_back4:
|
||||
container_name: auth_back
|
||||
#image: docker-registry.ispsystem.com/ispsystem/experimental/auth/debian:5.0.17
|
||||
image: registry-dev.ispsystem.net/ispsystem/experimental/auth/alma:ps-10989
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
FEAT_AUTH_V3_DEPRECATE: "on"
|
||||
FEAT_AUTH_V4: "on"
|
||||
LOG_LEVEL: trace
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_auth_v4
|
||||
auth_front:
|
||||
container_name: auth_front
|
||||
image: docker-registry.ispsystem.com/team/auth/front/box:9.15.0
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_auth_front
|
||||
batch:
|
||||
container_name: batch
|
||||
image: docker-registry.ispsystem.com/ispsystem/experimental/batch/alma:1.0.3
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
PRODUCT: dci
|
||||
PROXY_SERVICE: input:1500
|
||||
networks:
|
||||
auth: null
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_batch
|
||||
carbon_clickhouse:
|
||||
container_name: carbon_clickhouse
|
||||
image: docker-registry.ispsystem.com/team/dci/carbon-clickhouse:0.0.3
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/graphite_storage:/opt/ispsystem/graphite_storage
|
||||
environment:
|
||||
CLICKHOUSE_DATABASE: dci
|
||||
CLICKHOUSE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
CLICKHOUSE_USER: root
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- clickhouse_server
|
||||
restart: always
|
||||
logging:
|
||||
driver: json-file
|
||||
options:
|
||||
max-file: "10"
|
||||
max-size: 1m
|
||||
clickhouse_server:
|
||||
container_name: clickhouse_server
|
||||
image: docker-registry.ispsystem.com/team/dci/clickhouse:0.2.0
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/clickhouse_storage:/var/lib/clickhouse
|
||||
environment:
|
||||
CLICKHOUSE_DATABASE: dci
|
||||
CLICKHOUSE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
CLICKHOUSE_USER: root
|
||||
networks:
|
||||
auth: null
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_clickhouse_server
|
||||
ulimits:
|
||||
nofile:
|
||||
hard: 262144
|
||||
soft: 262144
|
||||
consul:
|
||||
container_name: consul
|
||||
image: docker-registry.ispsystem.com/consul:1.8.5
|
||||
environment:
|
||||
CONSUL_BIND_INTERFACE: eth0
|
||||
CONSUL_CLIENT_INTERFACE: eth0
|
||||
CONSUL_LOCAL_CONFIG: '{"datacenter":"testing","server":true,"bootstrap":true}'
|
||||
networks:
|
||||
auth: null
|
||||
restart: always
|
||||
logging:
|
||||
driver: json-file
|
||||
options:
|
||||
max-file: "10"
|
||||
max-size: 1m
|
||||
consumer:
|
||||
container_name: eservice_consumer
|
||||
image: docker-registry.ispsystem.com/team/dci/equip-consumer/debian:6.5.1
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
CLICKHOUSE_DATABASE: dci
|
||||
CLICKHOUSE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
CLICKHOUSE_USER: root
|
||||
GRAPHITE_HOST: carbon_clickhouse
|
||||
GRAPHITE_PORT: "2103"
|
||||
INSTANCE_ID: "1"
|
||||
NETFLOW_FLUSH_COUNT: "100"
|
||||
NETFLOW_FLUSH_TTL: "5"
|
||||
PRODUCT: dci
|
||||
REDIS_HOST: eservice_msg_queue
|
||||
REDIS_PASSWORD: ${DATABASE_PASSWORD}
|
||||
REDIS_PORT: "6379"
|
||||
REDIS_STREAM_STATISTIC_NAME: equip_statistic
|
||||
REDIS_STREAM_STATUS_NAME: equip_status
|
||||
WORKER_GROUP_NAME: daemon_worker
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- eservice
|
||||
- taskmgr
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_consumer
|
||||
customizer:
|
||||
container_name: customizer
|
||||
image: docker-registry.ispsystem.com/team/common/customizer/alma:1.6.9
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
DOMAIN: ${DOMAIN}
|
||||
INSTANCE_ID: "1"
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_customizer
|
||||
dci_alert_wrapper:
|
||||
container_name: alert_wrapper
|
||||
image: docker-registry.ispsystem.com/team/dci/dci_alert_wrapper/alma:2.7.1
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
- /opt/ispsystem/dci/vmalert/:/opt/ispsystem/vmalert/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
DATABASE_USER: root
|
||||
INSTANCE_ID: "1"
|
||||
LIC_TOKEN: ${TOKEN}
|
||||
NOTICE_CENTER: notice-center
|
||||
PRODUCT: dci
|
||||
REDIS_HOST: eservice_msg_queue
|
||||
REDIS_PASSWORD: ${DATABASE_PASSWORD}
|
||||
REDIS_PORT: "6379"
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- alert
|
||||
- notice-center
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_alert_wrapper
|
||||
dci_back:
|
||||
container_name: dci_back
|
||||
image: docker-registry.ispsystem.com/team/dci/back/alma:11.4.1
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
- /opt/ispsystem/dci/firmware/:/opt/ispsystem/dci/firmware/
|
||||
- /opt/ispsystem/dci/socket/:/opt/ispsystem/dci/socket/
|
||||
- /opt/ispsystem/license:/opt/ispsystem/license
|
||||
- /opt/ispsystem/dci/dci_back/server_monitoring:/opt/ispsystem/dci/server_monitoring
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME}
|
||||
DATABASE_NAME_AUTH: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
DATABASE_USER: root
|
||||
FEAT_AUTH_V4: "on"
|
||||
IMAGE_BIRD: docker-registry.ispsystem.com/team/dci/bird:0.0.5
|
||||
IMAGE_ESERVICE_HANDLER: docker-registry.ispsystem.com/team/dci/equip_handler:5.14.1
|
||||
IMAGE_GOFLOW: docker-registry.ispsystem.com/team/dci/goflow/alma:0.1.1
|
||||
IMAGE_KEA_DHCP: docker-registry.ispsystem.com/team/dci/kea-dhcp:0.0.7
|
||||
IMAGE_LWEB: docker-registry.ispsystem.com/team/dci/lweb:0.7.7
|
||||
IMAGE_NFSD: docker-registry.ispsystem.com/team/dci/nfs-server:0.0.1
|
||||
IMAGE_RABBITMQ: docker-registry.ispsystem.com/team/dci/flowbroker:0.1.0
|
||||
IMAGE_REDIS: docker-registry.ispsystem.com/team/dci/redis:0.1.3
|
||||
IMAGE_SMBD: docker-registry.ispsystem.com/team/dci/samba:0.0.5
|
||||
IMAGE_TFTPD: docker-registry.ispsystem.com/team/dci/tftp/alma:0.0.6
|
||||
IMAGE_VECTOR_LOC: docker-registry.ispsystem.com/team/dci/vector/location:0.1.3
|
||||
IMAGE_VMAGENT: docker-registry.ispsystem.com/team/dci/vmagent/alma:0.0.3
|
||||
LICENSE_AUTH_TOKEN: ${TOKEN}
|
||||
PRODUCT: dci
|
||||
REDIS_HOST: eservice_msg_queue
|
||||
REDIS_PASSWORD: ${DATABASE_PASSWORD}
|
||||
REDIS_PORT: "6379"
|
||||
LOG_SETTINGS_JOURNALD_LEVEL: trace
|
||||
networks:
|
||||
auth: null
|
||||
hostname: dci_back
|
||||
depends_on:
|
||||
- taskmgr
|
||||
- license
|
||||
restart: always
|
||||
dns:
|
||||
- 8.8.8.8
|
||||
- 1.1.1.1
|
||||
- 77.88.8.8
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_back
|
||||
dci_backup:
|
||||
container_name: backup
|
||||
image: docker-registry.ispsystem.com/team/dci/dci_backup/debian:2.2.4
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/socket/:/opt/ispsystem/backup/socket/
|
||||
- /opt/ispsystem/dci/backup/:/opt/ispsystem/backup/local_storage/
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
DATABASE_USER: root
|
||||
INSTANCE_ID: "1"
|
||||
PRODUCT: dci
|
||||
PROXY_SERVICE: input:1500
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_backup
|
||||
dci_front:
|
||||
container_name: dci_front
|
||||
image: docker-registry.ispsystem.com/team/dci/front/alma:0.167.8
|
||||
environment:
|
||||
BASE_HREF: /dci
|
||||
BOX: "true"
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_front
|
||||
eservice:
|
||||
container_name: eservice
|
||||
image: docker-registry.ispsystem.com/team/dci/equip_service/alma:6.6.1
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
DATABASE_USER: root
|
||||
GF_HOST: grafana
|
||||
GF_HOST_USER: grafana_user
|
||||
GF_SECURITY_ADMIN_PASSWORD: ${DATABASE_PASSWORD}
|
||||
GRAPHITE_HOST: carbon_clickhouse
|
||||
GRAPHITE_PORT: "2103"
|
||||
GRAPHITE_RENDER_HOST: graphite_carbonapi
|
||||
GRAPHITE_RENDER_PORT: "8080"
|
||||
PRODUCT: dci
|
||||
REDIS_HOST: eservice_msg_queue
|
||||
REDIS_PASSWORD: ${DATABASE_PASSWORD}
|
||||
REDIS_PORT: "6379"
|
||||
REDIS_STREAM_STATISTIC_NAME: equip_statistic
|
||||
REDIS_STREAM_STATUS_NAME: equip_status
|
||||
WORKER_GROUP_NAME: daemon_worker
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_eservice
|
||||
eservice_msg_queue:
|
||||
container_name: msg_queue
|
||||
image: docker-registry.ispsystem.com/team/dci/redis:0.1.3
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
PRODUCT: dci
|
||||
REDIS_ARGS: --save ''
|
||||
REDIS_MESSAGE_TTL: "600"
|
||||
REDIS_PASSWORD: ${DATABASE_PASSWORD}
|
||||
REDIS_PORT: "6379"
|
||||
networks:
|
||||
auth: null
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_eservice_msg_queue
|
||||
grafana:
|
||||
container_name: grafana
|
||||
image: docker-registry.ispsystem.com/team/dci/grafana:1.4.3
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/grafana/:/var/lib/grafana/
|
||||
environment:
|
||||
CLICKHOUSE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
GF_AUTH_LOGIN_COOKIE_NAME: dci6_grafana_session
|
||||
GF_SECURITY_ADMIN_PASSWORD: ${DATABASE_PASSWORD}
|
||||
GF_SECURITY_ALLOW_EMBEDDING: "true"
|
||||
GF_SERVER_ROOT_URL: '%(protocol)s://%(domain)s/grafana/'
|
||||
INSTANCE_ID: "1"
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_grafana
|
||||
grafana_user:
|
||||
container_name: grafana_user
|
||||
image: docker-registry.ispsystem.com/team/dci/grafana/user:1.4.3
|
||||
environment:
|
||||
CLICKHOUSE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
GF_AUTH_LOGIN_COOKIE_NAME: dci6_grafana_session
|
||||
GF_SECURITY_ADMIN_PASSWORD: ${DATABASE_PASSWORD}
|
||||
GF_SECURITY_ALLOW_EMBEDDING: "true"
|
||||
GF_SERVER_ROOT_URL: '%(protocol)s://%(domain)s/grafana-user/'
|
||||
INSTANCE_ID: "1"
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_grafana_user
|
||||
graphite_carbonapi:
|
||||
container_name: graphite_carbonapi
|
||||
image: docker-registry.ispsystem.com/team/dci/carbonapi:0.0.7
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- graphite_clickhouse
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_graphite_carbonapi
|
||||
graphite_clickhouse:
|
||||
container_name: graphite_clickhouse
|
||||
image: docker-registry.ispsystem.com/team/dci/graphite-clickhouse:0.0.2
|
||||
environment:
|
||||
CLICKHOUSE_DATABASE: dci
|
||||
CLICKHOUSE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
CLICKHOUSE_USER: root
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- clickhouse_server
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_graphite_clickhouse
|
||||
input:
|
||||
container_name: input
|
||||
image: docker-registry.ispsystem.com/team/common/input:2.2.4
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/socket/:/opt/ispsystem/installer/
|
||||
environment:
|
||||
BOX_MODE: "on"
|
||||
PROXY_SERVICE: input:1600
|
||||
ports:
|
||||
- mode: host
|
||||
published: 80
|
||||
target: 80
|
||||
- mode: host
|
||||
published: 443
|
||||
target: 443
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_input
|
||||
ipmgr:
|
||||
container_name: ipmgr
|
||||
image: docker-registry.ispsystem.com/team/extra/ipmgr/alma:3.5.7
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
LIFETIME: "64800"
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_ipmgr
|
||||
ipmi_proxy_v2_client:
|
||||
container_name: ipmi_proxy_client
|
||||
image: docker-registry.ispsystem.com/team/dci/ipmi_proxy_v2_client/alma:4.5.0
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
IMAGE_IPMI_PROXY_V2_SERVER: docker-registry.ispsystem.com/team/dci/ipmi_proxy_v2/alma:0.10.11
|
||||
LOG_SETTINGS_FILE_LEVEL: debug
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
hostname: ipmi_proxy_v2_client
|
||||
depends_on:
|
||||
- taskmgr
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_ipmi_proxy_v2_client
|
||||
journal:
|
||||
container_name: journal
|
||||
image: docker-registry.ispsystem.com/team/dci/journal:1.2.4
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
DATABASE_USER: root
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_journal
|
||||
license:
|
||||
container_name: license
|
||||
image: docker-registry.ispsystem.com/team/common/license/alma:1.0.0
|
||||
volumes:
|
||||
- /opt/ispsystem/license:/opt/ispsystem/license/tmp
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
LICENSE_TOKEN: ${TOKEN}
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- vault
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_license
|
||||
metric_collector:
|
||||
container_name: metric_collector
|
||||
image: docker-registry.ispsystem.com/team/common/metrica/alma:3.10.1
|
||||
environment:
|
||||
LOG_LEVEL: warn
|
||||
LOG_SETTINGS_JOURNALD_LEVEL: critical
|
||||
METRIC_RECEIVER_ADDR: metricreport.ispsystem.net:8000
|
||||
PROXY_SERVICE: input:1500
|
||||
networks:
|
||||
auth: null
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_metric_collector
|
||||
migrator:
|
||||
container_name: migrator
|
||||
image: docker-registry.ispsystem.com/team/dci/migrate/debian-12:0.6.0
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
INSTANCE_ID: "1"
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_migrator
|
||||
msgsender:
|
||||
container_name: msgsender
|
||||
image: docker-registry.ispsystem.com/team/common/msgsender/alma:4.1.1
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
INSTANCE_ID: "1"
|
||||
LANG: en_US.UTF-8
|
||||
LOG_LEVEL: warn
|
||||
LOG_SETTINGS_FILE_LEVEL: debug
|
||||
PRODUCT: dci
|
||||
TELEGRAM_SRV_HOST: telegram_srv:8080
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_msgsender
|
||||
mysql:
|
||||
container_name: mysql
|
||||
image: docker-registry.ispsystem.com/team/dci/mysql:0.0.2
|
||||
volumes:
|
||||
- /var/lib/mysql:/var/lib/mysql
|
||||
environment:
|
||||
MYSQL_DATABASE: auth
|
||||
MYSQL_PLATFORM_DATABASE: dci_1
|
||||
MYSQL_ROOT_PASSWORD: ${DATABASE_PASSWORD}
|
||||
networks:
|
||||
auth: null
|
||||
command: --max_allowed_packet=32M
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_mysql
|
||||
notice-center:
|
||||
container_name: notice_center
|
||||
image: docker-registry.ispsystem.com/team/common/notice-center/alma:1.1.0
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
CONSUL_PORT_8500_TCP_ADDR: consul
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
INSTANCE_ID: "1"
|
||||
KV_STORAGE_ADDR: consul
|
||||
LOG_LEVEL: warn
|
||||
LOG_SETTINGS_FILE_LEVEL: trace
|
||||
PRODUCT: dci
|
||||
PROXY_SERVICE: input:1500
|
||||
SERVICE_NAME: notice-center
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_notice_center
|
||||
notifier_v4:
|
||||
container_name: notifier
|
||||
image: docker-registry.ispsystem.com/ispsystem/experimental/notify/debian:0.3.5
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
LOG_LEVEL: warn
|
||||
LOG_SETTINGS_JOURNALD_LEVEL: critical
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_notifier_v4
|
||||
plugin:
|
||||
container_name: plugin
|
||||
image: docker-registry.ispsystem.com/team/market/plugin/alma:3.0.10
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/socket/:/opt/ispsystem/installer/socket/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
DATABASE_USER: root
|
||||
INSTANCE_ID: "1"
|
||||
LOG_SETTINGS_FILE_LEVEL: debug
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_plugin
|
||||
report:
|
||||
container_name: report
|
||||
image: docker-registry.ispsystem.com/team/dci/report/alma:1.3.0
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
INSTANCE_ID: "1"
|
||||
PRODUCT_NAME: DCI
|
||||
PROXY_SERVICE: input:1500
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_report
|
||||
search:
|
||||
container_name: search
|
||||
image: docker-registry.ispsystem.com/team/extra/search/debian:2.1.5
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
INSTANCE_ID: "1"
|
||||
PRODUCT_NAME: dci
|
||||
PROXY_SERVICE: input:1500
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_search
|
||||
swagger:
|
||||
container_name: swagger
|
||||
image: docker-registry.ispsystem.com/team/common/swagger/debian-12:1.5.0
|
||||
environment:
|
||||
DOC_EXPANSION: none
|
||||
DOMAIN: ${DOMAIN}
|
||||
PRODUCT: dci
|
||||
PROXY_SERVICE: input:1500
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- auth_back4
|
||||
- dci_back
|
||||
- report
|
||||
- ipmi_proxy_v2_client
|
||||
- eservice
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_swagger
|
||||
taskmgr:
|
||||
container_name: taskmgr
|
||||
image: docker-registry.ispsystem.com/ispsystem/experimental/taskmgr/debian:1.5.1
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- consul
|
||||
- ${DATABASE_TYPE}
|
||||
- notifier_v4
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_taskmgr
|
||||
telegram_srv:
|
||||
container_name: telegram_srv
|
||||
image: docker-registry.ispsystem.com/team/vm/telegram-srv/alma:0.1.9
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/telegram-srv/:/opt/ispsystem/telegram-srv/data/
|
||||
environment:
|
||||
PRODUCT: dci
|
||||
PROXY_SERVICE: input:1500
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- msgsender
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_telegram
|
||||
updater:
|
||||
container_name: updater
|
||||
image: docker-registry.ispsystem.com/team/common/updater/alma:3.0.4
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/socket/:/opt/ispsystem/installer/socket/
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
CONSUL_PORT_8500_TCP_ADDR: consul
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_USER: root
|
||||
INSTANCE_ID: "1"
|
||||
KV_STORAGE_ADDR: consul
|
||||
LOG_SETTINGS_FILE_LEVEL: debug
|
||||
PRODUCT_NAME: DCI
|
||||
PROXY_SERVICE: input:1500
|
||||
REPOSITORY_URL: http://download.ispsystem.com/6/dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_updater
|
||||
vault:
|
||||
container_name: vault
|
||||
image: docker-registry.ispsystem.com/team/common/vault/debian:2.3.0
|
||||
volumes:
|
||||
- /var/run/systemd/journal/:/var/run/systemd/journal/
|
||||
environment:
|
||||
DATABASE_DRIVER: ${DATABASE_TYPE}
|
||||
DATABASE_HOST: ${DATABASE_TYPE}
|
||||
DATABASE_NAME: ${DATABASE_NAME_AUTH}
|
||||
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
DATABASE_TYPE: ${DATABASE_TYPE}
|
||||
DATABASE_USER: root
|
||||
LOG_LEVEL: warn
|
||||
LOG_SETTINGS_JOURNALD_LEVEL: critical
|
||||
PRODUCT: dci
|
||||
VAULT_PASSWORD: ${DATABASE_PASSWORD}
|
||||
VAULT_TYPE: db
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- ${DATABASE_TYPE}
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_vault
|
||||
vector_master:
|
||||
container_name: vector_master
|
||||
image: docker-registry.ispsystem.com/team/dci/vector:0.1.3
|
||||
environment:
|
||||
CLICKHOUSE_DATABASE: dci
|
||||
CLICKHOUSE_PASSWORD: ${DATABASE_PASSWORD}
|
||||
CLICKHOUSE_USER: root
|
||||
INSTANCE_ID: "1"
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
depends_on:
|
||||
- clickhouse_server
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_vector_master
|
||||
victoria_metrics:
|
||||
container_name: victoria_metrics
|
||||
image: docker-registry.ispsystem.com/team/dci/victoria_metrics/debian:0.0.7
|
||||
environment:
|
||||
PRODUCT: dci
|
||||
networks:
|
||||
auth: null
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_victoria_metrics
|
||||
vmalert:
|
||||
container_name: vmalert
|
||||
image: docker-registry.ispsystem.com/team/dci/vmalert:0.0.1
|
||||
volumes:
|
||||
- /opt/ispsystem/dci/vmalert/alerts:/opt/ispsystem/vmalert/alerts
|
||||
networks:
|
||||
auth: null
|
||||
command: --datasource.url=http://victoria_metrics:8428/ --remoteRead.url=http://victoria_metrics:8428/
|
||||
--remoteWrite.url=http://victoria_metrics:8428/ --notifier.url=http://dci_alert_wrapper:3381/
|
||||
--notifier.headers=internal-auth:on --rule=/opt/ispsystem/vmalert/alerts/*.yml
|
||||
restart: always
|
||||
logging:
|
||||
driver: journald
|
||||
options:
|
||||
tag: dci_vmalert
|
||||
networks:
|
||||
auth: {}
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,259 @@
|
||||
2025-11-12 08:50:13,875 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-12 08:50:13,875 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-12 08:50:13,875 INFO Set uid to user 0 succeeded
|
||||
2025-11-12 08:50:13,910 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:13,910 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:13,910 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:14,923 INFO spawned: 'grafana_proxy' with pid 19
|
||||
2025-11-12 08:50:14,954 INFO spawned: 'grafana_server' with pid 20
|
||||
2025-11-12 08:50:15,967 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:15,968 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:26,638 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-17 12:01:26,661 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-17 12:01:26,661 INFO Set uid to user 0 succeeded
|
||||
2025-11-17 12:01:27,051 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:27,051 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:27,051 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:28,106 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-17 12:01:28,147 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-17 12:01:29,206 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,206 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,409 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-21 15:30:39,416 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-21 15:30:39,416 INFO Set uid to user 0 succeeded
|
||||
2025-11-21 15:30:39,770 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:39,771 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:39,783 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:40,788 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-21 15:30:40,870 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-21 15:30:41,879 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:41,879 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:58,507 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-22 15:19:58,509 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-22 15:19:58,509 INFO Set uid to user 0 succeeded
|
||||
2025-11-22 15:19:58,837 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:58,837 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:58,842 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:59,856 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-22 15:19:59,880 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-22 15:20:00,899 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:20:00,899 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:57,630 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:57,639 INFO waiting for grafana_proxy, grafana_server to die
|
||||
2025-11-22 15:27:57,786 INFO stopped: grafana_server (exit status 0)
|
||||
2025-11-22 15:27:58,807 WARN stopped: grafana_proxy (terminated by SIGTERM)
|
||||
2025-11-22 15:28:24,113 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-22 15:28:24,114 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-22 15:28:24,114 INFO Set uid to user 0 succeeded
|
||||
2025-11-22 15:28:24,143 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:24,143 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:24,143 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:25,159 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-22 15:28:25,228 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-22 15:28:26,256 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:26,256 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:46,410 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,425 INFO waiting for grafana_proxy, grafana_server to die
|
||||
2025-11-22 15:30:46,630 INFO stopped: grafana_server (exit status 0)
|
||||
2025-11-22 15:30:46,637 WARN stopped: grafana_proxy (terminated by SIGTERM)
|
||||
2025-11-22 15:31:20,629 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-22 15:31:20,633 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-22 15:31:20,633 INFO Set uid to user 0 succeeded
|
||||
2025-11-22 15:31:20,683 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:20,684 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:20,684 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:21,709 INFO spawned: 'grafana_proxy' with pid 19
|
||||
2025-11-22 15:31:21,760 INFO spawned: 'grafana_server' with pid 20
|
||||
2025-11-22 15:31:22,762 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,775 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:43,042 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:43,113 INFO waiting for grafana_proxy, grafana_server to die
|
||||
2025-11-22 15:37:43,384 INFO stopped: grafana_server (exit status 0)
|
||||
2025-11-22 15:37:43,419 WARN stopped: grafana_proxy (terminated by SIGTERM)
|
||||
2025-11-22 15:38:21,969 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-22 15:38:21,969 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-22 15:38:21,969 INFO Set uid to user 0 succeeded
|
||||
2025-11-22 15:38:21,986 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:21,986 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:21,986 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:23,018 INFO spawned: 'grafana_proxy' with pid 21
|
||||
2025-11-22 15:38:23,043 INFO spawned: 'grafana_server' with pid 22
|
||||
2025-11-22 15:38:24,057 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:24,057 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,514 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-25 15:48:30,535 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-25 15:48:30,535 INFO Set uid to user 0 succeeded
|
||||
2025-11-25 15:48:30,912 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:30,915 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:30,917 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:31,962 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-25 15:48:31,997 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-25 15:48:33,002 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:33,006 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,592 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-07 15:52:27,597 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-07 15:52:27,597 INFO Set uid to user 0 succeeded
|
||||
2025-12-07 15:52:27,944 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:27,944 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:27,945 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:28,991 INFO spawned: 'grafana_proxy' with pid 19
|
||||
2025-12-07 15:52:29,015 INFO spawned: 'grafana_server' with pid 20
|
||||
2025-12-07 15:52:30,043 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:30,043 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:30,957 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-08 11:39:30,963 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-08 11:39:30,963 INFO Set uid to user 0 succeeded
|
||||
2025-12-08 11:39:31,289 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:31,289 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:31,298 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:32,300 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-08 11:39:32,329 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-08 11:39:33,360 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:33,360 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:47,261 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-11 15:42:47,273 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-11 15:42:47,273 INFO Set uid to user 0 succeeded
|
||||
2025-12-11 15:42:47,628 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:47,637 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:47,643 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:48,650 INFO spawned: 'grafana_proxy' with pid 19
|
||||
2025-12-11 15:42:48,783 INFO spawned: 'grafana_server' with pid 23
|
||||
2025-12-11 15:42:49,787 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:49,787 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:32,213 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-14 06:18:32,214 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-14 06:18:32,214 INFO Set uid to user 0 succeeded
|
||||
2025-12-14 06:18:32,563 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:32,572 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:32,575 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:33,613 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-14 06:18:33,623 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-14 06:18:34,652 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:34,652 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:40,293 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-15 18:35:40,398 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-15 18:35:40,398 INFO Set uid to user 0 succeeded
|
||||
2025-12-15 18:35:40,782 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:40,783 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:40,783 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:41,809 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-15 18:35:41,886 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-15 18:35:42,905 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:42,905 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:54,443 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-18 15:22:54,452 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-18 15:22:54,452 INFO Set uid to user 0 succeeded
|
||||
2025-12-18 15:22:54,808 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:54,808 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:54,814 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:55,828 INFO spawned: 'grafana_proxy' with pid 19
|
||||
2025-12-18 15:22:55,891 INFO spawned: 'grafana_server' with pid 20
|
||||
2025-12-18 15:22:56,930 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:56,930 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,909 WARN exited: grafana_proxy (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:20,057 INFO spawned: 'grafana_proxy' with pid 51
|
||||
2025-12-18 20:53:20,058 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,058 INFO waiting for grafana_proxy, grafana_server to die
|
||||
2025-12-18 20:53:20,059 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,521 INFO stopped: grafana_server (exit status 0)
|
||||
2025-12-18 20:53:20,565 WARN stopped: grafana_proxy (terminated by SIGTERM)
|
||||
2026-01-25 19:02:31,228 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-01-25 19:02:31,229 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-01-25 19:02:31,229 INFO Set uid to user 0 succeeded
|
||||
2026-01-25 19:02:31,268 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:31,268 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:31,274 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:32,277 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-01-25 19:02:32,298 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-01-25 19:02:33,302 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:33,302 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,081 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-04 12:30:23,082 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-04 12:30:23,082 INFO Set uid to user 0 succeeded
|
||||
2026-02-04 12:30:23,416 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:23,416 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:23,416 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:24,438 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-02-04 12:30:24,470 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-02-04 12:30:25,472 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,473 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:42,240 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-04 14:57:42,242 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-04 14:57:42,242 INFO Set uid to user 0 succeeded
|
||||
2026-02-04 14:57:42,607 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:42,607 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:42,608 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:43,660 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-02-04 14:57:43,702 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-02-04 14:57:44,779 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:44,780 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:02,396 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-04 17:31:02,400 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-04 17:31:02,400 INFO Set uid to user 0 succeeded
|
||||
2026-02-04 17:31:02,748 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:31:02,748 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:31:02,749 INFO supervisord started with pid 1
|
||||
2026-02-04 17:31:03,797 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-02-04 17:31:03,846 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-02-04 17:31:04,883 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:04,883 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:30,157 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-07 14:26:30,158 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-07 14:26:30,159 INFO Set uid to user 0 succeeded
|
||||
2026-02-07 14:26:30,521 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:30,521 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:30,522 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:31,593 INFO spawned: 'grafana_proxy' with pid 22
|
||||
2026-02-07 14:26:31,655 INFO spawned: 'grafana_server' with pid 23
|
||||
2026-02-07 14:26:32,697 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:32,697 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:31,566 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-20 16:02:31,580 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-20 16:02:31,580 INFO Set uid to user 0 succeeded
|
||||
2026-02-20 16:02:31,926 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:31,930 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:31,930 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:32,936 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-02-20 16:02:32,976 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-02-20 16:02:33,978 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:33,994 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,619 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-03-04 12:10:34,626 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-03-04 12:10:34,626 INFO Set uid to user 0 succeeded
|
||||
2026-03-04 12:10:34,995 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:34,996 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:35,010 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:36,019 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-03-04 12:10:36,082 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-03-04 12:10:37,083 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:37,122 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,401 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-03-23 09:52:47,415 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-03-23 09:52:47,415 INFO Set uid to user 0 succeeded
|
||||
2026-03-23 09:52:47,772 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:47,772 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:47,772 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:48,782 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-03-23 09:52:48,834 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-03-23 09:52:49,863 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:49,863 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:22,047 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-03-25 17:35:22,062 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-03-25 17:35:22,062 INFO Set uid to user 0 succeeded
|
||||
2026-03-25 17:35:22,435 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:22,436 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:22,436 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:23,462 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-03-25 17:35:23,547 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-03-25 17:35:24,550 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:24,550 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:10,241 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-03-26 07:04:10,247 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-03-26 07:04:10,247 INFO Set uid to user 0 succeeded
|
||||
2026-03-26 07:04:10,619 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:10,627 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:10,629 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:11,644 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-03-26 07:04:11,720 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-03-26 07:04:12,750 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:12,757 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,256 @@
|
||||
2025-11-12 08:50:12,729 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-12 08:50:12,729 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-12 08:50:12,729 INFO Set uid to user 0 succeeded
|
||||
2025-11-12 08:50:12,758 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:12,758 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:12,758 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:13,762 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-12 08:50:13,808 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-12 08:50:14,823 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:14,823 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,276 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-17 12:01:28,283 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-17 12:01:28,286 INFO Set uid to user 0 succeeded
|
||||
2025-11-17 12:01:28,628 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:28,636 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:28,640 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:29,666 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-17 12:01:29,759 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-17 12:01:30,773 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:30,773 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,406 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-21 15:30:39,416 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-21 15:30:39,416 INFO Set uid to user 0 succeeded
|
||||
2025-11-21 15:30:39,778 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:39,778 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:39,778 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:40,819 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-21 15:30:40,855 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-21 15:30:41,942 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:41,942 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:58,557 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-22 15:19:58,557 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-22 15:19:58,557 INFO Set uid to user 0 succeeded
|
||||
2025-11-22 15:19:58,882 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:58,882 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:58,883 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:59,898 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-22 15:19:59,936 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-22 15:20:00,941 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:20:00,942 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:58,121 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:58,123 INFO waiting for grafana_proxy, grafana_server to die
|
||||
2025-11-22 15:27:58,257 INFO stopped: grafana_server (exit status 0)
|
||||
2025-11-22 15:27:58,275 WARN stopped: grafana_proxy (terminated by SIGTERM)
|
||||
2025-11-22 15:28:24,133 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-22 15:28:24,133 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-22 15:28:24,133 INFO Set uid to user 0 succeeded
|
||||
2025-11-22 15:28:24,155 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:24,157 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:24,157 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:25,182 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-22 15:28:25,257 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-22 15:28:26,266 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:26,266 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:46,555 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,564 INFO waiting for grafana_proxy, grafana_server to die
|
||||
2025-11-22 15:30:46,632 INFO stopped: grafana_server (exit status 0)
|
||||
2025-11-22 15:30:46,641 WARN stopped: grafana_proxy (terminated by SIGTERM)
|
||||
2025-11-22 15:31:20,497 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-22 15:31:20,497 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-22 15:31:20,497 INFO Set uid to user 0 succeeded
|
||||
2025-11-22 15:31:20,536 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:20,536 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:20,537 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:21,596 INFO spawned: 'grafana_proxy' with pid 19
|
||||
2025-11-22 15:31:21,598 INFO spawned: 'grafana_server' with pid 20
|
||||
2025-11-22 15:31:22,634 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,634 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:42,940 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:42,956 INFO waiting for grafana_proxy, grafana_server to die
|
||||
2025-11-22 15:37:43,042 INFO stopped: grafana_server (exit status 0)
|
||||
2025-11-22 15:37:43,053 WARN stopped: grafana_proxy (terminated by SIGTERM)
|
||||
2025-11-22 15:38:25,759 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-22 15:38:25,769 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-22 15:38:25,769 INFO Set uid to user 0 succeeded
|
||||
2025-11-22 15:38:25,819 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:25,819 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:25,820 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:26,836 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-11-22 15:38:26,950 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-11-22 15:38:27,961 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:27,961 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:33,594 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-11-25 15:48:33,621 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-11-25 15:48:33,621 INFO Set uid to user 0 succeeded
|
||||
2025-11-25 15:48:34,011 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:34,011 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:34,011 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:35,038 INFO spawned: 'grafana_proxy' with pid 19
|
||||
2025-11-25 15:48:35,122 INFO spawned: 'grafana_server' with pid 20
|
||||
2025-11-25 15:48:36,129 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:36,129 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,526 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-07 15:52:27,546 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-07 15:52:27,546 INFO Set uid to user 0 succeeded
|
||||
2025-12-07 15:52:27,907 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:27,917 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:27,927 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:28,940 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-07 15:52:29,003 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-07 15:52:30,005 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:30,005 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,321 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-08 11:39:43,332 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-08 11:39:43,333 INFO Set uid to user 0 succeeded
|
||||
2025-12-08 11:39:43,719 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:43,731 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:43,742 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:44,818 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-08 11:39:44,850 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-08 11:39:45,881 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:45,881 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:46,866 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-11 15:42:46,867 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-11 15:42:46,869 INFO Set uid to user 0 succeeded
|
||||
2025-12-11 15:42:47,246 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:47,255 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:47,257 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:48,269 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-11 15:42:48,332 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-11 15:42:49,334 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:49,334 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:30,008 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-14 06:18:30,016 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-14 06:18:30,016 INFO Set uid to user 0 succeeded
|
||||
2025-12-14 06:18:30,398 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:30,404 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:30,406 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:31,418 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-14 06:18:31,482 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-14 06:18:32,513 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:32,516 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:36,462 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-15 18:35:36,478 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-15 18:35:36,478 INFO Set uid to user 0 succeeded
|
||||
2025-12-15 18:35:36,832 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:36,832 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:36,832 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:37,853 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-15 18:35:37,925 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-15 18:35:38,980 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:38,980 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:04,520 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2025-12-18 15:23:04,522 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2025-12-18 15:23:04,522 INFO Set uid to user 0 succeeded
|
||||
2025-12-18 15:23:04,866 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:04,866 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:04,866 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:05,877 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2025-12-18 15:23:05,931 INFO spawned: 'grafana_server' with pid 21
|
||||
2025-12-18 15:23:06,963 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:06,963 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,930 WARN exited: grafana_proxy (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,971 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,015 INFO waiting for grafana_server to die
|
||||
2025-12-18 20:53:20,293 INFO stopped: grafana_server (exit status 0)
|
||||
2026-01-25 19:02:22,581 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-01-25 19:02:22,587 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-01-25 19:02:22,587 INFO Set uid to user 0 succeeded
|
||||
2026-01-25 19:02:22,652 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:22,652 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:22,653 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:23,694 INFO spawned: 'grafana_proxy' with pid 21
|
||||
2026-01-25 19:02:23,730 INFO spawned: 'grafana_server' with pid 22
|
||||
2026-01-25 19:02:24,745 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,745 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:24,413 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-04 12:30:24,415 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-04 12:30:24,415 INFO Set uid to user 0 succeeded
|
||||
2026-02-04 12:30:24,766 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:24,766 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:24,766 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:25,775 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-02-04 12:30:25,813 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-02-04 12:30:26,821 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:26,821 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:45,148 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-04 14:57:45,148 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-04 14:57:45,148 INFO Set uid to user 0 succeeded
|
||||
2026-02-04 14:57:45,496 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:45,496 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:45,514 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:46,522 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-02-04 14:57:46,649 INFO spawned: 'grafana_server' with pid 24
|
||||
2026-02-04 14:57:47,677 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:47,677 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:54,975 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-04 17:30:54,991 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-04 17:30:54,991 INFO Set uid to user 0 succeeded
|
||||
2026-02-04 17:30:55,381 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:55,381 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:55,381 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:56,436 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-02-04 17:30:56,478 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-02-04 17:30:57,550 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,550 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:30,960 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-07 14:26:30,966 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-07 14:26:30,966 INFO Set uid to user 0 succeeded
|
||||
2026-02-07 14:26:31,326 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:31,326 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:31,337 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:32,379 INFO spawned: 'grafana_proxy' with pid 19
|
||||
2026-02-07 14:26:32,427 INFO spawned: 'grafana_server' with pid 20
|
||||
2026-02-07 14:26:33,440 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:33,440 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:31,568 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-02-20 16:02:31,582 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-02-20 16:02:31,582 INFO Set uid to user 0 succeeded
|
||||
2026-02-20 16:02:31,932 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:31,932 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:31,933 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:32,951 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-02-20 16:02:32,960 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-02-20 16:02:33,992 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:33,994 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,324 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-03-04 12:10:34,345 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-03-04 12:10:34,346 INFO Set uid to user 0 succeeded
|
||||
2026-03-04 12:10:34,724 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:34,725 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:34,725 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:35,767 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-03-04 12:10:35,797 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-03-04 12:10:36,802 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:36,802 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,594 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-03-23 09:52:47,607 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-03-23 09:52:47,607 INFO Set uid to user 0 succeeded
|
||||
2026-03-23 09:52:47,957 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:47,957 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:47,957 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:48,970 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-03-23 09:52:49,027 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-03-23 09:52:50,069 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:50,069 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:14,935 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-03-25 17:35:14,938 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-03-25 17:35:14,938 INFO Set uid to user 0 succeeded
|
||||
2026-03-25 17:35:15,281 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:15,281 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:15,287 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:16,293 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-03-25 17:35:16,332 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-03-25 17:35:17,376 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:17,376 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:11,664 INFO Included extra file "/etc/supervisord.conf.d/grafana.conf" during parsing
|
||||
2026-03-26 07:04:11,669 INFO Included extra file "/etc/supervisord.conf.d/grafana_proxy.conf" during parsing
|
||||
2026-03-26 07:04:11,669 INFO Set uid to user 0 succeeded
|
||||
2026-03-26 07:04:12,057 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:12,057 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:12,088 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:13,132 INFO spawned: 'grafana_proxy' with pid 20
|
||||
2026-03-26 07:04:13,196 INFO spawned: 'grafana_server' with pid 21
|
||||
2026-03-26 07:04:14,202 INFO success: grafana_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:14,202 INFO success: grafana_server entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,483 @@
|
||||
2025-11-12 08:50:16,471 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.
|
||||
2025-11-12 08:50:16,471 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-11-12 08:50:16,471 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-11-12 08:50:16,471 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:16,471 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-12 08:50:16,492 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:16,495 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:16,496 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:17,507 INFO spawned: 'mesh' with pid 29
|
||||
2025-11-12 08:50:17,599 INFO spawned: 'ip_reader' with pid 30
|
||||
2025-11-12 08:50:17,650 INFO spawned: 'ip_writer' with pid 31
|
||||
2025-11-12 08:50:17,759 INFO spawned: 'ipmgr5_proxy' with pid 36
|
||||
2025-11-12 08:50:17,860 INFO spawned: 'taskmgr_worker' with pid 38
|
||||
2025-11-12 08:50:18,934 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:18,934 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:18,934 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:18,934 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:18,934 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:26,258 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.
|
||||
2025-11-17 12:01:26,263 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-11-17 12:01:26,263 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-11-17 12:01:26,263 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:26,263 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-17 12:01:26,615 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:26,615 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:26,616 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:27,630 INFO spawned: 'mesh' with pid 36
|
||||
2025-11-17 12:01:27,729 INFO spawned: 'ip_reader' with pid 37
|
||||
2025-11-17 12:01:27,765 INFO spawned: 'ip_writer' with pid 38
|
||||
2025-11-17 12:01:27,890 INFO spawned: 'ipmgr5_proxy' with pid 40
|
||||
2025-11-17 12:01:27,993 INFO spawned: 'taskmgr_worker' with pid 42
|
||||
2025-11-17 12:01:29,091 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,091 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,091 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,091 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,091 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:43,018 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.
|
||||
2025-11-21 15:30:43,031 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-11-21 15:30:43,031 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-11-21 15:30:43,031 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:43,032 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-21 15:30:43,363 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:43,368 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:43,368 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:44,389 INFO spawned: 'mesh' with pid 46
|
||||
2025-11-21 15:30:44,451 INFO spawned: 'ip_reader' with pid 47
|
||||
2025-11-21 15:30:44,531 INFO spawned: 'ip_writer' with pid 48
|
||||
2025-11-21 15:30:44,584 INFO spawned: 'ipmgr5_proxy' with pid 50
|
||||
2025-11-21 15:30:44,735 INFO spawned: 'taskmgr_worker' with pid 53
|
||||
2025-11-21 15:30:45,751 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:45,752 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:45,755 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:45,755 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:45,755 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,178 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.
|
||||
2025-11-22 15:19:49,279 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-11-22 15:19:49,279 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-11-22 15:19:49,279 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:49,279 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:19:49,708 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:49,723 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:49,723 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:50,736 INFO spawned: 'mesh' with pid 40
|
||||
2025-11-22 15:19:50,784 INFO spawned: 'ip_reader' with pid 41
|
||||
2025-11-22 15:19:50,844 INFO spawned: 'ip_writer' with pid 42
|
||||
2025-11-22 15:19:50,959 INFO spawned: 'ipmgr5_proxy' with pid 44
|
||||
2025-11-22 15:19:51,043 INFO spawned: 'taskmgr_worker' with pid 46
|
||||
2025-11-22 15:19:52,191 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,201 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,201 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,201 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,201 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:56,837 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:56,842 INFO waiting for mesh, ip_reader, ip_writer, ipmgr5_proxy, taskmgr_worker to die
|
||||
2025-11-22 15:27:56,896 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:27:56,983 INFO stopped: ipmgr5_proxy (exit status 0)
|
||||
2025-11-22 15:27:57,436 INFO stopped: ip_writer (exit status 0)
|
||||
2025-11-22 15:27:57,828 INFO stopped: ip_reader (exit status 0)
|
||||
2025-11-22 15:27:58,426 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:22,286 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.
|
||||
2025-11-22 15:28:22,286 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-11-22 15:28:22,286 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-11-22 15:28:22,286 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:22,287 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:28:22,293 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:22,293 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:22,293 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:23,320 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-22 15:28:23,351 INFO spawned: 'ip_reader' with pid 29
|
||||
2025-11-22 15:28:23,390 INFO spawned: 'ip_writer' with pid 31
|
||||
2025-11-22 15:28:23,435 INFO spawned: 'ipmgr5_proxy' with pid 34
|
||||
2025-11-22 15:28:23,514 INFO spawned: 'taskmgr_worker' with pid 35
|
||||
2025-11-22 15:28:24,546 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:24,546 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:24,554 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:24,554 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:24,554 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:45,824 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:45,835 INFO waiting for mesh, ip_reader, ip_writer, ipmgr5_proxy, taskmgr_worker to die
|
||||
2025-11-22 15:30:45,871 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:30:46,326 INFO stopped: ipmgr5_proxy (exit status 0)
|
||||
2025-11-22 15:30:46,510 INFO stopped: ip_writer (exit status 0)
|
||||
2025-11-22 15:30:46,904 INFO stopped: ip_reader (exit status 0)
|
||||
2025-11-22 15:30:47,159 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:20,863 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.
|
||||
2025-11-22 15:31:20,863 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-11-22 15:31:20,863 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-11-22 15:31:20,863 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:20,863 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:31:20,894 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:20,894 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:20,894 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:21,910 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-22 15:31:21,999 INFO spawned: 'ip_reader' with pid 29
|
||||
2025-11-22 15:31:22,046 INFO spawned: 'ip_writer' with pid 30
|
||||
2025-11-22 15:31:22,202 INFO spawned: 'ipmgr5_proxy' with pid 32
|
||||
2025-11-22 15:31:22,277 INFO spawned: 'taskmgr_worker' with pid 36
|
||||
2025-11-22 15:31:23,342 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:23,342 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:23,342 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:23,342 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:23,342 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:42,861 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:42,869 INFO waiting for mesh, ip_reader, ip_writer, ipmgr5_proxy, taskmgr_worker to die
|
||||
2025-11-22 15:37:43,034 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:37:43,878 INFO stopped: ipmgr5_proxy (exit status 0)
|
||||
2025-11-22 15:37:44,352 INFO stopped: ip_writer (exit status 0)
|
||||
2025-11-22 15:37:46,362 INFO waiting for mesh, ip_reader to die
|
||||
2025-11-22 15:37:49,366 INFO waiting for mesh, ip_reader to die
|
||||
2025-11-22 15:37:52,370 INFO waiting for mesh, ip_reader to die
|
||||
2025-11-22 15:37:54,372 WARN killing 'ip_reader' (29) with SIGKILL
|
||||
2025-11-22 15:37:54,374 WARN stopped: ip_reader (terminated by SIGKILL)
|
||||
2025-11-22 15:37:55,379 INFO waiting for mesh to die
|
||||
2025-11-22 15:37:58,384 INFO waiting for mesh to die
|
||||
2025-11-22 15:38:01,389 INFO waiting for mesh to die
|
||||
2025-11-22 15:38:20,964 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.
|
||||
2025-11-22 15:38:20,964 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-11-22 15:38:20,964 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-11-22 15:38:20,964 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:20,964 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:38:21,280 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:21,280 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:21,281 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:22,315 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-22 15:38:22,340 INFO spawned: 'ip_reader' with pid 29
|
||||
2025-11-22 15:38:22,379 INFO spawned: 'ip_writer' with pid 31
|
||||
2025-11-22 15:38:22,418 INFO spawned: 'ipmgr5_proxy' with pid 34
|
||||
2025-11-22 15:38:22,486 INFO spawned: 'taskmgr_worker' with pid 35
|
||||
2025-11-22 15:38:23,548 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:23,548 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:23,548 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:23,548 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:23,548 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:28,505 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.
|
||||
2025-11-25 15:48:28,510 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-11-25 15:48:28,510 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-11-25 15:48:28,510 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:28,510 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-25 15:48:28,863 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:28,863 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:28,863 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:29,889 INFO spawned: 'mesh' with pid 38
|
||||
2025-11-25 15:48:29,927 INFO spawned: 'ip_reader' with pid 40
|
||||
2025-11-25 15:48:29,999 INFO spawned: 'ip_writer' with pid 41
|
||||
2025-11-25 15:48:30,190 INFO spawned: 'ipmgr5_proxy' with pid 45
|
||||
2025-11-25 15:48:30,455 INFO spawned: 'taskmgr_worker' with pid 47
|
||||
2025-11-25 15:48:31,481 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,481 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,481 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,482 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,482 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,041 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.
|
||||
2025-12-07 15:52:25,048 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-12-07 15:52:25,049 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-12-07 15:52:25,049 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:25,049 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-07 15:52:25,397 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:25,397 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:25,397 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:26,405 INFO spawned: 'mesh' with pid 39
|
||||
2025-12-07 15:52:26,481 INFO spawned: 'ip_reader' with pid 40
|
||||
2025-12-07 15:52:26,537 INFO spawned: 'ip_writer' with pid 41
|
||||
2025-12-07 15:52:26,615 INFO spawned: 'ipmgr5_proxy' with pid 43
|
||||
2025-12-07 15:52:26,783 INFO spawned: 'taskmgr_worker' with pid 48
|
||||
2025-12-07 15:52:27,813 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,813 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,813 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,813 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,813 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:45,345 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.
|
||||
2025-12-08 11:39:45,351 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-12-08 11:39:45,351 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-12-08 11:39:45,351 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:45,351 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-08 11:39:45,694 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:45,694 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:45,694 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:46,706 INFO spawned: 'mesh' with pid 53
|
||||
2025-12-08 11:39:46,762 INFO spawned: 'ip_reader' with pid 54
|
||||
2025-12-08 11:39:46,915 INFO spawned: 'ip_writer' with pid 57
|
||||
2025-12-08 11:39:47,027 INFO spawned: 'ipmgr5_proxy' with pid 58
|
||||
2025-12-08 11:39:47,098 INFO spawned: 'taskmgr_worker' with pid 59
|
||||
2025-12-08 11:39:48,220 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:48,220 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:48,220 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:48,220 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:48,220 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:51,189 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.
|
||||
2025-12-11 15:42:51,203 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-12-11 15:42:51,203 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-12-11 15:42:51,203 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:51,203 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-11 15:42:51,541 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:51,542 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:51,542 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:52,563 INFO spawned: 'mesh' with pid 44
|
||||
2025-12-11 15:42:52,642 INFO spawned: 'ip_reader' with pid 45
|
||||
2025-12-11 15:42:52,695 INFO spawned: 'ip_writer' with pid 46
|
||||
2025-12-11 15:42:52,766 INFO spawned: 'ipmgr5_proxy' with pid 48
|
||||
2025-12-11 15:42:52,873 INFO spawned: 'taskmgr_worker' with pid 49
|
||||
2025-12-11 15:42:53,950 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,950 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,950 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,950 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,950 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:36,375 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.
|
||||
2025-12-14 06:18:36,378 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-12-14 06:18:36,378 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-12-14 06:18:36,378 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:36,378 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-14 06:18:36,722 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:36,722 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:36,723 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:37,730 INFO spawned: 'mesh' with pid 51
|
||||
2025-12-14 06:18:37,780 INFO spawned: 'ip_reader' with pid 52
|
||||
2025-12-14 06:18:37,836 INFO spawned: 'ip_writer' with pid 56
|
||||
2025-12-14 06:18:37,914 INFO spawned: 'ipmgr5_proxy' with pid 57
|
||||
2025-12-14 06:18:37,987 INFO spawned: 'taskmgr_worker' with pid 58
|
||||
2025-12-14 06:18:39,044 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:39,044 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:39,044 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:39,044 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:39,044 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:42,659 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.
|
||||
2025-12-15 18:35:42,663 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-12-15 18:35:42,663 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-12-15 18:35:42,663 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:42,663 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-15 18:35:43,009 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:43,009 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:43,010 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:44,023 INFO spawned: 'mesh' with pid 51
|
||||
2025-12-15 18:35:44,100 INFO spawned: 'ip_reader' with pid 52
|
||||
2025-12-15 18:35:44,186 INFO spawned: 'ip_writer' with pid 56
|
||||
2025-12-15 18:35:44,262 INFO spawned: 'ipmgr5_proxy' with pid 57
|
||||
2025-12-15 18:35:44,342 INFO spawned: 'taskmgr_worker' with pid 59
|
||||
2025-12-15 18:35:45,429 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:45,429 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:45,429 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:45,429 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:45,429 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:08,780 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.
|
||||
2025-12-18 15:23:08,781 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2025-12-18 15:23:08,781 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2025-12-18 15:23:08,781 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:08,781 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-18 15:23:09,103 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:09,103 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:09,103 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:10,112 INFO spawned: 'mesh' with pid 46
|
||||
2025-12-18 15:23:10,183 INFO spawned: 'ip_reader' with pid 47
|
||||
2025-12-18 15:23:10,224 INFO spawned: 'ip_writer' with pid 51
|
||||
2025-12-18 15:23:10,464 INFO spawned: 'ipmgr5_proxy' with pid 53
|
||||
2025-12-18 15:23:10,632 INFO spawned: 'taskmgr_worker' with pid 56
|
||||
2025-12-18 15:23:11,667 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,668 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,668 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,668 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,668 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,018 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,106 INFO spawned: 'mesh' with pid 63
|
||||
2025-12-18 20:53:19,153 WARN exited: ip_writer (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,169 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,255 INFO spawned: 'ip_writer' with pid 64
|
||||
2025-12-18 20:53:19,281 WARN exited: ip_reader (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,377 INFO spawned: 'ip_reader' with pid 66
|
||||
2025-12-18 20:53:19,435 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,458 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,462 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,555 INFO spawned: 'mesh' with pid 68
|
||||
2025-12-18 20:53:19,608 INFO exited: taskmgr_worker (exit status 0; expected)
|
||||
2025-12-18 20:53:19,608 WARN exited: ip_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,629 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,768 INFO spawned: 'ip_writer' with pid 70
|
||||
2025-12-18 20:53:20,006 INFO spawned: 'taskmgr_worker' with pid 71
|
||||
2025-12-18 20:53:20,007 WARN exited: ip_reader (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:20,007 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,094 INFO waiting for mesh, ip_writer, ipmgr5_proxy, taskmgr_worker to die
|
||||
2025-12-18 20:53:20,094 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,149 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:20,286 WARN exited: ip_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:20,342 WARN stopped: taskmgr_worker (terminated by SIGABRT (core dumped))
|
||||
2025-12-18 20:53:20,440 WARN stopped: ipmgr5_proxy (terminated by SIGTERM)
|
||||
2026-01-25 19:02:21,557 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.
|
||||
2026-01-25 19:02:21,575 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-01-25 19:02:21,576 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-01-25 19:02:21,576 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:21,576 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-01-25 19:02:21,641 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:21,642 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:21,642 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:22,659 INFO spawned: 'mesh' with pid 38
|
||||
2026-01-25 19:02:22,717 INFO spawned: 'ip_reader' with pid 39
|
||||
2026-01-25 19:02:22,817 INFO spawned: 'ip_writer' with pid 40
|
||||
2026-01-25 19:02:22,912 INFO spawned: 'ipmgr5_proxy' with pid 43
|
||||
2026-01-25 19:02:22,984 INFO spawned: 'taskmgr_worker' with pid 44
|
||||
2026-01-25 19:02:24,020 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,020 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,020 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,020 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,020 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:42,037 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.
|
||||
2026-02-04 12:30:42,038 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-02-04 12:30:42,038 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-02-04 12:30:42,038 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:42,038 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 12:30:42,376 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:42,379 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:42,383 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:43,395 INFO spawned: 'mesh' with pid 48
|
||||
2026-02-04 12:30:43,446 INFO spawned: 'ip_reader' with pid 49
|
||||
2026-02-04 12:30:43,506 INFO spawned: 'ip_writer' with pid 51
|
||||
2026-02-04 12:30:43,609 INFO spawned: 'ipmgr5_proxy' with pid 52
|
||||
2026-02-04 12:30:43,754 INFO spawned: 'taskmgr_worker' with pid 57
|
||||
2026-02-04 12:30:44,793 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,798 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,845 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,845 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,847 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,960 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.
|
||||
2026-02-04 14:57:35,975 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-02-04 14:57:35,975 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-02-04 14:57:35,975 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,975 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 14:57:36,303 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,309 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,309 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,319 INFO spawned: 'mesh' with pid 31
|
||||
2026-02-04 14:57:37,378 INFO spawned: 'ip_reader' with pid 32
|
||||
2026-02-04 14:57:37,445 INFO spawned: 'ip_writer' with pid 33
|
||||
2026-02-04 14:57:37,547 INFO spawned: 'ipmgr5_proxy' with pid 36
|
||||
2026-02-04 14:57:37,721 INFO spawned: 'taskmgr_worker' with pid 37
|
||||
2026-02-04 14:57:38,743 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,744 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,744 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,744 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,744 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:04,285 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.
|
||||
2026-02-04 17:31:04,286 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-02-04 17:31:04,286 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-02-04 17:31:04,286 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:31:04,286 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 17:31:04,618 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:31:04,618 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:31:04,618 INFO supervisord started with pid 1
|
||||
2026-02-04 17:31:05,682 INFO spawned: 'mesh' with pid 41
|
||||
2026-02-04 17:31:05,714 INFO spawned: 'ip_reader' with pid 42
|
||||
2026-02-04 17:31:05,782 INFO spawned: 'ip_writer' with pid 43
|
||||
2026-02-04 17:31:05,928 INFO spawned: 'ipmgr5_proxy' with pid 45
|
||||
2026-02-04 17:31:06,024 INFO spawned: 'taskmgr_worker' with pid 47
|
||||
2026-02-04 17:31:07,026 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:07,026 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:07,026 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:07,026 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:07,026 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:19,556 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.
|
||||
2026-02-07 14:26:19,562 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-02-07 14:26:19,562 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-02-07 14:26:19,562 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:19,562 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-07 14:26:19,893 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:19,893 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:19,927 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:20,929 INFO spawned: 'mesh' with pid 29
|
||||
2026-02-07 14:26:20,994 INFO spawned: 'ip_reader' with pid 30
|
||||
2026-02-07 14:26:21,056 INFO spawned: 'ip_writer' with pid 31
|
||||
2026-02-07 14:26:21,209 INFO spawned: 'ipmgr5_proxy' with pid 33
|
||||
2026-02-07 14:26:21,292 INFO spawned: 'taskmgr_worker' with pid 38
|
||||
2026-02-07 14:26:22,372 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,373 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,373 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,373 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,373 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,144 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.
|
||||
2026-02-20 16:02:21,154 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-02-20 16:02:21,154 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-02-20 16:02:21,154 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:21,155 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-20 16:02:21,528 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,529 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,529 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,538 INFO spawned: 'mesh' with pid 31
|
||||
2026-02-20 16:02:22,624 INFO spawned: 'ip_reader' with pid 32
|
||||
2026-02-20 16:02:22,814 INFO spawned: 'ip_writer' with pid 33
|
||||
2026-02-20 16:02:22,963 INFO spawned: 'ipmgr5_proxy' with pid 36
|
||||
2026-02-20 16:02:23,080 INFO spawned: 'taskmgr_worker' with pid 40
|
||||
2026-02-20 16:02:24,219 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,219 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,219 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,219 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,219 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:31,584 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.
|
||||
2026-03-04 12:10:31,587 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-03-04 12:10:31,587 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-03-04 12:10:31,587 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,587 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-04 12:10:31,918 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,918 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,924 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,974 INFO spawned: 'mesh' with pid 34
|
||||
2026-03-04 12:10:33,037 INFO spawned: 'ip_reader' with pid 35
|
||||
2026-03-04 12:10:33,114 INFO spawned: 'ip_writer' with pid 36
|
||||
2026-03-04 12:10:33,178 INFO spawned: 'ipmgr5_proxy' with pid 38
|
||||
2026-03-04 12:10:33,313 INFO spawned: 'taskmgr_worker' with pid 40
|
||||
2026-03-04 12:10:34,333 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,335 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,336 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,336 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:34,336 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:49,703 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.
|
||||
2026-03-23 09:52:49,706 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-03-23 09:52:49,706 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-03-23 09:52:49,706 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:49,706 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-23 09:52:50,042 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:50,042 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:50,042 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:51,071 INFO spawned: 'mesh' with pid 42
|
||||
2026-03-23 09:52:51,125 INFO spawned: 'ip_reader' with pid 43
|
||||
2026-03-23 09:52:51,172 INFO spawned: 'ip_writer' with pid 45
|
||||
2026-03-23 09:52:51,214 INFO spawned: 'ipmgr5_proxy' with pid 46
|
||||
2026-03-23 09:52:51,319 INFO spawned: 'taskmgr_worker' with pid 48
|
||||
2026-03-23 09:52:52,372 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:52,372 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:52,372 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:52,372 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:52,372 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:28,542 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.
|
||||
2026-03-25 17:35:28,550 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-03-25 17:35:28,550 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-03-25 17:35:28,550 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:28,550 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-25 17:35:28,884 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:28,884 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:28,888 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:29,898 INFO spawned: 'mesh' with pid 50
|
||||
2026-03-25 17:35:29,974 INFO spawned: 'ip_reader' with pid 51
|
||||
2026-03-25 17:35:30,066 INFO spawned: 'ip_writer' with pid 53
|
||||
2026-03-25 17:35:30,149 INFO spawned: 'ipmgr5_proxy' with pid 54
|
||||
2026-03-25 17:35:30,403 INFO spawned: 'taskmgr_worker' with pid 59
|
||||
2026-03-25 17:35:31,454 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:31,454 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:31,455 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:31,455 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:31,455 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,856 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.
|
||||
2026-03-26 07:04:03,879 INFO Included extra file "/opt/supervisor.d/ipmgr.conf" during parsing
|
||||
2026-03-26 07:04:03,879 INFO Included extra file "/opt/supervisor.d/ipmgr_proxy.conf" during parsing
|
||||
2026-03-26 07:04:03,879 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,879 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-26 07:04:04,209 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:04,209 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:04,213 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:05,233 INFO spawned: 'mesh' with pid 34
|
||||
2026-03-26 07:04:05,291 INFO spawned: 'ip_reader' with pid 35
|
||||
2026-03-26 07:04:05,375 INFO spawned: 'ip_writer' with pid 37
|
||||
2026-03-26 07:04:05,552 INFO spawned: 'ipmgr5_proxy' with pid 39
|
||||
2026-03-26 07:04:05,661 INFO spawned: 'taskmgr_worker' with pid 41
|
||||
2026-03-26 07:04:06,729 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,734 INFO success: ip_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,734 INFO success: ip_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,734 INFO success: ipmgr5_proxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,734 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,386 @@
|
||||
2025-11-12 08:50:23,592 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.
|
||||
2025-11-12 08:50:23,592 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-11-12 08:50:23,592 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:23,643 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:23,643 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:23,643 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:24,673 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-12 08:50:24,720 INFO spawned: 'license' with pid 18
|
||||
2025-11-12 08:50:25,774 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:25,774 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:30,248 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.
|
||||
2025-11-17 12:01:30,255 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-11-17 12:01:30,255 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:30,626 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:30,626 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:30,632 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:31,674 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-17 12:01:31,714 INFO spawned: 'license' with pid 18
|
||||
2025-11-17 12:01:32,716 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,716 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:35,853 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.
|
||||
2025-11-21 15:30:35,872 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-11-21 15:30:35,872 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:36,224 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:36,226 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:36,238 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:37,240 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-21 15:30:37,358 INFO spawned: 'license' with pid 27
|
||||
2025-11-21 15:30:38,372 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,372 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:46,647 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.
|
||||
2025-11-22 15:19:46,650 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-11-22 15:19:46,650 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:47,163 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,191 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,192 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,201 INFO spawned: 'mesh' with pid 23
|
||||
2025-11-22 15:19:48,255 INFO spawned: 'license' with pid 24
|
||||
2025-11-22 15:19:49,332 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,332 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:04,966 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:28:04,971 INFO waiting for mesh, license to die
|
||||
2025-11-22 15:28:05,004 INFO stopped: license (exit status 0)
|
||||
2025-11-22 15:28:05,012 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:33,519 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.
|
||||
2025-11-22 15:28:33,521 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-11-22 15:28:33,521 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:33,554 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:33,555 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:33,559 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:34,570 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:28:34,620 INFO spawned: 'license' with pid 18
|
||||
2025-11-22 15:28:35,649 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:35,650 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:52,880 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:52,881 INFO waiting for mesh, license to die
|
||||
2025-11-22 15:30:52,922 INFO stopped: license (exit status 0)
|
||||
2025-11-22 15:30:52,929 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:21,267 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.
|
||||
2025-11-22 15:31:21,267 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-11-22 15:31:21,267 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:21,308 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:21,308 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:21,317 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:22,331 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:31:22,395 INFO spawned: 'license' with pid 17
|
||||
2025-11-22 15:31:23,565 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:23,565 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:50,020 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:50,023 INFO waiting for mesh, license to die
|
||||
2025-11-22 15:37:50,049 INFO stopped: license (exit status 0)
|
||||
2025-11-22 15:37:50,061 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:34,665 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.
|
||||
2025-11-22 15:38:34,674 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-11-22 15:38:34,674 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:34,724 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:34,744 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:34,744 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:35,753 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:38:35,818 INFO spawned: 'license' with pid 18
|
||||
2025-11-22 15:38:36,865 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:36,865 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:25,217 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.
|
||||
2025-11-25 15:48:25,219 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-11-25 15:48:25,219 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:25,540 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:25,540 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:25,541 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:26,550 INFO spawned: 'mesh' with pid 20
|
||||
2025-11-25 15:48:26,586 INFO spawned: 'license' with pid 21
|
||||
2025-11-25 15:48:27,608 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,608 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:23,323 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.
|
||||
2025-12-07 15:52:23,324 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-12-07 15:52:23,324 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:23,680 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:23,680 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:23,681 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:24,701 INFO spawned: 'mesh' with pid 20
|
||||
2025-12-07 15:52:24,744 INFO spawned: 'license' with pid 21
|
||||
2025-12-07 15:52:25,758 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,758 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,811 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.
|
||||
2025-12-08 11:39:34,813 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-12-08 11:39:34,813 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:35,160 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:35,160 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:35,160 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:36,171 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-08 11:39:36,240 INFO spawned: 'license' with pid 17
|
||||
2025-12-08 11:39:37,252 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:37,252 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,597 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.
|
||||
2025-12-11 15:42:42,599 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-12-11 15:42:42,599 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:42,963 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:42,963 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:42,982 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:43,984 INFO spawned: 'mesh' with pid 23
|
||||
2025-12-11 15:42:44,058 INFO spawned: 'license' with pid 24
|
||||
2025-12-11 15:42:45,095 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,095 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:25,134 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.
|
||||
2025-12-14 06:18:25,149 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-12-14 06:18:25,149 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,538 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:25,538 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:25,547 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:26,553 INFO spawned: 'mesh' with pid 20
|
||||
2025-12-14 06:18:26,640 INFO spawned: 'license' with pid 21
|
||||
2025-12-14 06:18:27,652 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,659 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:32,593 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.
|
||||
2025-12-15 18:35:32,596 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-12-15 18:35:32,596 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:32,964 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:32,964 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:32,964 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:34,022 INFO spawned: 'mesh' with pid 29
|
||||
2025-12-15 18:35:34,056 INFO spawned: 'license' with pid 30
|
||||
2025-12-15 18:35:35,071 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:35,071 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:54,064 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.
|
||||
2025-12-18 15:22:54,066 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2025-12-18 15:22:54,066 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:54,403 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:54,403 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:54,407 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:55,416 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-18 15:22:55,466 INFO spawned: 'license' with pid 18
|
||||
2025-12-18 15:22:56,484 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:56,484 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,824 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:14,828 WARN exited: license (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:14,829 INFO reaped unknown pid 25 (terminated by SIGTERM)
|
||||
2025-12-18 20:53:14,844 INFO spawned: 'mesh' with pid 27
|
||||
2025-12-18 20:53:14,877 INFO spawned: 'license' with pid 28
|
||||
2025-12-18 20:53:14,976 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,984 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,984 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,984 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,006 INFO spawned: 'mesh' with pid 31
|
||||
2025-12-18 20:53:15,029 INFO spawned: 'license' with pid 32
|
||||
2025-12-18 20:53:15,077 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,079 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,079 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,178 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-18 20:53:15,183 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,183 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,212 INFO spawned: 'license' with pid 37
|
||||
2025-12-18 20:53:15,233 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,369 INFO spawned: 'mesh' with pid 39
|
||||
2025-12-18 20:53:15,369 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,383 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,383 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,450 INFO spawned: 'license' with pid 41
|
||||
2025-12-18 20:53:15,475 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,573 INFO spawned: 'mesh' with pid 43
|
||||
2025-12-18 20:53:15,584 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,585 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,600 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,638 INFO spawned: 'license' with pid 44
|
||||
2025-12-18 20:53:15,730 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,738 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,825 INFO spawned: 'mesh' with pid 47
|
||||
2025-12-18 20:53:15,840 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,840 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,914 INFO spawned: 'license' with pid 48
|
||||
2025-12-18 20:53:15,970 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,975 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,032 INFO spawned: 'mesh' with pid 51
|
||||
2025-12-18 20:53:16,067 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,068 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,117 INFO spawned: 'license' with pid 52
|
||||
2025-12-18 20:53:16,243 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,244 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,302 INFO spawned: 'mesh' with pid 55
|
||||
2025-12-18 20:53:16,304 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,324 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,354 INFO spawned: 'license' with pid 56
|
||||
2025-12-18 20:53:16,483 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,501 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,540 INFO spawned: 'mesh' with pid 59
|
||||
2025-12-18 20:53:16,541 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,568 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,593 INFO spawned: 'license' with pid 60
|
||||
2025-12-18 20:53:16,689 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,689 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,717 INFO spawned: 'mesh' with pid 63
|
||||
2025-12-18 20:53:16,738 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,744 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,763 INFO spawned: 'license' with pid 64
|
||||
2025-12-18 20:53:16,899 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,929 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,986 INFO spawned: 'mesh' with pid 67
|
||||
2025-12-18 20:53:16,987 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,987 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,047 INFO spawned: 'license' with pid 68
|
||||
2025-12-18 20:53:17,106 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,135 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,145 INFO spawned: 'mesh' with pid 71
|
||||
2025-12-18 20:53:17,160 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,227 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,264 INFO spawned: 'license' with pid 73
|
||||
2025-12-18 20:53:17,264 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,302 INFO spawned: 'mesh' with pid 74
|
||||
2025-12-18 20:53:17,320 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,403 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,404 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,443 INFO spawned: 'license' with pid 77
|
||||
2025-12-18 20:53:17,486 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,498 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,557 INFO spawned: 'mesh' with pid 79
|
||||
2025-12-18 20:53:17,582 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,583 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,617 INFO spawned: 'license' with pid 80
|
||||
2025-12-18 20:53:17,704 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,719 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,754 INFO spawned: 'mesh' with pid 83
|
||||
2025-12-18 20:53:17,780 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,789 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,865 INFO spawned: 'license' with pid 84
|
||||
2025-12-18 20:53:17,952 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,955 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,997 INFO spawned: 'mesh' with pid 87
|
||||
2025-12-18 20:53:18,087 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,087 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,123 INFO spawned: 'license' with pid 89
|
||||
2025-12-18 20:53:18,152 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,273 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,273 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,299 INFO spawned: 'mesh' with pid 91
|
||||
2025-12-18 20:53:18,348 INFO spawned: 'license' with pid 92
|
||||
2025-12-18 20:53:18,469 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,470 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,493 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,509 INFO spawned: 'mesh' with pid 95
|
||||
2025-12-18 20:53:18,546 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,548 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,576 INFO spawned: 'license' with pid 96
|
||||
2025-12-18 20:53:18,694 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,694 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,727 INFO spawned: 'mesh' with pid 99
|
||||
2025-12-18 20:53:18,728 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,728 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,793 INFO spawned: 'license' with pid 101
|
||||
2025-12-18 20:53:18,862 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,862 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,023 INFO spawned: 'mesh' with pid 103
|
||||
2025-12-18 20:53:19,046 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,047 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,120 INFO spawned: 'license' with pid 104
|
||||
2025-12-18 20:53:19,251 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,251 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,328 INFO spawned: 'mesh' with pid 107
|
||||
2025-12-18 20:53:19,360 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,362 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,399 INFO spawned: 'license' with pid 108
|
||||
2025-12-18 20:53:19,543 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,584 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,726 INFO spawned: 'mesh' with pid 111
|
||||
2025-12-18 20:53:19,780 WARN exited: license (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,780 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,803 INFO waiting for mesh to die
|
||||
2025-12-18 20:53:19,804 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,915 INFO stopped: mesh (exit status 0)
|
||||
2026-01-25 19:02:19,665 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.
|
||||
2026-01-25 19:02:19,696 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-01-25 19:02:19,697 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:19,771 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:19,771 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:19,772 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:20,784 INFO spawned: 'mesh' with pid 17
|
||||
2026-01-25 19:02:20,885 INFO spawned: 'license' with pid 18
|
||||
2026-01-25 19:02:21,888 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:21,888 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:28,261 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.
|
||||
2026-02-04 12:30:28,269 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-02-04 12:30:28,269 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:28,636 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:28,636 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:28,640 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:29,655 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 12:30:29,732 INFO spawned: 'license' with pid 17
|
||||
2026-02-04 12:30:30,757 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:30,757 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,344 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.
|
||||
2026-02-04 14:57:35,355 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-02-04 14:57:35,355 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,712 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:35,712 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:35,713 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:36,739 INFO spawned: 'mesh' with pid 20
|
||||
2026-02-04 14:57:36,790 INFO spawned: 'license' with pid 21
|
||||
2026-02-04 14:57:37,792 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,793 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,344 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.
|
||||
2026-02-04 17:30:53,361 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-02-04 17:30:53,361 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:53,721 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:53,722 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:53,722 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:54,737 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 17:30:54,795 INFO spawned: 'license' with pid 18
|
||||
2026-02-04 17:30:55,849 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:55,850 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:19,447 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.
|
||||
2026-02-07 14:26:19,455 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-02-07 14:26:19,464 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:19,833 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:19,834 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:19,834 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:20,849 INFO spawned: 'mesh' with pid 20
|
||||
2026-02-07 14:26:20,900 INFO spawned: 'license' with pid 21
|
||||
2026-02-07 14:26:21,903 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:21,903 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:18,912 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.
|
||||
2026-02-20 16:02:18,933 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-02-20 16:02:18,933 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:19,305 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:19,305 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:19,306 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:20,325 INFO spawned: 'mesh' with pid 23
|
||||
2026-02-20 16:02:20,453 INFO spawned: 'license' with pid 24
|
||||
2026-02-20 16:02:21,496 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,496 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:30,715 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.
|
||||
2026-03-04 12:10:30,733 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-03-04 12:10:30,733 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,098 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,099 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,099 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,114 INFO spawned: 'mesh' with pid 29
|
||||
2026-03-04 12:10:32,176 INFO spawned: 'license' with pid 30
|
||||
2026-03-04 12:10:33,196 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,196 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:44,466 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.
|
||||
2026-03-23 09:52:44,494 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-03-23 09:52:44,494 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,879 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:44,879 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:44,879 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:45,886 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-23 09:52:45,921 INFO spawned: 'license' with pid 23
|
||||
2026-03-23 09:52:46,946 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,946 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:20,254 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.
|
||||
2026-03-25 17:35:20,262 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-03-25 17:35:20,262 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:20,611 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:20,626 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:20,626 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:21,638 INFO spawned: 'mesh' with pid 17
|
||||
2026-03-25 17:35:21,708 INFO spawned: 'license' with pid 18
|
||||
2026-03-25 17:35:22,747 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:22,747 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,055 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.
|
||||
2026-03-26 07:04:03,078 INFO Included extra file "/opt/supervisor.d/license.conf" during parsing
|
||||
2026-03-26 07:04:03,078 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,430 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,456 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,456 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,461 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-26 07:04:04,514 INFO spawned: 'license' with pid 23
|
||||
2026-03-26 07:04:05,546 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,546 INFO success: license entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,539 @@
|
||||
2025-11-12 08:50:15,212 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.
|
||||
2025-11-12 08:50:15,212 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-11-12 08:50:15,212 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:15,212 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-12 08:50:15,251 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:15,251 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:15,252 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:16,286 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-12 08:50:16,314 INFO spawned: 'daemon' with pid 17
|
||||
2025-11-12 08:50:16,377 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-11-12 08:50:16,740 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:16,741 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:16,743 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:25,265 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.
|
||||
2025-11-17 12:01:25,281 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-11-17 12:01:25,281 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:25,281 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-17 12:01:25,648 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:25,648 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:25,648 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:26,681 INFO spawned: 'mesh' with pid 22
|
||||
2025-11-17 12:01:26,768 INFO spawned: 'daemon' with pid 23
|
||||
2025-11-17 12:01:26,860 INFO spawned: 'taskmgr_worker' with pid 24
|
||||
2025-11-17 12:01:27,879 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:27,879 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:27,879 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:36,632 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.
|
||||
2025-11-21 15:30:36,632 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-11-21 15:30:36,632 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:36,632 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-21 15:30:36,971 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:36,971 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:36,971 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:38,002 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-21 15:30:38,119 INFO spawned: 'daemon' with pid 29
|
||||
2025-11-21 15:30:38,189 INFO spawned: 'taskmgr_worker' with pid 30
|
||||
2025-11-21 15:30:39,153 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,163 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:39,163 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:47,017 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.
|
||||
2025-11-22 15:19:47,163 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-11-22 15:19:47,163 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:47,163 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:19:47,620 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,748 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,748 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,768 INFO spawned: 'mesh' with pid 25
|
||||
2025-11-22 15:19:48,880 INFO spawned: 'daemon' with pid 26
|
||||
2025-11-22 15:19:48,974 INFO spawned: 'taskmgr_worker' with pid 27
|
||||
2025-11-22 15:19:50,047 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:50,053 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:50,054 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:57,614 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:57,630 INFO waiting for mesh, daemon, taskmgr_worker to die
|
||||
2025-11-22 15:27:57,863 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:27:58,389 INFO stopped: daemon (exit status 0)
|
||||
2025-11-22 15:27:58,528 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:29,509 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.
|
||||
2025-11-22 15:28:29,520 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-11-22 15:28:29,520 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:29,520 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:28:29,551 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:29,551 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:29,551 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:30,571 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:28:30,619 INFO spawned: 'daemon' with pid 17
|
||||
2025-11-22 15:28:30,635 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-11-22 15:28:31,267 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:31,267 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:31,267 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:46,489 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,531 INFO waiting for mesh, daemon, taskmgr_worker to die
|
||||
2025-11-22 15:30:46,656 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:30:47,297 INFO stopped: daemon (exit status 0)
|
||||
2025-11-22 15:30:47,636 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:13,399 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.
|
||||
2025-11-22 15:31:13,399 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-11-22 15:31:13,399 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:13,399 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:31:13,409 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:13,409 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:13,409 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:14,415 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:31:14,459 INFO spawned: 'daemon' with pid 17
|
||||
2025-11-22 15:31:14,511 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-11-22 15:31:14,856 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:14,856 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:14,856 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:43,385 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:43,420 INFO waiting for mesh, daemon, taskmgr_worker to die
|
||||
2025-11-22 15:37:43,536 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:37:44,216 INFO stopped: daemon (exit status 0)
|
||||
2025-11-22 15:37:44,420 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:28,731 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.
|
||||
2025-11-22 15:38:28,731 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-11-22 15:38:28,731 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:28,731 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:38:28,780 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:28,780 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:28,780 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:29,793 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:38:29,848 INFO spawned: 'daemon' with pid 17
|
||||
2025-11-22 15:38:29,941 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-11-22 15:38:30,969 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:30,969 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:30,969 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,792 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.
|
||||
2025-11-25 15:48:27,815 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-11-25 15:48:27,815 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:27,816 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-25 15:48:28,159 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:28,159 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:28,159 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:29,188 INFO spawned: 'mesh' with pid 15
|
||||
2025-11-25 15:48:29,288 INFO spawned: 'daemon' with pid 16
|
||||
2025-11-25 15:48:29,343 INFO spawned: 'taskmgr_worker' with pid 17
|
||||
2025-11-25 15:48:30,470 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,470 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,470 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:24,017 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.
|
||||
2025-12-07 15:52:24,031 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-12-07 15:52:24,031 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:24,031 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-07 15:52:24,379 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:24,379 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:24,379 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:25,402 INFO spawned: 'mesh' with pid 25
|
||||
2025-12-07 15:52:25,449 INFO spawned: 'daemon' with pid 26
|
||||
2025-12-07 15:52:25,501 INFO spawned: 'taskmgr_worker' with pid 27
|
||||
2025-12-07 15:52:26,533 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,534 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,534 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:31,707 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.
|
||||
2025-12-08 11:39:31,712 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-12-08 11:39:31,713 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:31,713 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-08 11:39:32,033 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:32,033 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:32,033 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:33,052 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-08 11:39:33,085 INFO spawned: 'daemon' with pid 17
|
||||
2025-12-08 11:39:33,130 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-12-08 11:39:34,008 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,008 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,008 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:43,223 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.
|
||||
2025-12-11 15:42:43,224 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-12-11 15:42:43,224 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:43,224 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-11 15:42:43,553 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:43,553 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:43,553 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:44,601 INFO spawned: 'mesh' with pid 19
|
||||
2025-12-11 15:42:44,649 INFO spawned: 'daemon' with pid 20
|
||||
2025-12-11 15:42:44,692 INFO spawned: 'taskmgr_worker' with pid 21
|
||||
2025-12-11 15:42:45,782 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,782 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,782 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:25,488 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.
|
||||
2025-12-14 06:18:25,511 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-12-14 06:18:25,511 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,511 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-14 06:18:25,862 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:25,863 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:25,864 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:26,886 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-14 06:18:27,059 INFO spawned: 'daemon' with pid 20
|
||||
2025-12-14 06:18:27,068 INFO spawned: 'taskmgr_worker' with pid 21
|
||||
2025-12-14 06:18:28,085 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:28,085 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:28,085 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:33,863 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.
|
||||
2025-12-15 18:35:33,872 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-12-15 18:35:33,872 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:33,872 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-15 18:35:34,322 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:34,326 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:34,327 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:35,348 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-15 18:35:35,415 INFO spawned: 'daemon' with pid 17
|
||||
2025-12-15 18:35:35,468 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-12-15 18:35:36,496 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:36,497 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:36,497 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:59,989 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.
|
||||
2025-12-18 15:23:00,071 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2025-12-18 15:23:00,071 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:00,071 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-18 15:23:00,429 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:00,429 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:00,447 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:01,460 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-18 15:23:01,483 INFO spawned: 'daemon' with pid 17
|
||||
2025-12-18 15:23:01,526 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-12-18 15:23:02,183 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:02,183 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:02,183 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,255 INFO exited: taskmgr_worker (exit status 0; expected)
|
||||
2025-12-18 20:53:10,376 WARN exited: daemon (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:10,376 INFO reaped unknown pid 28 (exit status 0)
|
||||
2025-12-18 20:53:10,534 INFO spawned: 'daemon' with pid 31
|
||||
2025-12-18 20:53:10,619 INFO spawned: 'taskmgr_worker' with pid 32
|
||||
2025-12-18 20:53:10,741 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,741 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,754 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:10,842 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-18 20:53:10,843 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,067 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,274 INFO spawned: 'daemon' with pid 37
|
||||
2025-12-18 20:53:11,294 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,403 INFO spawned: 'mesh' with pid 38
|
||||
2025-12-18 20:53:11,418 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,418 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:11,531 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,554 INFO spawned: 'taskmgr_worker' with pid 41
|
||||
2025-12-18 20:53:11,558 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,594 INFO spawned: 'daemon' with pid 42
|
||||
2025-12-18 20:53:11,595 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,658 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,659 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,749 INFO spawned: 'mesh' with pid 45
|
||||
2025-12-18 20:53:11,763 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,764 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,787 INFO spawned: 'daemon' with pid 46
|
||||
2025-12-18 20:53:11,817 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,870 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:11,909 INFO spawned: 'taskmgr_worker' with pid 49
|
||||
2025-12-18 20:53:11,933 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,960 INFO spawned: 'daemon' with pid 50
|
||||
2025-12-18 20:53:11,979 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,062 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,062 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,200 INFO spawned: 'mesh' with pid 53
|
||||
2025-12-18 20:53:12,211 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:12,212 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,217 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,237 INFO spawned: 'daemon' with pid 54
|
||||
2025-12-18 20:53:12,266 INFO spawned: 'taskmgr_worker' with pid 55
|
||||
2025-12-18 20:53:12,365 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,365 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,467 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,468 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:12,471 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,480 INFO spawned: 'mesh' with pid 59
|
||||
2025-12-18 20:53:12,521 INFO spawned: 'daemon' with pid 60
|
||||
2025-12-18 20:53:12,551 INFO spawned: 'taskmgr_worker' with pid 62
|
||||
2025-12-18 20:53:12,672 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,673 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,673 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,711 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:12,711 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,724 INFO spawned: 'mesh' with pid 65
|
||||
2025-12-18 20:53:12,768 INFO spawned: 'taskmgr_worker' with pid 66
|
||||
2025-12-18 20:53:12,796 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,798 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,844 INFO spawned: 'daemon' with pid 67
|
||||
2025-12-18 20:53:12,847 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,944 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,945 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:12,954 INFO spawned: 'taskmgr_worker' with pid 71
|
||||
2025-12-18 20:53:13,060 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,060 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,082 INFO spawned: 'mesh' with pid 73
|
||||
2025-12-18 20:53:13,106 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,119 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,129 INFO spawned: 'daemon' with pid 74
|
||||
2025-12-18 20:53:13,148 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:13,155 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,172 INFO spawned: 'taskmgr_worker' with pid 76
|
||||
2025-12-18 20:53:13,321 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,328 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,336 INFO spawned: 'mesh' with pid 79
|
||||
2025-12-18 20:53:13,372 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,387 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,407 INFO spawned: 'daemon' with pid 80
|
||||
2025-12-18 20:53:13,421 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:13,610 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,695 INFO spawned: 'taskmgr_worker' with pid 83
|
||||
2025-12-18 20:53:13,696 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,696 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,739 INFO spawned: 'mesh' with pid 85
|
||||
2025-12-18 20:53:13,831 INFO spawned: 'daemon' with pid 86
|
||||
2025-12-18 20:53:13,851 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,950 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,958 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,959 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:14,080 INFO spawned: 'taskmgr_worker' with pid 89
|
||||
2025-12-18 20:53:14,491 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,531 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:14,574 INFO spawned: 'taskmgr_worker' with pid 91
|
||||
2025-12-18 20:53:14,622 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,622 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,717 INFO spawned: 'mesh' with pid 93
|
||||
2025-12-18 20:53:14,775 INFO spawned: 'daemon' with pid 94
|
||||
2025-12-18 20:53:14,776 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,913 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,913 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,160 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:15,161 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,235 INFO spawned: 'mesh' with pid 97
|
||||
2025-12-18 20:53:15,284 INFO spawned: 'taskmgr_worker' with pid 98
|
||||
2025-12-18 20:53:15,285 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,285 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,357 INFO spawned: 'daemon' with pid 100
|
||||
2025-12-18 20:53:15,357 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,358 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,390 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:15,409 INFO spawned: 'taskmgr_worker' with pid 103
|
||||
2025-12-18 20:53:15,535 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,539 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,570 INFO spawned: 'daemon' with pid 105
|
||||
2025-12-18 20:53:15,718 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,718 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,737 INFO spawned: 'mesh' with pid 107
|
||||
2025-12-18 20:53:15,752 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:15,754 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,765 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,776 INFO spawned: 'daemon' with pid 108
|
||||
2025-12-18 20:53:15,811 INFO spawned: 'taskmgr_worker' with pid 109
|
||||
2025-12-18 20:53:15,948 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,949 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,969 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:15,971 INFO spawned: 'taskmgr_worker' with pid 113
|
||||
2025-12-18 20:53:15,994 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,012 INFO spawned: 'daemon' with pid 114
|
||||
2025-12-18 20:53:16,013 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,099 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,162 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:16,179 INFO spawned: 'taskmgr_worker' with pid 117
|
||||
2025-12-18 20:53:16,185 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,223 INFO spawned: 'daemon' with pid 118
|
||||
2025-12-18 20:53:16,237 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,239 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,378 INFO spawned: 'mesh' with pid 121
|
||||
2025-12-18 20:53:16,379 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,379 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:16,411 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,412 INFO spawned: 'taskmgr_worker' with pid 122
|
||||
2025-12-18 20:53:16,469 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,511 INFO spawned: 'daemon' with pid 124
|
||||
2025-12-18 20:53:16,544 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,715 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,715 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:16,771 INFO spawned: 'taskmgr_worker' with pid 127
|
||||
2025-12-18 20:53:16,868 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,868 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,928 INFO spawned: 'mesh' with pid 129
|
||||
2025-12-18 20:53:16,974 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,977 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:16,978 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,025 INFO spawned: 'daemon' with pid 131
|
||||
2025-12-18 20:53:17,088 INFO spawned: 'taskmgr_worker' with pid 132
|
||||
2025-12-18 20:53:17,298 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,298 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,345 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,345 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:17,358 INFO spawned: 'mesh' with pid 135
|
||||
2025-12-18 20:53:17,424 INFO spawned: 'taskmgr_worker' with pid 136
|
||||
2025-12-18 20:53:17,469 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,470 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,517 INFO spawned: 'daemon' with pid 137
|
||||
2025-12-18 20:53:17,534 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,696 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,728 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:17,810 INFO spawned: 'taskmgr_worker' with pid 141
|
||||
2025-12-18 20:53:17,846 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,913 INFO spawned: 'mesh' with pid 142
|
||||
2025-12-18 20:53:17,942 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,943 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,943 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,000 INFO spawned: 'daemon' with pid 143
|
||||
2025-12-18 20:53:18,102 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,102 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:18,186 INFO spawned: 'taskmgr_worker' with pid 146
|
||||
2025-12-18 20:53:18,336 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,336 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,444 INFO spawned: 'mesh' with pid 149
|
||||
2025-12-18 20:53:18,474 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,480 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:18,491 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,522 INFO spawned: 'daemon' with pid 150
|
||||
2025-12-18 20:53:18,612 INFO spawned: 'taskmgr_worker' with pid 152
|
||||
2025-12-18 20:53:18,898 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,898 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,900 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:18,908 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,924 INFO spawned: 'mesh' with pid 155
|
||||
2025-12-18 20:53:18,995 INFO spawned: 'taskmgr_worker' with pid 156
|
||||
2025-12-18 20:53:19,098 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,098 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,098 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,150 INFO spawned: 'daemon' with pid 158
|
||||
2025-12-18 20:53:19,316 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,430 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,438 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,551 INFO spawned: 'mesh' with pid 161
|
||||
2025-12-18 20:53:19,635 INFO spawned: 'taskmgr_worker' with pid 163
|
||||
2025-12-18 20:53:19,636 WARN exited: daemon (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,714 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,801 INFO spawned: 'mesh' with pid 164
|
||||
2025-12-18 20:53:19,943 INFO spawned: 'daemon' with pid 166
|
||||
2025-12-18 20:53:19,988 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,994 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,022 INFO waiting for mesh, daemon, taskmgr_worker to die
|
||||
2025-12-18 20:53:20,028 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,029 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,029 WARN stopped: taskmgr_worker (terminated by SIGTERM)
|
||||
2025-12-18 20:53:20,495 WARN stopped: daemon (exit status 1)
|
||||
2025-12-18 20:53:20,526 WARN stopped: mesh (terminated by SIGTERM)
|
||||
2026-01-25 19:02:20,434 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.
|
||||
2026-01-25 19:02:20,437 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-01-25 19:02:20,437 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:20,437 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-01-25 19:02:20,480 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:20,480 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:20,480 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:21,506 INFO spawned: 'mesh' with pid 28
|
||||
2026-01-25 19:02:21,631 INFO spawned: 'daemon' with pid 29
|
||||
2026-01-25 19:02:21,770 INFO spawned: 'taskmgr_worker' with pid 30
|
||||
2026-01-25 19:02:22,815 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,815 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,815 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:21,622 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.
|
||||
2026-02-04 12:30:21,627 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-02-04 12:30:21,627 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:21,627 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 12:30:21,948 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:21,948 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:21,949 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:22,954 INFO spawned: 'mesh' with pid 15
|
||||
2026-02-04 12:30:22,978 INFO spawned: 'daemon' with pid 16
|
||||
2026-02-04 12:30:23,007 INFO spawned: 'taskmgr_worker' with pid 17
|
||||
2026-02-04 12:30:23,486 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,486 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,486 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:36,506 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.
|
||||
2026-02-04 14:57:36,510 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-02-04 14:57:36,510 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:36,510 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 14:57:36,855 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,856 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,856 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,879 INFO spawned: 'mesh' with pid 22
|
||||
2026-02-04 14:57:37,911 INFO spawned: 'daemon' with pid 23
|
||||
2026-02-04 14:57:37,991 INFO spawned: 'taskmgr_worker' with pid 24
|
||||
2026-02-04 14:57:39,028 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,028 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,028 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:54,643 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.
|
||||
2026-02-04 17:30:54,647 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-02-04 17:30:54,647 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:54,651 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 17:30:55,011 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:55,011 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:55,011 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:56,041 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 17:30:56,083 INFO spawned: 'daemon' with pid 17
|
||||
2026-02-04 17:30:56,159 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2026-02-04 17:30:57,204 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,204 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,204 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:20,510 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.
|
||||
2026-02-07 14:26:20,513 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-02-07 14:26:20,513 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:20,513 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-07 14:26:20,857 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,858 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,858 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,883 INFO spawned: 'mesh' with pid 19
|
||||
2026-02-07 14:26:21,981 INFO spawned: 'daemon' with pid 20
|
||||
2026-02-07 14:26:22,000 INFO spawned: 'taskmgr_worker' with pid 21
|
||||
2026-02-07 14:26:23,112 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,112 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,112 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,107 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.
|
||||
2026-02-20 16:02:21,135 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-02-20 16:02:21,135 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:21,135 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-20 16:02:21,503 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,503 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,504 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,533 INFO spawned: 'mesh' with pid 25
|
||||
2026-02-20 16:02:22,619 INFO spawned: 'daemon' with pid 26
|
||||
2026-02-20 16:02:22,755 INFO spawned: 'taskmgr_worker' with pid 27
|
||||
2026-02-20 16:02:23,814 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,814 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,814 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:31,020 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.
|
||||
2026-03-04 12:10:31,041 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-03-04 12:10:31,041 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,041 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-04 12:10:31,399 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,399 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,399 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,427 INFO spawned: 'mesh' with pid 25
|
||||
2026-03-04 12:10:32,499 INFO spawned: 'daemon' with pid 26
|
||||
2026-03-04 12:10:32,587 INFO spawned: 'taskmgr_worker' with pid 27
|
||||
2026-03-04 12:10:33,608 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,608 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,608 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:44,671 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.
|
||||
2026-03-23 09:52:44,677 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-03-23 09:52:44,677 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,677 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-23 09:52:45,026 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:45,033 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:45,040 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:46,056 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-23 09:52:46,094 INFO spawned: 'daemon' with pid 23
|
||||
2026-03-23 09:52:46,176 INFO spawned: 'taskmgr_worker' with pid 24
|
||||
2026-03-23 09:52:47,204 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,204 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,204 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:24,044 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.
|
||||
2026-03-25 17:35:24,049 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-03-25 17:35:24,049 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:24,049 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-25 17:35:24,406 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:24,423 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:24,423 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:25,433 INFO spawned: 'mesh' with pid 16
|
||||
2026-03-25 17:35:25,509 INFO spawned: 'daemon' with pid 17
|
||||
2026-03-25 17:35:25,710 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2026-03-25 17:35:26,723 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:26,723 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:26,723 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,572 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.
|
||||
2026-03-26 07:04:03,592 INFO Included extra file "/opt/supervisor.d/daemon.conf" during parsing
|
||||
2026-03-26 07:04:03,592 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,592 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-26 07:04:03,939 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,939 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,944 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,954 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-26 07:04:05,052 INFO spawned: 'daemon' with pid 23
|
||||
2026-03-26 07:04:05,121 INFO spawned: 'taskmgr_worker' with pid 24
|
||||
2026-03-26 07:04:06,170 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,170 INFO success: daemon entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,170 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,92 @@
|
||||
table ip nat {
|
||||
chain DOCKER {
|
||||
iifname "docker0" counter packets 0 bytes 0 return
|
||||
iifname "br-dde8e06c7d48" counter packets 0 bytes 0 return
|
||||
iifname != "br-dde8e06c7d48" tcp dport 80 counter packets 0 bytes 0 dnat to 172.18.0.27:80
|
||||
iifname != "br-dde8e06c7d48" tcp dport 443 counter packets 0 bytes 0 dnat to 172.18.0.27:443
|
||||
}
|
||||
|
||||
chain POSTROUTING {
|
||||
type nat hook postrouting priority srcnat; policy accept;
|
||||
ip saddr 172.17.0.0/16 oifname != "docker0" counter packets 0 bytes 0 masquerade
|
||||
ip saddr 172.18.0.0/16 oifname != "br-dde8e06c7d48" counter packets 129 bytes 7854 masquerade
|
||||
ip saddr 172.18.0.27 ip daddr 172.18.0.27 tcp dport 80 counter packets 0 bytes 0 masquerade
|
||||
ip saddr 172.18.0.27 ip daddr 172.18.0.27 tcp dport 443 counter packets 0 bytes 0 masquerade
|
||||
}
|
||||
|
||||
chain PREROUTING {
|
||||
type nat hook prerouting priority dstnat; policy accept;
|
||||
fib daddr type local counter packets 1 bytes 60 jump DOCKER
|
||||
}
|
||||
|
||||
chain OUTPUT {
|
||||
type nat hook output priority dstnat; policy accept;
|
||||
ip daddr != 127.0.0.0/8 fib daddr type local counter packets 0 bytes 0 jump DOCKER
|
||||
}
|
||||
}
|
||||
table ip filter {
|
||||
chain DOCKER {
|
||||
ip daddr 172.18.0.27 iifname != "br-dde8e06c7d48" oifname "br-dde8e06c7d48" tcp dport 80 counter packets 0 bytes 0 accept
|
||||
ip daddr 172.18.0.27 iifname != "br-dde8e06c7d48" oifname "br-dde8e06c7d48" tcp dport 443 counter packets 0 bytes 0 accept
|
||||
}
|
||||
|
||||
chain DOCKER-ISOLATION-STAGE-1 {
|
||||
iifname "docker0" oifname != "docker0" counter packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2
|
||||
iifname "br-dde8e06c7d48" oifname != "br-dde8e06c7d48" counter packets 813 bytes 61268 jump DOCKER-ISOLATION-STAGE-2
|
||||
counter packets 1190 bytes 449114 return
|
||||
}
|
||||
|
||||
chain DOCKER-ISOLATION-STAGE-2 {
|
||||
oifname "docker0" counter packets 0 bytes 0 drop
|
||||
oifname "br-dde8e06c7d48" counter packets 0 bytes 0 drop
|
||||
counter packets 813 bytes 61268 return
|
||||
}
|
||||
|
||||
chain FORWARD {
|
||||
type filter hook forward priority filter; policy drop;
|
||||
counter packets 1190 bytes 449114 jump DOCKER-USER
|
||||
counter packets 1190 bytes 449114 jump DOCKER-ISOLATION-STAGE-1
|
||||
oifname "docker0" ct state related,established counter packets 0 bytes 0 accept
|
||||
oifname "docker0" counter packets 0 bytes 0 jump DOCKER
|
||||
iifname "docker0" oifname != "docker0" counter packets 0 bytes 0 accept
|
||||
iifname "docker0" oifname "docker0" counter packets 0 bytes 0 accept
|
||||
oifname "br-dde8e06c7d48" ct state related,established counter packets 377 bytes 387846 accept
|
||||
oifname "br-dde8e06c7d48" counter packets 0 bytes 0 jump DOCKER
|
||||
iifname "br-dde8e06c7d48" oifname != "br-dde8e06c7d48" counter packets 813 bytes 61268 accept
|
||||
iifname "br-dde8e06c7d48" oifname "br-dde8e06c7d48" counter packets 0 bytes 0 accept
|
||||
}
|
||||
|
||||
chain DOCKER-USER {
|
||||
counter packets 1190 bytes 449114 return
|
||||
}
|
||||
}
|
||||
table ip6 nat {
|
||||
chain DOCKER {
|
||||
}
|
||||
}
|
||||
table ip6 filter {
|
||||
chain DOCKER {
|
||||
}
|
||||
|
||||
chain DOCKER-ISOLATION-STAGE-1 {
|
||||
iifname "docker0" oifname != "docker0" counter packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2
|
||||
iifname "br-dde8e06c7d48" oifname != "br-dde8e06c7d48" counter packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2
|
||||
counter packets 0 bytes 0 return
|
||||
}
|
||||
|
||||
chain DOCKER-ISOLATION-STAGE-2 {
|
||||
oifname "docker0" counter packets 0 bytes 0 drop
|
||||
oifname "br-dde8e06c7d48" counter packets 0 bytes 0 drop
|
||||
counter packets 0 bytes 0 return
|
||||
}
|
||||
|
||||
chain FORWARD {
|
||||
type filter hook forward priority filter; policy drop;
|
||||
counter packets 0 bytes 0 jump DOCKER-USER
|
||||
}
|
||||
|
||||
chain DOCKER-USER {
|
||||
counter packets 0 bytes 0 return
|
||||
}
|
||||
}
|
||||
|
||||
@@ -0,0 +1,637 @@
|
||||
2025-11-12 08:50:18,424 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.
|
||||
2025-11-12 08:50:18,424 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:18,424 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-11-12 08:50:18,424 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-11-12 08:50:18,477 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:18,477 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:18,477 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:19,496 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-12 08:50:19,518 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2025-11-12 08:50:19,550 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2025-11-12 08:50:19,604 INFO spawned: 'sender' with pid 20
|
||||
2025-11-12 08:50:20,637 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:20,637 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:20,637 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:20,637 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,724 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.
|
||||
2025-11-17 12:01:29,737 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:29,737 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-11-17 12:01:29,737 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-11-17 12:01:30,086 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:30,086 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:30,114 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:31,130 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-17 12:01:31,193 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2025-11-17 12:01:31,295 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2025-11-17 12:01:31,391 INFO spawned: 'sender' with pid 20
|
||||
2025-11-17 12:01:32,438 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,446 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,446 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,446 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:35,391 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.
|
||||
2025-11-21 15:30:35,400 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:35,400 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-11-21 15:30:35,400 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-11-21 15:30:35,764 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:35,764 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:35,764 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:36,775 INFO spawned: 'mesh' with pid 23
|
||||
2025-11-21 15:30:36,813 INFO spawned: 'notice_center_reader' with pid 24
|
||||
2025-11-21 15:30:36,860 INFO spawned: 'notice_center_writer' with pid 25
|
||||
2025-11-21 15:30:36,898 INFO spawned: 'sender' with pid 26
|
||||
2025-11-21 15:30:37,912 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,912 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,912 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,912 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:46,821 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.
|
||||
2025-11-22 15:19:46,825 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:46,825 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-11-22 15:19:46,825 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-11-22 15:19:47,166 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,199 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,199 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,226 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-22 15:19:48,338 INFO spawned: 'notice_center_reader' with pid 27
|
||||
2025-11-22 15:19:48,444 INFO spawned: 'notice_center_writer' with pid 28
|
||||
2025-11-22 15:19:48,594 INFO spawned: 'sender' with pid 29
|
||||
2025-11-22 15:19:49,618 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,688 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,704 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,704 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:01,342 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:28:01,349 INFO waiting for mesh, notice_center_reader, notice_center_writer, sender to die
|
||||
2025-11-22 15:28:01,357 INFO stopped: sender (exit status 0)
|
||||
2025-11-22 15:28:01,410 INFO stopped: notice_center_writer (exit status 0)
|
||||
2025-11-22 15:28:01,437 INFO stopped: notice_center_reader (exit status 0)
|
||||
2025-11-22 15:28:01,471 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:29,449 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.
|
||||
2025-11-22 15:28:29,449 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:29,449 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-11-22 15:28:29,449 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-11-22 15:28:29,488 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:29,488 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:29,488 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:30,503 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:28:30,545 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2025-11-22 15:28:30,653 INFO spawned: 'notice_center_writer' with pid 20
|
||||
2025-11-22 15:28:30,707 INFO spawned: 'sender' with pid 21
|
||||
2025-11-22 15:28:31,757 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:31,757 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:31,757 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:31,757 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:51,992 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:51,996 INFO waiting for mesh, notice_center_reader, notice_center_writer, sender to die
|
||||
2025-11-22 15:30:52,000 INFO stopped: sender (exit status 0)
|
||||
2025-11-22 15:30:52,019 INFO stopped: notice_center_writer (exit status 0)
|
||||
2025-11-22 15:30:52,029 INFO stopped: notice_center_reader (exit status 0)
|
||||
2025-11-22 15:30:52,045 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:14,203 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.
|
||||
2025-11-22 15:31:14,206 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:14,206 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-11-22 15:31:14,206 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-11-22 15:31:14,232 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:14,232 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:14,232 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:15,239 INFO spawned: 'mesh' with pid 18
|
||||
2025-11-22 15:31:15,283 INFO spawned: 'notice_center_reader' with pid 19
|
||||
2025-11-22 15:31:15,330 INFO spawned: 'notice_center_writer' with pid 23
|
||||
2025-11-22 15:31:15,472 INFO spawned: 'sender' with pid 24
|
||||
2025-11-22 15:31:16,475 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,475 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,475 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,475 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:47,969 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:47,972 INFO waiting for mesh, notice_center_reader, notice_center_writer, sender to die
|
||||
2025-11-22 15:37:47,974 INFO stopped: sender (exit status 0)
|
||||
2025-11-22 15:37:47,998 INFO stopped: notice_center_writer (exit status 0)
|
||||
2025-11-22 15:37:48,013 INFO stopped: notice_center_reader (exit status 0)
|
||||
2025-11-22 15:37:48,031 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:27,627 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.
|
||||
2025-11-22 15:38:27,627 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:27,627 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-11-22 15:38:27,627 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-11-22 15:38:27,689 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:27,689 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:27,689 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:28,713 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:38:28,770 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2025-11-22 15:38:28,815 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2025-11-22 15:38:28,864 INFO spawned: 'sender' with pid 21
|
||||
2025-11-22 15:38:29,923 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:29,923 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:29,923 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:29,923 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:32,145 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.
|
||||
2025-11-25 15:48:32,148 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:32,149 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-11-25 15:48:32,150 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-11-25 15:48:32,506 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:32,506 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:32,506 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:33,529 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-25 15:48:33,680 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2025-11-25 15:48:33,742 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2025-11-25 15:48:33,901 INFO spawned: 'sender' with pid 20
|
||||
2025-11-25 15:48:34,903 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:34,903 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:34,903 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:34,903 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:22,312 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.
|
||||
2025-12-07 15:52:22,322 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:22,322 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-12-07 15:52:22,322 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-12-07 15:52:22,686 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:22,709 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:22,710 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:23,728 INFO spawned: 'mesh' with pid 23
|
||||
2025-12-07 15:52:23,865 INFO spawned: 'notice_center_reader' with pid 24
|
||||
2025-12-07 15:52:23,912 INFO spawned: 'notice_center_writer' with pid 25
|
||||
2025-12-07 15:52:24,025 INFO spawned: 'sender' with pid 26
|
||||
2025-12-07 15:52:25,095 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,095 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,095 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,095 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:40,291 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.
|
||||
2025-12-08 11:39:40,309 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:40,309 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-12-08 11:39:40,309 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-12-08 11:39:40,671 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:40,671 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:40,671 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:41,692 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-08 11:39:41,756 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2025-12-08 11:39:41,822 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2025-12-08 11:39:41,876 INFO spawned: 'sender' with pid 20
|
||||
2025-12-08 11:39:42,906 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:42,906 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:42,906 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:42,907 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,339 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.
|
||||
2025-12-11 15:42:42,352 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:42,352 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-12-11 15:42:42,352 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-12-11 15:42:42,699 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:42,714 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:42,714 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:43,731 INFO spawned: 'mesh' with pid 24
|
||||
2025-12-11 15:42:43,750 INFO spawned: 'notice_center_reader' with pid 25
|
||||
2025-12-11 15:42:43,766 INFO spawned: 'notice_center_writer' with pid 26
|
||||
2025-12-11 15:42:43,793 INFO spawned: 'sender' with pid 27
|
||||
2025-12-11 15:42:44,612 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,612 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,612 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,612 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:24,804 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.
|
||||
2025-12-14 06:18:24,810 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:24,810 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-12-14 06:18:24,810 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-12-14 06:18:25,154 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:25,155 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:25,155 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:26,190 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-14 06:18:26,244 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2025-12-14 06:18:26,286 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2025-12-14 06:18:26,333 INFO spawned: 'sender' with pid 20
|
||||
2025-12-14 06:18:27,171 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,171 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,171 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,172 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:31,753 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.
|
||||
2025-12-15 18:35:31,774 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:31,774 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-12-15 18:35:31,775 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-12-15 18:35:32,144 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:32,147 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:32,147 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:33,175 INFO spawned: 'mesh' with pid 23
|
||||
2025-12-15 18:35:33,354 INFO spawned: 'notice_center_reader' with pid 24
|
||||
2025-12-15 18:35:33,510 INFO spawned: 'notice_center_writer' with pid 25
|
||||
2025-12-15 18:35:33,735 INFO spawned: 'sender' with pid 26
|
||||
2025-12-15 18:35:34,866 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,867 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,867 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,867 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:50,411 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.
|
||||
2025-12-18 15:22:50,419 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:50,419 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2025-12-18 15:22:50,419 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2025-12-18 15:22:50,737 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:50,737 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:50,737 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:51,750 INFO spawned: 'mesh' with pid 20
|
||||
2025-12-18 15:22:51,781 INFO spawned: 'notice_center_reader' with pid 21
|
||||
2025-12-18 15:22:51,811 INFO spawned: 'notice_center_writer' with pid 22
|
||||
2025-12-18 15:22:51,871 INFO spawned: 'sender' with pid 23
|
||||
2025-12-18 15:22:52,888 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:52,888 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:52,888 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:52,888 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,449 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:10,660 INFO spawned: 'mesh' with pid 282
|
||||
2025-12-18 20:53:10,666 WARN exited: notice_center_reader (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:10,667 INFO reaped unknown pid 275 (terminated by SIGTERM)
|
||||
2025-12-18 20:53:10,764 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,768 INFO spawned: 'notice_center_reader' with pid 284
|
||||
2025-12-18 20:53:10,782 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:10,787 WARN exited: notice_center_writer (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:10,834 INFO spawned: 'mesh' with pid 285
|
||||
2025-12-18 20:53:10,855 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,964 INFO spawned: 'notice_center_writer' with pid 286
|
||||
2025-12-18 20:53:11,198 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,198 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,198 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,206 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,233 INFO spawned: 'mesh' with pid 290
|
||||
2025-12-18 20:53:11,325 INFO spawned: 'notice_center_reader' with pid 291
|
||||
2025-12-18 20:53:11,372 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,373 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,373 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,408 INFO spawned: 'notice_center_writer' with pid 293
|
||||
2025-12-18 20:53:11,460 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,460 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,507 INFO spawned: 'mesh' with pid 296
|
||||
2025-12-18 20:53:11,534 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,535 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,572 INFO spawned: 'notice_center_reader' with pid 297
|
||||
2025-12-18 20:53:11,597 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,597 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,642 INFO spawned: 'notice_center_writer' with pid 299
|
||||
2025-12-18 20:53:11,676 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,676 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,746 INFO spawned: 'mesh' with pid 301
|
||||
2025-12-18 20:53:11,747 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,756 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,778 INFO spawned: 'notice_center_reader' with pid 303
|
||||
2025-12-18 20:53:11,824 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,837 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,883 INFO spawned: 'notice_center_writer' with pid 304
|
||||
2025-12-18 20:53:11,947 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,964 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,987 INFO spawned: 'mesh' with pid 308
|
||||
2025-12-18 20:53:12,008 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,009 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,040 INFO spawned: 'notice_center_reader' with pid 309
|
||||
2025-12-18 20:53:12,069 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,069 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,109 INFO spawned: 'notice_center_writer' with pid 311
|
||||
2025-12-18 20:53:12,147 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,147 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,185 INFO spawned: 'mesh' with pid 313
|
||||
2025-12-18 20:53:12,204 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,213 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,248 INFO spawned: 'notice_center_reader' with pid 315
|
||||
2025-12-18 20:53:12,282 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,293 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,343 INFO spawned: 'notice_center_writer' with pid 317
|
||||
2025-12-18 20:53:12,386 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,388 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,433 INFO spawned: 'mesh' with pid 319
|
||||
2025-12-18 20:53:12,461 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,473 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,500 INFO spawned: 'notice_center_reader' with pid 321
|
||||
2025-12-18 20:53:12,520 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,537 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,565 INFO spawned: 'notice_center_writer' with pid 323
|
||||
2025-12-18 20:53:12,580 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,618 INFO spawned: 'mesh' with pid 325
|
||||
2025-12-18 20:53:12,631 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,651 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,651 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,694 INFO spawned: 'notice_center_reader' with pid 326
|
||||
2025-12-18 20:53:12,730 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,731 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,763 INFO spawned: 'notice_center_writer' with pid 330
|
||||
2025-12-18 20:53:12,795 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,797 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,832 INFO spawned: 'mesh' with pid 331
|
||||
2025-12-18 20:53:12,837 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,852 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,910 INFO spawned: 'notice_center_reader' with pid 334
|
||||
2025-12-18 20:53:12,911 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,921 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,951 INFO spawned: 'mesh' with pid 335
|
||||
2025-12-18 20:53:12,968 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,024 INFO spawned: 'notice_center_writer' with pid 337
|
||||
2025-12-18 20:53:13,048 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,049 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,055 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,086 INFO spawned: 'notice_center_reader' with pid 339
|
||||
2025-12-18 20:53:13,131 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,138 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,164 INFO spawned: 'mesh' with pid 342
|
||||
2025-12-18 20:53:13,183 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,184 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,210 INFO spawned: 'notice_center_writer' with pid 343
|
||||
2025-12-18 20:53:13,252 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,313 INFO spawned: 'notice_center_reader' with pid 345
|
||||
2025-12-18 20:53:13,340 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,343 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,357 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,394 INFO spawned: 'mesh' with pid 347
|
||||
2025-12-18 20:53:13,416 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,423 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,464 INFO spawned: 'notice_center_writer' with pid 349
|
||||
2025-12-18 20:53:13,479 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,581 INFO spawned: 'notice_center_reader' with pid 351
|
||||
2025-12-18 20:53:13,622 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,627 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,667 INFO spawned: 'mesh' with pid 353
|
||||
2025-12-18 20:53:13,703 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,723 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,723 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,746 INFO spawned: 'notice_center_writer' with pid 354
|
||||
2025-12-18 20:53:14,015 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,015 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,111 INFO spawned: 'notice_center_reader' with pid 357
|
||||
2025-12-18 20:53:14,162 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,191 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,244 INFO spawned: 'mesh' with pid 359
|
||||
2025-12-18 20:53:14,320 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,423 INFO spawned: 'notice_center_writer' with pid 360
|
||||
2025-12-18 20:53:14,454 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,454 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,455 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,500 INFO spawned: 'notice_center_writer' with pid 362
|
||||
2025-12-18 20:53:14,607 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,608 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,702 INFO spawned: 'notice_center_reader' with pid 365
|
||||
2025-12-18 20:53:14,703 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,831 INFO spawned: 'mesh' with pid 367
|
||||
2025-12-18 20:53:14,831 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,850 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,851 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,887 INFO spawned: 'notice_center_writer' with pid 368
|
||||
2025-12-18 20:53:15,089 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,132 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,132 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,132 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,143 INFO spawned: 'mesh' with pid 372
|
||||
2025-12-18 20:53:15,223 INFO spawned: 'notice_center_reader' with pid 373
|
||||
2025-12-18 20:53:15,287 INFO spawned: 'notice_center_writer' with pid 374
|
||||
2025-12-18 20:53:15,410 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,410 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,410 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,410 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,466 INFO spawned: 'mesh' with pid 378
|
||||
2025-12-18 20:53:15,487 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,518 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,550 INFO spawned: 'notice_center_reader' with pid 379
|
||||
2025-12-18 20:53:15,580 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,582 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,635 INFO spawned: 'notice_center_writer' with pid 381
|
||||
2025-12-18 20:53:15,728 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,736 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,786 INFO spawned: 'mesh' with pid 383
|
||||
2025-12-18 20:53:15,827 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,842 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,905 INFO spawned: 'notice_center_reader' with pid 385
|
||||
2025-12-18 20:53:15,947 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,953 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,034 INFO spawned: 'notice_center_writer' with pid 387
|
||||
2025-12-18 20:53:16,075 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,075 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,204 INFO spawned: 'mesh' with pid 389
|
||||
2025-12-18 20:53:16,219 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,227 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,278 INFO spawned: 'notice_center_reader' with pid 391
|
||||
2025-12-18 20:53:16,331 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,332 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,383 INFO spawned: 'notice_center_writer' with pid 393
|
||||
2025-12-18 20:53:16,478 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,478 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,520 INFO spawned: 'mesh' with pid 395
|
||||
2025-12-18 20:53:16,571 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,571 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,625 INFO spawned: 'notice_center_reader' with pid 397
|
||||
2025-12-18 20:53:16,664 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,664 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,705 INFO spawned: 'notice_center_writer' with pid 399
|
||||
2025-12-18 20:53:16,769 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,810 INFO spawned: 'mesh' with pid 401
|
||||
2025-12-18 20:53:16,810 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,865 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,866 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,971 INFO spawned: 'notice_center_reader' with pid 403
|
||||
2025-12-18 20:53:16,991 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,009 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,102 INFO spawned: 'notice_center_writer' with pid 406
|
||||
2025-12-18 20:53:17,119 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,128 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,160 INFO spawned: 'mesh' with pid 407
|
||||
2025-12-18 20:53:17,251 INFO spawned: 'notice_center_reader' with pid 409
|
||||
2025-12-18 20:53:17,251 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,376 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,378 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,379 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,409 INFO spawned: 'notice_center_writer' with pid 411
|
||||
2025-12-18 20:53:17,410 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,515 INFO spawned: 'mesh' with pid 413
|
||||
2025-12-18 20:53:17,516 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,538 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,538 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,576 INFO spawned: 'notice_center_reader' with pid 414
|
||||
2025-12-18 20:53:17,647 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,647 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,692 INFO spawned: 'notice_center_writer' with pid 417
|
||||
2025-12-18 20:53:17,724 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,724 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,793 INFO spawned: 'mesh' with pid 419
|
||||
2025-12-18 20:53:17,821 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,822 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,900 INFO spawned: 'notice_center_reader' with pid 421
|
||||
2025-12-18 20:53:17,966 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,970 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,067 INFO spawned: 'notice_center_writer' with pid 423
|
||||
2025-12-18 20:53:18,116 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,119 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,171 INFO spawned: 'mesh' with pid 426
|
||||
2025-12-18 20:53:18,198 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,221 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,263 INFO spawned: 'notice_center_reader' with pid 427
|
||||
2025-12-18 20:53:18,314 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,314 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,361 INFO spawned: 'notice_center_writer' with pid 429
|
||||
2025-12-18 20:53:18,408 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,418 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,524 INFO spawned: 'mesh' with pid 432
|
||||
2025-12-18 20:53:18,545 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,545 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,615 INFO spawned: 'notice_center_reader' with pid 433
|
||||
2025-12-18 20:53:18,645 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,656 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,719 INFO spawned: 'notice_center_writer' with pid 435
|
||||
2025-12-18 20:53:18,817 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,817 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,817 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,852 INFO spawned: 'mesh' with pid 437
|
||||
2025-12-18 20:53:18,974 INFO spawned: 'notice_center_reader' with pid 439
|
||||
2025-12-18 20:53:19,030 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,031 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,031 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,073 INFO spawned: 'notice_center_writer' with pid 441
|
||||
2025-12-18 20:53:19,241 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,241 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,384 INFO spawned: 'mesh' with pid 444
|
||||
2025-12-18 20:53:19,417 WARN exited: notice_center_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,417 WARN exited: notice_center_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,432 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,512 INFO spawned: 'notice_center_reader' with pid 445
|
||||
2025-12-18 20:53:19,582 INFO spawned: 'notice_center_writer' with pid 446
|
||||
2025-12-18 20:53:19,732 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,733 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,733 WARN exited: notice_center_reader (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,733 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,733 INFO waiting for mesh, notice_center_writer, sender to die
|
||||
2025-12-18 20:53:19,783 WARN exited: mesh (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,800 WARN exited: notice_center_writer (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,884 INFO stopped: sender (exit status 0)
|
||||
2026-01-25 19:02:21,271 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.
|
||||
2026-01-25 19:02:21,283 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:21,283 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-01-25 19:02:21,283 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-01-25 19:02:21,347 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:21,347 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:21,347 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:22,372 INFO spawned: 'mesh' with pid 17
|
||||
2026-01-25 19:02:22,459 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2026-01-25 19:02:22,513 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2026-01-25 19:02:22,631 INFO spawned: 'sender' with pid 20
|
||||
2026-01-25 19:02:23,646 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:23,646 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:23,646 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:23,646 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:26,334 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.
|
||||
2026-02-04 12:30:26,345 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:26,345 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-02-04 12:30:26,345 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-02-04 12:30:26,694 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:26,694 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:26,694 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:27,724 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 12:30:27,770 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2026-02-04 12:30:27,846 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2026-02-04 12:30:28,004 INFO spawned: 'sender' with pid 20
|
||||
2026-02-04 12:30:28,892 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:28,892 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:28,892 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:28,906 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,293 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.
|
||||
2026-02-04 14:57:35,309 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,310 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-02-04 14:57:35,310 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-02-04 14:57:35,668 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:35,668 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:35,669 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:36,685 INFO spawned: 'mesh' with pid 29
|
||||
2026-02-04 14:57:36,719 INFO spawned: 'notice_center_reader' with pid 30
|
||||
2026-02-04 14:57:36,784 INFO spawned: 'notice_center_writer' with pid 31
|
||||
2026-02-04 14:57:36,895 INFO spawned: 'sender' with pid 32
|
||||
2026-02-04 14:57:37,903 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,904 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,911 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,911 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:55,394 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.
|
||||
2026-02-04 17:30:55,400 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:55,400 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-02-04 17:30:55,400 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-02-04 17:30:55,738 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:55,738 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:55,758 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:56,780 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 17:30:56,856 INFO spawned: 'notice_center_reader' with pid 17
|
||||
2026-02-04 17:30:56,950 INFO spawned: 'notice_center_writer' with pid 18
|
||||
2026-02-04 17:30:56,994 INFO spawned: 'sender' with pid 19
|
||||
2026-02-04 17:30:57,902 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,902 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,902 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,902 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:19,796 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.
|
||||
2026-02-07 14:26:19,811 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:19,811 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-02-07 14:26:19,811 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-02-07 14:26:20,165 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,190 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,190 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,200 INFO spawned: 'mesh' with pid 22
|
||||
2026-02-07 14:26:21,258 INFO spawned: 'notice_center_reader' with pid 23
|
||||
2026-02-07 14:26:21,304 INFO spawned: 'notice_center_writer' with pid 24
|
||||
2026-02-07 14:26:21,543 INFO spawned: 'sender' with pid 25
|
||||
2026-02-07 14:26:22,552 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,552 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,552 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,552 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:20,144 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.
|
||||
2026-02-20 16:02:20,156 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:20,156 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-02-20 16:02:20,156 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-02-20 16:02:20,554 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:20,555 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:20,555 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:21,608 INFO spawned: 'mesh' with pid 23
|
||||
2026-02-20 16:02:21,645 INFO spawned: 'notice_center_reader' with pid 24
|
||||
2026-02-20 16:02:21,732 INFO spawned: 'notice_center_writer' with pid 25
|
||||
2026-02-20 16:02:21,844 INFO spawned: 'sender' with pid 26
|
||||
2026-02-20 16:02:22,864 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,864 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,864 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,864 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:30,727 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.
|
||||
2026-03-04 12:10:30,737 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:30,737 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-03-04 12:10:30,737 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-03-04 12:10:31,113 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,113 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,113 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,128 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-04 12:10:32,169 INFO spawned: 'notice_center_reader' with pid 24
|
||||
2026-03-04 12:10:32,231 INFO spawned: 'notice_center_writer' with pid 25
|
||||
2026-03-04 12:10:32,277 INFO spawned: 'sender' with pid 26
|
||||
2026-03-04 12:10:33,323 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,324 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,324 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,324 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:44,673 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.
|
||||
2026-03-23 09:52:44,679 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,679 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-03-23 09:52:44,680 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-03-23 09:52:45,036 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:45,051 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:45,051 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:46,072 INFO spawned: 'mesh' with pid 26
|
||||
2026-03-23 09:52:46,145 INFO spawned: 'notice_center_reader' with pid 27
|
||||
2026-03-23 09:52:46,198 INFO spawned: 'notice_center_writer' with pid 28
|
||||
2026-03-23 09:52:46,248 INFO spawned: 'sender' with pid 29
|
||||
2026-03-23 09:52:47,281 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,281 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,281 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,281 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:12,783 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.
|
||||
2026-03-25 17:35:12,785 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:12,785 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-03-25 17:35:12,785 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-03-25 17:35:13,100 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:13,100 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:13,101 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:14,111 INFO spawned: 'mesh' with pid 17
|
||||
2026-03-25 17:35:14,170 INFO spawned: 'notice_center_reader' with pid 18
|
||||
2026-03-25 17:35:14,219 INFO spawned: 'notice_center_writer' with pid 19
|
||||
2026-03-25 17:35:14,262 INFO spawned: 'sender' with pid 20
|
||||
2026-03-25 17:35:14,700 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:14,701 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:14,701 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:14,701 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:02,482 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.
|
||||
2026-03-26 07:04:02,496 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:02,496 INFO Included extra file "/opt/supervisor.d/notice_center.conf" during parsing
|
||||
2026-03-26 07:04:02,496 INFO Included extra file "/opt/supervisor.d/sender.conf" during parsing
|
||||
2026-03-26 07:04:02,910 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:02,910 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:02,911 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:03,930 INFO spawned: 'mesh' with pid 26
|
||||
2026-03-26 07:04:03,995 INFO spawned: 'notice_center_reader' with pid 27
|
||||
2026-03-26 07:04:04,046 INFO spawned: 'notice_center_writer' with pid 28
|
||||
2026-03-26 07:04:04,151 INFO spawned: 'sender' with pid 29
|
||||
2026-03-26 07:04:05,179 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,180 INFO success: notice_center_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,180 INFO success: notice_center_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,180 INFO success: sender entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,267 @@
|
||||
2025-11-12 08:50:17,298 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.
|
||||
2025-11-12 08:50:17,298 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:17,298 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-11-12 08:50:17,427 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:17,440 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:17,442 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:18,448 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-12 08:50:18,492 INFO spawned: 'notifier' with pid 18
|
||||
2025-11-12 08:50:19,025 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:19,025 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:25,411 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.
|
||||
2025-11-17 12:01:25,420 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:25,421 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-11-17 12:01:25,786 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:25,786 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:25,786 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:26,794 INFO spawned: 'mesh' with pid 25
|
||||
2025-11-17 12:01:26,891 INFO spawned: 'notifier' with pid 26
|
||||
2025-11-17 12:01:27,894 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:27,895 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:41,737 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.
|
||||
2025-11-21 15:30:41,741 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:41,742 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-11-21 15:30:42,059 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:42,069 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:42,070 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:43,082 INFO spawned: 'mesh' with pid 38
|
||||
2025-11-21 15:30:43,113 INFO spawned: 'notifier' with pid 39
|
||||
2025-11-21 15:30:43,981 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:43,981 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:46,662 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.
|
||||
2025-11-22 15:19:46,682 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:46,682 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-11-22 15:19:47,191 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,191 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,191 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,204 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-22 15:19:48,301 INFO spawned: 'notifier' with pid 27
|
||||
2025-11-22 15:19:49,324 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,324 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:05,159 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:28:05,160 INFO waiting for mesh, notifier to die
|
||||
2025-11-22 15:28:05,346 WARN stopped: notifier (terminated by SIGABRT (core dumped))
|
||||
2025-11-22 15:28:05,361 INFO reaped unknown pid 34 (exit status 0)
|
||||
2025-11-22 15:28:05,492 WARN stopped: mesh (terminated by SIGABRT (core dumped))
|
||||
2025-11-22 15:28:27,916 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.
|
||||
2025-11-22 15:28:27,916 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:27,916 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-11-22 15:28:27,954 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:27,956 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:27,959 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:28,970 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:28:29,023 INFO spawned: 'notifier' with pid 18
|
||||
2025-11-22 15:28:30,063 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:30,063 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:53,346 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:53,353 INFO waiting for mesh, notifier to die
|
||||
2025-11-22 15:30:53,376 INFO stopped: notifier (exit status 0)
|
||||
2025-11-22 15:30:53,395 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:15,390 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.
|
||||
2025-11-22 15:31:15,390 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:15,390 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-11-22 15:31:15,409 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:15,409 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:15,409 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:16,430 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:31:16,516 INFO spawned: 'notifier' with pid 18
|
||||
2025-11-22 15:31:16,962 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,962 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:51,017 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:51,048 INFO waiting for mesh, notifier to die
|
||||
2025-11-22 15:37:51,082 INFO stopped: notifier (exit status 0)
|
||||
2025-11-22 15:37:51,087 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:23,918 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.
|
||||
2025-11-22 15:38:23,918 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:23,922 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-11-22 15:38:23,962 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:23,962 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:23,962 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:25,001 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:38:25,021 INFO spawned: 'notifier' with pid 18
|
||||
2025-11-22 15:38:25,443 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:25,443 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:29,763 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.
|
||||
2025-11-25 15:48:29,807 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:29,807 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-11-25 15:48:30,154 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:30,165 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:30,165 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:31,174 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-25 15:48:31,230 INFO spawned: 'notifier' with pid 18
|
||||
2025-11-25 15:48:32,067 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:32,067 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:24,766 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.
|
||||
2025-12-07 15:52:24,767 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:24,768 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-12-07 15:52:25,084 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:25,096 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:25,096 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:26,110 INFO spawned: 'mesh' with pid 30
|
||||
2025-12-07 15:52:26,197 INFO spawned: 'notifier' with pid 31
|
||||
2025-12-07 15:52:27,209 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,209 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:44,309 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.
|
||||
2025-12-08 11:39:44,313 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:44,314 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-12-08 11:39:44,656 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:44,656 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:44,657 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:45,666 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-08 11:39:45,717 INFO spawned: 'notifier' with pid 36
|
||||
2025-12-08 11:39:46,700 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:46,700 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:50,762 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.
|
||||
2025-12-11 15:42:50,826 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:50,826 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-12-11 15:42:51,170 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:51,170 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:51,171 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:52,180 INFO spawned: 'mesh' with pid 38
|
||||
2025-12-11 15:42:52,258 INFO spawned: 'notifier' with pid 39
|
||||
2025-12-11 15:42:53,282 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,283 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:31,141 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.
|
||||
2025-12-14 06:18:31,145 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:31,146 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-12-14 06:18:31,476 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:31,476 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:31,477 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:32,480 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-14 06:18:32,533 INFO spawned: 'notifier' with pid 36
|
||||
2025-12-14 06:18:33,165 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:33,166 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:42,316 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.
|
||||
2025-12-15 18:35:42,336 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:42,336 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-12-15 18:35:42,680 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:42,680 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:42,696 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:43,705 INFO spawned: 'mesh' with pid 49
|
||||
2025-12-15 18:35:43,813 INFO spawned: 'notifier' with pid 50
|
||||
2025-12-15 18:35:44,642 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:44,642 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:08,765 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.
|
||||
2025-12-18 15:23:08,768 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:08,768 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2025-12-18 15:23:09,081 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:09,081 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:09,081 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:10,095 INFO spawned: 'mesh' with pid 37
|
||||
2025-12-18 15:23:10,125 INFO spawned: 'notifier' with pid 38
|
||||
2025-12-18 15:23:10,858 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:10,858 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,373 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:18,816 INFO spawned: 'mesh' with pid 54
|
||||
2025-12-18 20:53:19,105 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,266 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,266 INFO reaped unknown pid 47 (exit status 0)
|
||||
2025-12-18 20:53:20,297 INFO spawned: 'mesh' with pid 56
|
||||
2025-12-18 20:53:20,298 WARN exited: notifier (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:20,384 INFO reaped unknown pid 45 (terminated by SIGSEGV (core dumped))
|
||||
2025-12-18 20:53:20,837 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,897 INFO spawned: 'notifier' with pid 58
|
||||
2025-12-18 20:53:20,898 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:20,898 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,919 INFO waiting for notifier to die
|
||||
2025-12-18 20:53:21,141 WARN stopped: notifier (exit status 1)
|
||||
2026-01-25 19:02:21,249 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.
|
||||
2026-01-25 19:02:21,254 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:21,255 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-01-25 19:02:21,295 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:21,295 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:21,296 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:22,317 INFO spawned: 'mesh' with pid 27
|
||||
2026-01-25 19:02:22,388 INFO spawned: 'notifier' with pid 28
|
||||
2026-01-25 19:02:23,392 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:23,392 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:41,702 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.
|
||||
2026-02-04 12:30:41,712 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:41,712 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-02-04 12:30:42,055 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:42,061 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:42,062 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:43,079 INFO spawned: 'mesh' with pid 38
|
||||
2026-02-04 12:30:43,148 INFO spawned: 'notifier' with pid 39
|
||||
2026-02-04 12:30:43,911 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:43,962 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,378 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.
|
||||
2026-02-04 14:57:35,425 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,425 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-02-04 14:57:35,756 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:35,768 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:35,770 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:36,777 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 14:57:36,854 INFO spawned: 'notifier' with pid 18
|
||||
2026-02-04 14:57:37,888 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,891 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:03,129 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.
|
||||
2026-02-04 17:31:03,134 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:31:03,134 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-02-04 17:31:03,478 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:31:03,478 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:31:03,478 INFO supervisord started with pid 1
|
||||
2026-02-04 17:31:04,512 INFO spawned: 'mesh' with pid 50
|
||||
2026-02-04 17:31:04,584 INFO spawned: 'notifier' with pid 51
|
||||
2026-02-04 17:31:05,603 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:05,603 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:19,686 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.
|
||||
2026-02-07 14:26:19,708 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:19,708 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-02-07 14:26:20,072 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,072 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,072 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,085 INFO spawned: 'mesh' with pid 22
|
||||
2026-02-07 14:26:21,138 INFO spawned: 'notifier' with pid 23
|
||||
2026-02-07 14:26:22,166 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,167 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:19,567 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.
|
||||
2026-02-20 16:02:19,576 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:19,576 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-02-20 16:02:19,902 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:19,925 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:19,925 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:20,931 INFO spawned: 'mesh' with pid 23
|
||||
2026-02-20 16:02:21,007 INFO spawned: 'notifier' with pid 24
|
||||
2026-02-20 16:02:21,612 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,612 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:31,042 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.
|
||||
2026-03-04 12:10:31,044 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,044 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-03-04 12:10:31,381 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,393 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,393 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,404 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-04 12:10:32,475 INFO spawned: 'notifier' with pid 24
|
||||
2026-03-04 12:10:33,477 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,477 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,724 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.
|
||||
2026-03-23 09:52:48,726 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:48,726 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-03-23 09:52:49,047 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:49,059 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:49,063 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:50,077 INFO spawned: 'mesh' with pid 31
|
||||
2026-03-23 09:52:50,136 INFO spawned: 'notifier' with pid 32
|
||||
2026-03-23 09:52:51,169 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:51,169 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:27,926 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.
|
||||
2026-03-25 17:35:27,944 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:27,944 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-03-25 17:35:28,293 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:28,293 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:28,293 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:29,331 INFO spawned: 'mesh' with pid 39
|
||||
2026-03-25 17:35:29,365 INFO spawned: 'notifier' with pid 40
|
||||
2026-03-25 17:35:30,023 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:30,023 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:02,501 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.
|
||||
2026-03-26 07:04:02,506 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:02,506 INFO Included extra file "/opt/supervisor.d/notifier.conf" during parsing
|
||||
2026-03-26 07:04:02,913 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:02,945 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:02,945 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:03,949 INFO spawned: 'mesh' with pid 25
|
||||
2026-03-26 07:04:04,012 INFO spawned: 'notifier' with pid 26
|
||||
2026-03-26 07:04:04,982 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:04,982 INFO success: notifier entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,650 @@
|
||||
2025-11-12 08:50:19,840 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.
|
||||
2025-11-12 08:50:19,850 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:19,850 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-11-12 08:50:19,850 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-11-12 08:50:19,850 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-11-12 08:50:19,850 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-11-12 08:50:19,911 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:19,911 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:19,911 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:20,926 INFO spawned: 'mesh' with pid 27
|
||||
2025-11-12 08:50:20,994 INFO spawned: 'nginx' with pid 28
|
||||
2025-11-12 08:50:21,017 INFO spawned: 'plugin_checker' with pid 29
|
||||
2025-11-12 08:50:21,114 INFO spawned: 'plugin_service_reader' with pid 31
|
||||
2025-11-12 08:50:21,239 INFO spawned: 'plugin_service_writer' with pid 34
|
||||
2025-11-12 08:50:21,418 INFO spawned: 'taskmgr_worker' with pid 36
|
||||
2025-11-12 08:50:21,452 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,574 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,574 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,574 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,574 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:21,574 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:36,487 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.
|
||||
2025-11-17 12:01:36,488 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:36,488 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-11-17 12:01:36,488 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-11-17 12:01:36,488 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-11-17 12:01:36,488 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-11-17 12:01:36,826 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:36,826 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:36,839 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:37,850 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-17 12:01:37,890 INFO spawned: 'nginx' with pid 29
|
||||
2025-11-17 12:01:37,946 INFO spawned: 'plugin_checker' with pid 31
|
||||
2025-11-17 12:01:37,973 INFO spawned: 'plugin_service_reader' with pid 34
|
||||
2025-11-17 12:01:38,046 INFO spawned: 'plugin_service_writer' with pid 35
|
||||
2025-11-17 12:01:38,124 INFO spawned: 'taskmgr_worker' with pid 36
|
||||
2025-11-17 12:01:38,125 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:38,125 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:38,125 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:38,125 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:38,125 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:38,125 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:36,539 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.
|
||||
2025-11-21 15:30:36,539 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:36,541 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-11-21 15:30:36,541 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-11-21 15:30:36,542 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-11-21 15:30:36,543 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-11-21 15:30:36,874 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:36,874 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:36,874 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:37,883 INFO spawned: 'mesh' with pid 31
|
||||
2025-11-21 15:30:37,946 INFO spawned: 'nginx' with pid 32
|
||||
2025-11-21 15:30:38,003 INFO spawned: 'plugin_checker' with pid 34
|
||||
2025-11-21 15:30:38,093 INFO spawned: 'plugin_service_reader' with pid 35
|
||||
2025-11-21 15:30:38,229 INFO spawned: 'plugin_service_writer' with pid 38
|
||||
2025-11-21 15:30:38,353 INFO spawned: 'taskmgr_worker' with pid 40
|
||||
2025-11-21 15:30:38,437 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,437 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,437 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,438 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,471 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,471 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:50,517 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.
|
||||
2025-11-22 15:19:50,530 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:50,530 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-11-22 15:19:50,530 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-11-22 15:19:50,530 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-11-22 15:19:50,530 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-11-22 15:19:50,871 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:50,871 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:50,871 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:51,887 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-22 15:19:51,935 INFO spawned: 'nginx' with pid 29
|
||||
2025-11-22 15:19:52,032 INFO spawned: 'plugin_checker' with pid 31
|
||||
2025-11-22 15:19:52,189 INFO spawned: 'plugin_service_reader' with pid 32
|
||||
2025-11-22 15:19:52,383 INFO spawned: 'plugin_service_writer' with pid 35
|
||||
2025-11-22 15:19:52,425 INFO spawned: 'taskmgr_worker' with pid 39
|
||||
2025-11-22 15:19:52,518 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,585 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,585 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,586 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,586 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:52,586 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:57,584 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:57,591 INFO waiting for mesh, nginx, plugin_checker, plugin_service_reader, plugin_service_writer, taskmgr_worker to die
|
||||
2025-11-22 15:27:57,827 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:27:58,423 INFO stopped: plugin_service_writer (exit status 0)
|
||||
2025-11-22 15:27:58,606 INFO stopped: plugin_service_reader (exit status 0)
|
||||
2025-11-22 15:27:58,618 WARN stopped: plugin_checker (terminated by SIGTERM)
|
||||
2025-11-22 15:27:58,666 INFO stopped: nginx (exit status 0)
|
||||
2025-11-22 15:27:58,790 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:23,803 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.
|
||||
2025-11-22 15:28:23,803 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:23,803 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-11-22 15:28:23,803 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-11-22 15:28:23,803 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-11-22 15:28:23,803 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-11-22 15:28:23,825 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:23,836 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:23,841 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:24,846 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-22 15:28:24,869 INFO spawned: 'nginx' with pid 29
|
||||
2025-11-22 15:28:24,929 INFO spawned: 'plugin_checker' with pid 31
|
||||
2025-11-22 15:28:24,976 INFO spawned: 'plugin_service_reader' with pid 32
|
||||
2025-11-22 15:28:25,011 INFO spawned: 'plugin_service_writer' with pid 33
|
||||
2025-11-22 15:28:25,073 INFO spawned: 'taskmgr_worker' with pid 36
|
||||
2025-11-22 15:28:25,156 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,156 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,156 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,156 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,195 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:25,195 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:45,759 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:45,770 INFO waiting for mesh, nginx, plugin_checker, plugin_service_reader, plugin_service_writer, taskmgr_worker to die
|
||||
2025-11-22 15:30:45,790 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:30:45,901 INFO stopped: plugin_service_writer (exit status 0)
|
||||
2025-11-22 15:30:46,058 INFO stopped: plugin_service_reader (exit status 0)
|
||||
2025-11-22 15:30:46,064 WARN stopped: plugin_checker (terminated by SIGTERM)
|
||||
2025-11-22 15:30:46,094 INFO stopped: nginx (exit status 0)
|
||||
2025-11-22 15:30:46,331 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:21,326 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.
|
||||
2025-11-22 15:31:21,337 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:21,337 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-11-22 15:31:21,337 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-11-22 15:31:21,337 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-11-22 15:31:21,337 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-11-22 15:31:21,371 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:21,371 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:21,371 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:22,387 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-22 15:31:22,548 INFO spawned: 'nginx' with pid 30
|
||||
2025-11-22 15:31:22,634 INFO spawned: 'plugin_checker' with pid 31
|
||||
2025-11-22 15:31:22,699 INFO spawned: 'plugin_service_reader' with pid 32
|
||||
2025-11-22 15:31:22,845 INFO spawned: 'plugin_service_writer' with pid 35
|
||||
2025-11-22 15:31:22,921 INFO spawned: 'taskmgr_worker' with pid 37
|
||||
2025-11-22 15:31:22,982 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,982 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,982 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,982 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,982 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:22,983 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:42,643 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:42,654 INFO waiting for mesh, nginx, plugin_checker, plugin_service_reader, plugin_service_writer, taskmgr_worker to die
|
||||
2025-11-22 15:37:42,712 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:37:42,821 INFO stopped: plugin_service_writer (exit status 0)
|
||||
2025-11-22 15:37:43,076 INFO stopped: plugin_service_reader (exit status 0)
|
||||
2025-11-22 15:37:43,095 WARN stopped: plugin_checker (terminated by SIGTERM)
|
||||
2025-11-22 15:37:43,164 INFO stopped: nginx (exit status 0)
|
||||
2025-11-22 15:37:43,515 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:21,375 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.
|
||||
2025-11-22 15:38:21,375 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:21,375 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-11-22 15:38:21,375 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-11-22 15:38:21,375 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-11-22 15:38:21,375 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-11-22 15:38:21,388 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:21,388 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:21,388 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:22,395 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-22 15:38:22,444 INFO spawned: 'nginx' with pid 29
|
||||
2025-11-22 15:38:22,484 INFO spawned: 'plugin_checker' with pid 31
|
||||
2025-11-22 15:38:22,525 INFO spawned: 'plugin_service_reader' with pid 32
|
||||
2025-11-22 15:38:22,621 INFO spawned: 'plugin_service_writer' with pid 36
|
||||
2025-11-22 15:38:22,695 INFO spawned: 'taskmgr_worker' with pid 37
|
||||
2025-11-22 15:38:22,741 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:22,741 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:22,741 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:22,741 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:22,741 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:22,742 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:34,163 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.
|
||||
2025-11-25 15:48:34,182 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:34,182 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-11-25 15:48:34,182 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-11-25 15:48:34,182 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-11-25 15:48:34,182 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-11-25 15:48:34,512 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:34,535 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:34,536 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:35,546 INFO spawned: 'mesh' with pid 28
|
||||
2025-11-25 15:48:35,608 INFO spawned: 'nginx' with pid 29
|
||||
2025-11-25 15:48:35,697 INFO spawned: 'plugin_checker' with pid 31
|
||||
2025-11-25 15:48:35,792 INFO spawned: 'plugin_service_reader' with pid 34
|
||||
2025-11-25 15:48:35,987 INFO spawned: 'plugin_service_writer' with pid 35
|
||||
2025-11-25 15:48:36,068 INFO spawned: 'taskmgr_worker' with pid 36
|
||||
2025-11-25 15:48:36,155 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:36,155 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:36,155 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:36,155 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:36,155 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:36,155 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:23,515 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.
|
||||
2025-12-07 15:52:23,535 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:23,535 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-12-07 15:52:23,535 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-12-07 15:52:23,535 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-12-07 15:52:23,535 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-12-07 15:52:23,864 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:23,898 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:23,899 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:24,903 INFO spawned: 'mesh' with pid 31
|
||||
2025-12-07 15:52:24,983 INFO spawned: 'nginx' with pid 32
|
||||
2025-12-07 15:52:25,015 INFO spawned: 'plugin_checker' with pid 36
|
||||
2025-12-07 15:52:25,160 INFO spawned: 'plugin_service_reader' with pid 37
|
||||
2025-12-07 15:52:25,276 INFO spawned: 'plugin_service_writer' with pid 38
|
||||
2025-12-07 15:52:25,366 INFO spawned: 'taskmgr_worker' with pid 40
|
||||
2025-12-07 15:52:25,445 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,445 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,445 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,445 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,445 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,445 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:40,849 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.
|
||||
2025-12-08 11:39:40,867 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:40,867 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-12-08 11:39:40,867 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-12-08 11:39:40,867 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-12-08 11:39:40,867 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-12-08 11:39:41,203 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:41,212 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:41,213 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:42,257 INFO spawned: 'mesh' with pid 28
|
||||
2025-12-08 11:39:42,340 INFO spawned: 'nginx' with pid 29
|
||||
2025-12-08 11:39:42,436 INFO spawned: 'plugin_checker' with pid 31
|
||||
2025-12-08 11:39:42,645 INFO spawned: 'plugin_service_reader' with pid 32
|
||||
2025-12-08 11:39:42,738 INFO spawned: 'plugin_service_writer' with pid 35
|
||||
2025-12-08 11:39:42,845 INFO spawned: 'taskmgr_worker' with pid 37
|
||||
2025-12-08 11:39:42,961 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:42,961 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:42,961 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:42,961 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:42,961 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:42,961 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:43,508 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.
|
||||
2025-12-11 15:42:43,511 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:43,512 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-12-11 15:42:43,513 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-12-11 15:42:43,513 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-12-11 15:42:43,513 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-12-11 15:42:43,835 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:43,852 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:43,853 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:44,868 INFO spawned: 'mesh' with pid 34
|
||||
2025-12-11 15:42:44,931 INFO spawned: 'nginx' with pid 36
|
||||
2025-12-11 15:42:45,090 INFO spawned: 'plugin_checker' with pid 37
|
||||
2025-12-11 15:42:45,169 INFO spawned: 'plugin_service_reader' with pid 40
|
||||
2025-12-11 15:42:45,322 INFO spawned: 'plugin_service_writer' with pid 41
|
||||
2025-12-11 15:42:45,499 INFO spawned: 'taskmgr_worker' with pid 42
|
||||
2025-12-11 15:42:45,521 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,522 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,522 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,522 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,522 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,522 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:25,884 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.
|
||||
2025-12-14 06:18:25,891 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,891 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-12-14 06:18:25,891 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-12-14 06:18:25,892 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-12-14 06:18:25,892 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-12-14 06:18:26,218 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:26,224 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:26,224 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:27,234 INFO spawned: 'mesh' with pid 31
|
||||
2025-12-14 06:18:27,296 INFO spawned: 'nginx' with pid 32
|
||||
2025-12-14 06:18:27,385 INFO spawned: 'plugin_checker' with pid 34
|
||||
2025-12-14 06:18:27,485 INFO spawned: 'plugin_service_reader' with pid 35
|
||||
2025-12-14 06:18:27,553 INFO spawned: 'plugin_service_writer' with pid 36
|
||||
2025-12-14 06:18:27,800 INFO spawned: 'taskmgr_worker' with pid 40
|
||||
2025-12-14 06:18:27,882 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,925 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,925 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,926 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,926 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,926 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:35,630 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.
|
||||
2025-12-15 18:35:35,645 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:35,645 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-12-15 18:35:35,645 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-12-15 18:35:35,645 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-12-15 18:35:35,645 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-12-15 18:35:35,980 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:35,980 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:36,003 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:37,030 INFO spawned: 'mesh' with pid 34
|
||||
2025-12-15 18:35:37,052 INFO spawned: 'nginx' with pid 36
|
||||
2025-12-15 18:35:37,164 INFO spawned: 'plugin_checker' with pid 37
|
||||
2025-12-15 18:35:37,314 INFO spawned: 'plugin_service_reader' with pid 38
|
||||
2025-12-15 18:35:37,407 INFO spawned: 'plugin_service_writer' with pid 41
|
||||
2025-12-15 18:35:37,494 INFO spawned: 'taskmgr_worker' with pid 42
|
||||
2025-12-15 18:35:37,558 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:37,558 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:37,558 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:37,558 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:37,558 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:37,558 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:56,222 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.
|
||||
2025-12-18 15:22:56,223 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:56,223 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2025-12-18 15:22:56,223 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2025-12-18 15:22:56,223 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2025-12-18 15:22:56,223 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2025-12-18 15:22:56,570 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:56,570 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:56,572 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:57,578 INFO spawned: 'mesh' with pid 28
|
||||
2025-12-18 15:22:57,619 INFO spawned: 'nginx' with pid 29
|
||||
2025-12-18 15:22:57,709 INFO spawned: 'plugin_checker' with pid 33
|
||||
2025-12-18 15:22:57,834 INFO spawned: 'plugin_service_reader' with pid 34
|
||||
2025-12-18 15:22:57,935 INFO spawned: 'plugin_service_writer' with pid 35
|
||||
2025-12-18 15:22:58,134 INFO spawned: 'taskmgr_worker' with pid 37
|
||||
2025-12-18 15:22:58,146 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:58,186 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:58,186 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:58,186 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:58,186 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:58,186 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,968 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:16,020 INFO spawned: 'mesh' with pid 56
|
||||
2025-12-18 20:53:16,033 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,165 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,289 INFO spawned: 'mesh' with pid 58
|
||||
2025-12-18 20:53:16,323 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,357 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,408 INFO spawned: 'mesh' with pid 60
|
||||
2025-12-18 20:53:16,420 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,432 WARN exited: plugin_service_writer (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:16,451 INFO spawned: 'plugin_service_writer' with pid 62
|
||||
2025-12-18 20:53:16,464 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,468 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,493 INFO spawned: 'mesh' with pid 63
|
||||
2025-12-18 20:53:16,519 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,566 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,597 INFO spawned: 'plugin_service_writer' with pid 66
|
||||
2025-12-18 20:53:16,650 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,668 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,704 INFO spawned: 'mesh' with pid 68
|
||||
2025-12-18 20:53:16,746 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,774 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,808 INFO spawned: 'plugin_service_writer' with pid 69
|
||||
2025-12-18 20:53:16,840 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,875 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,909 INFO spawned: 'mesh' with pid 71
|
||||
2025-12-18 20:53:16,943 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,968 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,012 INFO spawned: 'plugin_service_writer' with pid 74
|
||||
2025-12-18 20:53:17,013 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,020 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,070 INFO spawned: 'mesh' with pid 75
|
||||
2025-12-18 20:53:17,080 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,220 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,258 INFO spawned: 'mesh' with pid 78
|
||||
2025-12-18 20:53:17,286 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,304 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,348 INFO spawned: 'plugin_service_writer' with pid 79
|
||||
2025-12-18 20:53:17,366 WARN exited: plugin_service_reader (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:17,366 INFO exited: taskmgr_worker (exit status 0; expected)
|
||||
2025-12-18 20:53:17,486 INFO spawned: 'plugin_service_reader' with pid 81
|
||||
2025-12-18 20:53:17,487 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,509 INFO spawned: 'taskmgr_worker' with pid 83
|
||||
2025-12-18 20:53:17,510 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,639 INFO spawned: 'mesh' with pid 85
|
||||
2025-12-18 20:53:17,639 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,639 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,640 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,640 WARN exited: plugin_service_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,685 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,741 INFO spawned: 'plugin_service_reader' with pid 87
|
||||
2025-12-18 20:53:17,818 INFO spawned: 'plugin_service_writer' with pid 90
|
||||
2025-12-18 20:53:17,878 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,878 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,878 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:17,908 INFO spawned: 'taskmgr_worker' with pid 91
|
||||
2025-12-18 20:53:17,909 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,026 INFO spawned: 'mesh' with pid 94
|
||||
2025-12-18 20:53:18,043 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,093 WARN exited: plugin_service_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,093 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,093 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:18,093 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,125 INFO spawned: 'plugin_service_reader' with pid 96
|
||||
2025-12-18 20:53:18,225 INFO spawned: 'plugin_service_writer' with pid 97
|
||||
2025-12-18 20:53:18,307 INFO spawned: 'taskmgr_worker' with pid 100
|
||||
2025-12-18 20:53:18,308 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,436 INFO spawned: 'mesh' with pid 101
|
||||
2025-12-18 20:53:18,440 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,446 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,470 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,477 WARN exited: plugin_service_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,499 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,500 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,596 INFO spawned: 'plugin_service_reader' with pid 103
|
||||
2025-12-18 20:53:18,650 INFO spawned: 'plugin_service_writer' with pid 105
|
||||
2025-12-18 20:53:18,686 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:18,696 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,771 INFO spawned: 'mesh' with pid 107
|
||||
2025-12-18 20:53:18,791 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,795 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,855 INFO spawned: 'taskmgr_worker' with pid 109
|
||||
2025-12-18 20:53:18,886 WARN exited: plugin_service_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,916 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,974 INFO spawned: 'plugin_service_reader' with pid 110
|
||||
2025-12-18 20:53:18,974 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,009 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,051 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,129 INFO spawned: 'plugin_service_writer' with pid 113
|
||||
2025-12-18 20:53:19,182 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,294 INFO spawned: 'mesh' with pid 115
|
||||
2025-12-18 20:53:19,295 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,295 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,295 WARN exited: plugin_service_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,357 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,420 INFO spawned: 'plugin_service_reader' with pid 117
|
||||
2025-12-18 20:53:19,576 INFO spawned: 'taskmgr_worker' with pid 119
|
||||
2025-12-18 20:53:19,626 WARN exited: plugin_service_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,770 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,917 INFO spawned: 'plugin_service_writer' with pid 121
|
||||
2025-12-18 20:53:19,947 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,948 INFO exited: nginx (exit status 0; expected)
|
||||
2025-12-18 20:53:19,948 WARN exited: plugin_checker (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,948 WARN exited: mesh (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,948 WARN exited: plugin_service_reader (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:20,026 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,081 INFO waiting for plugin_service_writer, taskmgr_worker to die
|
||||
2025-12-18 20:53:20,081 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,081 WARN stopped: taskmgr_worker (terminated by SIGABRT (core dumped))
|
||||
2025-12-18 20:53:20,090 WARN stopped: plugin_service_writer (terminated by SIGTERM)
|
||||
2026-01-25 19:02:20,372 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.
|
||||
2026-01-25 19:02:20,387 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:20,387 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-01-25 19:02:20,387 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-01-25 19:02:20,387 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-01-25 19:02:20,387 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-01-25 19:02:20,435 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:20,435 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:20,436 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:21,454 INFO spawned: 'mesh' with pid 31
|
||||
2026-01-25 19:02:21,596 INFO spawned: 'nginx' with pid 32
|
||||
2026-01-25 19:02:21,743 INFO spawned: 'plugin_checker' with pid 34
|
||||
2026-01-25 19:02:21,892 INFO spawned: 'plugin_service_reader' with pid 37
|
||||
2026-01-25 19:02:21,988 INFO spawned: 'plugin_service_writer' with pid 38
|
||||
2026-01-25 19:02:22,182 INFO spawned: 'taskmgr_worker' with pid 41
|
||||
2026-01-25 19:02:22,183 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,183 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,183 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,183 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,183 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,183 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:21,683 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.
|
||||
2026-02-04 12:30:21,686 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:21,686 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-02-04 12:30:21,686 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-02-04 12:30:21,686 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-02-04 12:30:21,686 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-02-04 12:30:21,997 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:21,997 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:21,997 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:23,015 INFO spawned: 'mesh' with pid 28
|
||||
2026-02-04 12:30:23,051 INFO spawned: 'nginx' with pid 29
|
||||
2026-02-04 12:30:23,077 INFO spawned: 'plugin_checker' with pid 30
|
||||
2026-02-04 12:30:23,095 INFO spawned: 'plugin_service_reader' with pid 31
|
||||
2026-02-04 12:30:23,161 INFO spawned: 'plugin_service_writer' with pid 32
|
||||
2026-02-04 12:30:23,199 INFO spawned: 'taskmgr_worker' with pid 34
|
||||
2026-02-04 12:30:23,240 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,241 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,241 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,241 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,241 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,241 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:36,565 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.
|
||||
2026-02-04 14:57:36,569 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:36,569 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-02-04 14:57:36,569 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-02-04 14:57:36,569 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-02-04 14:57:36,569 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-02-04 14:57:36,905 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,905 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,905 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,920 INFO spawned: 'mesh' with pid 40
|
||||
2026-02-04 14:57:37,986 INFO spawned: 'nginx' with pid 41
|
||||
2026-02-04 14:57:38,050 INFO spawned: 'plugin_checker' with pid 43
|
||||
2026-02-04 14:57:38,159 INFO spawned: 'plugin_service_reader' with pid 44
|
||||
2026-02-04 14:57:38,269 INFO spawned: 'plugin_service_writer' with pid 47
|
||||
2026-02-04 14:57:38,600 INFO spawned: 'taskmgr_worker' with pid 50
|
||||
2026-02-04 14:57:38,602 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,602 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,602 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,602 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,602 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,602 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:56,896 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.
|
||||
2026-02-04 17:30:56,912 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:56,912 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-02-04 17:30:56,912 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-02-04 17:30:56,912 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-02-04 17:30:56,912 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-02-04 17:30:57,269 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:57,278 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:57,278 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:58,305 INFO spawned: 'mesh' with pid 28
|
||||
2026-02-04 17:30:58,411 INFO spawned: 'nginx' with pid 29
|
||||
2026-02-04 17:30:58,457 INFO spawned: 'plugin_checker' with pid 31
|
||||
2026-02-04 17:30:58,606 INFO spawned: 'plugin_service_reader' with pid 32
|
||||
2026-02-04 17:30:58,727 INFO spawned: 'plugin_service_writer' with pid 35
|
||||
2026-02-04 17:30:58,822 INFO spawned: 'taskmgr_worker' with pid 36
|
||||
2026-02-04 17:30:58,996 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:58,996 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:58,996 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:58,996 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:58,996 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:58,996 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:22,944 WARN exited: plugin_checker (exit status 1; not expected)
|
||||
2026-02-04 17:31:24,018 INFO spawned: 'plugin_checker' with pid 47
|
||||
2026-02-04 17:31:25,025 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:47,897 WARN exited: plugin_checker (exit status 1; not expected)
|
||||
2026-02-04 17:31:48,927 INFO spawned: 'plugin_checker' with pid 48
|
||||
2026-02-04 17:31:49,754 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:32:10,259 WARN exited: plugin_checker (exit status 1; not expected)
|
||||
2026-02-04 17:32:11,265 INFO spawned: 'plugin_checker' with pid 49
|
||||
2026-02-04 17:32:12,269 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:32:32,075 WARN exited: plugin_checker (exit status 1; not expected)
|
||||
2026-02-04 17:32:32,555 INFO spawned: 'plugin_checker' with pid 58
|
||||
2026-02-04 17:32:32,564 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,992 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.
|
||||
2026-02-07 14:26:23,004 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:23,004 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-02-07 14:26:23,004 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-02-07 14:26:23,004 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-02-07 14:26:23,004 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-02-07 14:26:23,339 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:23,358 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:23,358 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:24,369 INFO spawned: 'mesh' with pid 37
|
||||
2026-02-07 14:26:24,494 INFO spawned: 'nginx' with pid 39
|
||||
2026-02-07 14:26:24,516 INFO spawned: 'plugin_checker' with pid 40
|
||||
2026-02-07 14:26:24,601 INFO spawned: 'plugin_service_reader' with pid 41
|
||||
2026-02-07 14:26:24,799 INFO spawned: 'plugin_service_writer' with pid 42
|
||||
2026-02-07 14:26:24,926 INFO spawned: 'taskmgr_worker' with pid 47
|
||||
2026-02-07 14:26:25,032 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:25,032 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:25,032 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:25,032 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:25,033 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:25,033 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,410 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.
|
||||
2026-02-20 16:02:21,430 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:21,430 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-02-20 16:02:21,430 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-02-20 16:02:21,430 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-02-20 16:02:21,430 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-02-20 16:02:21,760 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,760 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,760 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,794 INFO spawned: 'mesh' with pid 34
|
||||
2026-02-20 16:02:22,856 INFO spawned: 'nginx' with pid 35
|
||||
2026-02-20 16:02:22,944 INFO spawned: 'plugin_checker' with pid 36
|
||||
2026-02-20 16:02:23,030 INFO spawned: 'plugin_service_reader' with pid 38
|
||||
2026-02-20 16:02:23,186 INFO spawned: 'plugin_service_writer' with pid 41
|
||||
2026-02-20 16:02:23,433 INFO spawned: 'taskmgr_worker' with pid 43
|
||||
2026-02-20 16:02:23,515 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,515 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,515 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,515 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,515 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,515 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:31,375 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.
|
||||
2026-03-04 12:10:31,380 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,380 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-03-04 12:10:31,380 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-03-04 12:10:31,380 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-03-04 12:10:31,380 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-03-04 12:10:31,733 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,733 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,733 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,762 INFO spawned: 'mesh' with pid 34
|
||||
2026-03-04 12:10:32,836 INFO spawned: 'nginx' with pid 36
|
||||
2026-03-04 12:10:33,012 INFO spawned: 'plugin_checker' with pid 37
|
||||
2026-03-04 12:10:33,135 INFO spawned: 'plugin_service_reader' with pid 38
|
||||
2026-03-04 12:10:33,252 INFO spawned: 'plugin_service_writer' with pid 42
|
||||
2026-03-04 12:10:33,532 INFO spawned: 'taskmgr_worker' with pid 43
|
||||
2026-03-04 12:10:33,649 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,649 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,649 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,649 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,649 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,649 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,558 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.
|
||||
2026-03-23 09:52:46,576 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:46,576 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-03-23 09:52:46,576 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-03-23 09:52:46,576 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-03-23 09:52:46,576 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-03-23 09:52:46,924 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:46,924 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:46,925 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:47,933 INFO spawned: 'mesh' with pid 32
|
||||
2026-03-23 09:52:47,971 INFO spawned: 'nginx' with pid 33
|
||||
2026-03-23 09:52:48,128 INFO spawned: 'plugin_checker' with pid 35
|
||||
2026-03-23 09:52:48,218 INFO spawned: 'plugin_service_reader' with pid 36
|
||||
2026-03-23 09:52:48,301 INFO spawned: 'plugin_service_writer' with pid 37
|
||||
2026-03-23 09:52:48,478 INFO spawned: 'taskmgr_worker' with pid 42
|
||||
2026-03-23 09:52:48,557 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,557 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,557 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,557 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,557 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,557 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:17,568 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.
|
||||
2026-03-25 17:35:17,576 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:17,577 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-03-25 17:35:17,577 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-03-25 17:35:17,577 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-03-25 17:35:17,577 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-03-25 17:35:17,926 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:17,927 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:17,927 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:18,947 INFO spawned: 'mesh' with pid 28
|
||||
2026-03-25 17:35:19,067 INFO spawned: 'nginx' with pid 29
|
||||
2026-03-25 17:35:19,170 INFO spawned: 'plugin_checker' with pid 31
|
||||
2026-03-25 17:35:19,340 INFO spawned: 'plugin_service_reader' with pid 34
|
||||
2026-03-25 17:35:19,460 INFO spawned: 'plugin_service_writer' with pid 35
|
||||
2026-03-25 17:35:19,640 INFO spawned: 'taskmgr_worker' with pid 36
|
||||
2026-03-25 17:35:19,696 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,795 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,795 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,795 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,795 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,795 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:04,302 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.
|
||||
2026-03-26 07:04:04,316 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:04,316 INFO Included extra file "/etc/supervisord.conf.d/nginx.conf" during parsing
|
||||
2026-03-26 07:04:04,316 INFO Included extra file "/etc/supervisord.conf.d/plugin_checker.conf" during parsing
|
||||
2026-03-26 07:04:04,316 INFO Included extra file "/etc/supervisord.conf.d/plugin_service.conf" during parsing
|
||||
2026-03-26 07:04:04,316 INFO Included extra file "/etc/supervisord.conf.d/worker.conf" during parsing
|
||||
2026-03-26 07:04:04,692 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:04,692 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:04,692 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:05,707 INFO spawned: 'mesh' with pid 33
|
||||
2026-03-26 07:04:05,832 INFO spawned: 'nginx' with pid 35
|
||||
2026-03-26 07:04:05,901 INFO spawned: 'plugin_checker' with pid 36
|
||||
2026-03-26 07:04:05,974 INFO spawned: 'plugin_service_reader' with pid 37
|
||||
2026-03-26 07:04:06,059 INFO spawned: 'plugin_service_writer' with pid 38
|
||||
2026-03-26 07:04:06,157 INFO spawned: 'taskmgr_worker' with pid 40
|
||||
2026-03-26 07:04:06,242 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,242 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,242 INFO success: plugin_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,242 INFO success: plugin_service_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,242 INFO success: plugin_service_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,242 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,503 @@
|
||||
2025-07-19 14:29:13,246 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.
|
||||
2025-07-19 14:29:13,251 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-07-19 14:29:13,251 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-07-19 14:29:13,251 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-07-19 14:29:13,280 INFO RPC interface 'supervisor' initialized
|
||||
2025-07-19 14:29:13,280 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-07-19 14:29:13,282 INFO supervisord started with pid 1
|
||||
2025-07-19 14:29:14,290 INFO spawned: 'mesh' with pid 17
|
||||
2025-07-19 14:29:14,389 INFO spawned: 'report' with pid 19
|
||||
2025-07-19 14:29:14,487 INFO spawned: 'taskmgr_worker' with pid 20
|
||||
2025-07-19 14:29:15,490 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-19 14:29:15,518 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-19 14:29:15,518 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-19 14:34:04,548 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.
|
||||
2025-07-19 14:34:04,550 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-07-19 14:34:04,550 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-07-19 14:34:04,550 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-07-19 14:34:04,890 INFO RPC interface 'supervisor' initialized
|
||||
2025-07-19 14:34:04,891 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-07-19 14:34:04,891 INFO supervisord started with pid 1
|
||||
2025-07-19 14:34:05,899 INFO spawned: 'mesh' with pid 23
|
||||
2025-07-19 14:34:06,006 INFO spawned: 'report' with pid 24
|
||||
2025-07-19 14:34:06,044 INFO spawned: 'taskmgr_worker' with pid 25
|
||||
2025-07-19 14:34:07,137 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-19 14:34:07,137 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-19 14:34:07,138 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-22 09:00:50,675 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.
|
||||
2025-07-22 09:00:50,682 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-07-22 09:00:50,684 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-07-22 09:00:50,684 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-07-22 09:00:51,055 INFO RPC interface 'supervisor' initialized
|
||||
2025-07-22 09:00:51,055 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-07-22 09:00:51,055 INFO supervisord started with pid 1
|
||||
2025-07-22 09:00:52,062 INFO spawned: 'mesh' with pid 20
|
||||
2025-07-22 09:00:52,109 INFO spawned: 'report' with pid 21
|
||||
2025-07-22 09:00:52,201 INFO spawned: 'taskmgr_worker' with pid 26
|
||||
2025-07-22 09:00:53,270 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-22 09:00:53,270 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-22 09:00:53,270 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-31 11:18:49,615 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.
|
||||
2025-07-31 11:18:49,620 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-07-31 11:18:49,620 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-07-31 11:18:49,620 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-07-31 11:18:49,963 INFO RPC interface 'supervisor' initialized
|
||||
2025-07-31 11:18:49,963 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-07-31 11:18:50,001 INFO supervisord started with pid 1
|
||||
2025-07-31 11:18:51,009 INFO spawned: 'mesh' with pid 29
|
||||
2025-07-31 11:18:51,117 INFO spawned: 'report' with pid 30
|
||||
2025-07-31 11:18:51,176 INFO spawned: 'taskmgr_worker' with pid 32
|
||||
2025-07-31 11:18:52,177 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-31 11:18:52,177 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-07-31 11:18:52,177 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-09 07:24:33,078 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.
|
||||
2025-08-09 07:24:33,080 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-08-09 07:24:33,080 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-08-09 07:24:33,080 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-08-09 07:24:33,432 INFO RPC interface 'supervisor' initialized
|
||||
2025-08-09 07:24:33,432 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-08-09 07:24:33,432 INFO supervisord started with pid 1
|
||||
2025-08-09 07:24:34,440 INFO spawned: 'mesh' with pid 22
|
||||
2025-08-09 07:24:34,513 INFO spawned: 'report' with pid 23
|
||||
2025-08-09 07:24:34,574 INFO spawned: 'taskmgr_worker' with pid 24
|
||||
2025-08-09 07:24:35,676 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-09 07:24:35,676 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-09 07:24:35,676 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:02:01,980 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.
|
||||
2025-08-30 21:02:01,982 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-08-30 21:02:01,982 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-08-30 21:02:01,982 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-08-30 21:02:02,328 INFO RPC interface 'supervisor' initialized
|
||||
2025-08-30 21:02:02,341 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-08-30 21:02:02,341 INFO supervisord started with pid 1
|
||||
2025-08-30 21:02:03,349 INFO spawned: 'mesh' with pid 23
|
||||
2025-08-30 21:02:03,408 INFO spawned: 'report' with pid 24
|
||||
2025-08-30 21:02:03,468 INFO spawned: 'taskmgr_worker' with pid 25
|
||||
2025-08-30 21:02:04,541 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:02:04,541 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:02:04,541 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-08-30 21:38:52,226 WARN received SIGTERM indicating exit request
|
||||
2025-08-30 21:38:52,228 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-08-30 21:38:55,233 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-08-30 21:38:58,238 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-08-30 21:39:01,244 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-08-30 21:39:02,245 WARN killing 'taskmgr_worker' (25) with SIGKILL
|
||||
2025-08-30 21:39:02,246 WARN stopped: taskmgr_worker (terminated by SIGKILL)
|
||||
2025-08-30 21:39:04,248 INFO waiting for mesh, report to die
|
||||
2025-08-30 21:39:07,254 INFO waiting for mesh, report to die
|
||||
2025-08-30 21:39:10,260 INFO waiting for mesh, report to die
|
||||
2025-08-30 21:39:12,263 WARN killing 'report' (24) with SIGKILL
|
||||
2025-08-30 21:39:12,265 WARN stopped: report (terminated by SIGKILL)
|
||||
2025-09-02 13:52:13,400 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.
|
||||
2025-09-02 13:52:13,402 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-09-02 13:52:13,403 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-09-02 13:52:13,403 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-09-02 13:52:13,762 INFO RPC interface 'supervisor' initialized
|
||||
2025-09-02 13:52:13,762 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-09-02 13:52:13,763 INFO supervisord started with pid 1
|
||||
2025-09-02 13:52:14,789 INFO spawned: 'mesh' with pid 17
|
||||
2025-09-02 13:52:14,829 INFO spawned: 'report' with pid 18
|
||||
2025-09-02 13:52:14,874 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2025-09-02 13:52:15,929 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-09-02 13:52:15,929 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-09-02 13:52:15,929 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-09-14 11:46:00,778 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.
|
||||
2025-09-14 11:46:00,780 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-09-14 11:46:00,780 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-09-14 11:46:00,780 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-09-14 11:46:01,110 INFO RPC interface 'supervisor' initialized
|
||||
2025-09-14 11:46:01,110 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-09-14 11:46:01,110 INFO supervisord started with pid 1
|
||||
2025-09-14 11:46:02,123 INFO spawned: 'mesh' with pid 16
|
||||
2025-09-14 11:46:02,164 INFO spawned: 'report' with pid 17
|
||||
2025-09-14 11:46:02,258 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2025-09-14 11:46:03,319 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-09-14 11:46:03,319 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-09-14 11:46:03,319 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-20 16:49:45,239 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.
|
||||
2025-10-20 16:49:45,248 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-10-20 16:49:45,250 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-10-20 16:49:45,250 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-10-20 16:49:45,620 INFO RPC interface 'supervisor' initialized
|
||||
2025-10-20 16:49:45,620 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-10-20 16:49:45,621 INFO supervisord started with pid 1
|
||||
2025-10-20 16:49:46,629 INFO spawned: 'mesh' with pid 23
|
||||
2025-10-20 16:49:46,695 INFO spawned: 'report' with pid 24
|
||||
2025-10-20 16:49:46,766 INFO spawned: 'taskmgr_worker' with pid 25
|
||||
2025-10-20 16:49:47,788 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-20 16:49:47,788 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-20 16:49:47,788 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-21 16:46:09,127 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.
|
||||
2025-10-21 16:46:09,131 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-10-21 16:46:09,131 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-10-21 16:46:09,132 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-10-21 16:46:09,509 INFO RPC interface 'supervisor' initialized
|
||||
2025-10-21 16:46:09,509 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-10-21 16:46:09,510 INFO supervisord started with pid 1
|
||||
2025-10-21 16:46:10,513 INFO spawned: 'mesh' with pid 18
|
||||
2025-10-21 16:46:10,657 INFO spawned: 'report' with pid 20
|
||||
2025-10-21 16:46:10,772 INFO spawned: 'taskmgr_worker' with pid 21
|
||||
2025-10-21 16:46:11,834 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-21 16:46:11,834 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-21 16:46:11,834 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-30 10:40:51,130 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.
|
||||
2025-10-30 10:40:51,132 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-10-30 10:40:51,132 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-10-30 10:40:51,132 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-10-30 10:40:51,484 INFO RPC interface 'supervisor' initialized
|
||||
2025-10-30 10:40:51,484 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-10-30 10:40:51,500 INFO supervisord started with pid 1
|
||||
2025-10-30 10:40:52,508 INFO spawned: 'mesh' with pid 26
|
||||
2025-10-30 10:40:52,570 INFO spawned: 'report' with pid 27
|
||||
2025-10-30 10:40:52,689 INFO spawned: 'taskmgr_worker' with pid 28
|
||||
2025-10-30 10:40:53,700 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-30 10:40:53,700 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-10-30 10:40:53,701 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-05 09:21:56,193 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.
|
||||
2025-11-05 09:21:56,199 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-05 09:21:56,199 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-05 09:21:56,199 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-05 09:21:56,573 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-05 09:21:56,573 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-05 09:21:56,573 INFO supervisord started with pid 1
|
||||
2025-11-05 09:21:57,580 INFO spawned: 'mesh' with pid 29
|
||||
2025-11-05 09:21:57,662 INFO spawned: 'report' with pid 30
|
||||
2025-11-05 09:21:57,815 INFO spawned: 'taskmgr_worker' with pid 32
|
||||
2025-11-05 09:21:58,859 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-05 09:21:58,859 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-05 09:21:58,859 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:43:04,666 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.
|
||||
2025-11-12 08:43:04,672 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:43:04,672 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-12 08:43:04,672 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-12 08:43:05,023 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:43:05,023 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:43:05,024 INFO supervisord started with pid 1
|
||||
2025-11-12 08:43:06,043 INFO spawned: 'mesh' with pid 23
|
||||
2025-11-12 08:43:06,142 INFO spawned: 'report' with pid 24
|
||||
2025-11-12 08:43:06,190 INFO spawned: 'taskmgr_worker' with pid 26
|
||||
2025-11-12 08:43:07,236 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:43:07,236 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:43:07,241 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:24,901 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.
|
||||
2025-11-17 12:01:24,927 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:24,927 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-17 12:01:24,927 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-17 12:01:25,306 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:25,306 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:25,306 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:26,326 INFO spawned: 'mesh' with pid 20
|
||||
2025-11-17 12:01:26,370 INFO spawned: 'report' with pid 21
|
||||
2025-11-17 12:01:26,467 INFO spawned: 'taskmgr_worker' with pid 22
|
||||
2025-11-17 12:01:27,527 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:27,528 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:27,528 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:36,033 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.
|
||||
2025-11-21 15:30:36,040 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:36,040 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-21 15:30:36,040 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-21 15:30:36,373 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:36,373 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:36,373 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:37,402 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-21 15:30:37,505 INFO spawned: 'report' with pid 27
|
||||
2025-11-21 15:30:37,528 INFO spawned: 'taskmgr_worker' with pid 28
|
||||
2025-11-21 15:30:38,545 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,545 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:38,545 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,029 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.
|
||||
2025-11-22 15:19:49,063 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:49,063 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-22 15:19:49,063 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:19:49,458 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:49,468 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:49,468 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:50,474 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:19:50,513 INFO spawned: 'report' with pid 18
|
||||
2025-11-22 15:19:50,580 INFO spawned: 'taskmgr_worker' with pid 20
|
||||
2025-11-22 15:19:51,617 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,617 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,617 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:00,245 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:28:00,253 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-11-22 15:28:00,271 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:28:00,355 INFO stopped: report (exit status 0)
|
||||
2025-11-22 15:28:00,407 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:26,935 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.
|
||||
2025-11-22 15:28:26,935 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:26,935 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-22 15:28:26,935 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:28:26,987 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:26,987 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:26,987 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:28,007 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:28:28,075 INFO spawned: 'report' with pid 18
|
||||
2025-11-22 15:28:28,247 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2025-11-22 15:28:29,250 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:29,250 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:29,250 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:49,480 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:49,493 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-11-22 15:30:49,513 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:30:49,559 INFO stopped: report (exit status 0)
|
||||
2025-11-22 15:30:49,609 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:14,071 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.
|
||||
2025-11-22 15:31:14,071 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:14,071 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-22 15:31:14,071 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:31:14,089 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:14,089 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:14,090 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:15,092 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:31:15,141 INFO spawned: 'report' with pid 18
|
||||
2025-11-22 15:31:15,172 INFO spawned: 'taskmgr_worker' with pid 22
|
||||
2025-11-22 15:31:16,181 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,181 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:16,181 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:45,678 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:45,684 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-11-22 15:37:45,709 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:37:45,842 INFO stopped: report (exit status 0)
|
||||
2025-11-22 15:37:45,884 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:27,278 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.
|
||||
2025-11-22 15:38:27,278 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:27,278 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-22 15:38:27,278 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:38:27,339 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:27,339 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:27,339 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:28,352 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:38:28,410 INFO spawned: 'report' with pid 18
|
||||
2025-11-22 15:38:28,473 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2025-11-22 15:38:29,474 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:29,474 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:29,474 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:24,624 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.
|
||||
2025-11-25 15:48:24,633 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:24,633 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-11-25 15:48:24,633 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-25 15:48:24,970 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:24,970 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:24,971 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:25,977 INFO spawned: 'mesh' with pid 20
|
||||
2025-11-25 15:48:26,011 INFO spawned: 'report' with pid 21
|
||||
2025-11-25 15:48:26,054 INFO spawned: 'taskmgr_worker' with pid 22
|
||||
2025-11-25 15:48:27,057 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,057 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,057 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:23,497 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.
|
||||
2025-12-07 15:52:23,503 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:23,503 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-12-07 15:52:23,503 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-07 15:52:23,841 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:23,878 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:23,878 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:24,894 INFO spawned: 'mesh' with pid 25
|
||||
2025-12-07 15:52:24,935 INFO spawned: 'report' with pid 26
|
||||
2025-12-07 15:52:24,979 INFO spawned: 'taskmgr_worker' with pid 27
|
||||
2025-12-07 15:52:26,015 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,015 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,016 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:41,069 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.
|
||||
2025-12-08 11:39:41,075 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:41,075 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-12-08 11:39:41,075 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-08 11:39:41,431 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:41,433 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:41,436 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:42,493 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-08 11:39:42,512 INFO spawned: 'report' with pid 18
|
||||
2025-12-08 11:39:42,618 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2025-12-08 11:39:43,661 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,661 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,661 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,646 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.
|
||||
2025-12-11 15:42:42,653 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:42,653 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-12-11 15:42:42,653 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-11 15:42:42,993 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:42,993 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:42,999 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:44,003 INFO spawned: 'mesh' with pid 22
|
||||
2025-12-11 15:42:44,082 INFO spawned: 'report' with pid 23
|
||||
2025-12-11 15:42:44,142 INFO spawned: 'taskmgr_worker' with pid 24
|
||||
2025-12-11 15:42:45,194 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,194 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:45,194 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:25,050 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.
|
||||
2025-12-14 06:18:25,062 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,062 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-12-14 06:18:25,062 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-14 06:18:25,425 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:25,425 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:25,425 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:26,433 INFO spawned: 'mesh' with pid 23
|
||||
2025-12-14 06:18:26,488 INFO spawned: 'report' with pid 24
|
||||
2025-12-14 06:18:26,534 INFO spawned: 'taskmgr_worker' with pid 25
|
||||
2025-12-14 06:18:27,581 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,581 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,581 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:31,952 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.
|
||||
2025-12-15 18:35:31,955 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:31,955 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-12-15 18:35:31,955 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-15 18:35:32,346 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:32,346 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:32,346 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:33,368 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-15 18:35:33,486 INFO spawned: 'report' with pid 18
|
||||
2025-12-15 18:35:33,583 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2025-12-15 18:35:34,657 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,657 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,657 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:00,381 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.
|
||||
2025-12-18 15:23:00,394 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:00,394 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2025-12-18 15:23:00,394 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-18 15:23:00,770 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:00,770 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:00,770 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:01,791 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-18 15:23:01,813 INFO spawned: 'report' with pid 18
|
||||
2025-12-18 15:23:01,863 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2025-12-18 15:23:02,892 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:02,892 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:02,892 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,835 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,876 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-12-18 20:53:22,901 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-12-18 20:53:25,907 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-12-18 20:53:28,912 INFO waiting for mesh, report, taskmgr_worker to die
|
||||
2025-12-18 20:53:29,913 WARN killing 'taskmgr_worker' (19) with SIGKILL
|
||||
2025-12-18 20:53:29,915 WARN stopped: taskmgr_worker (terminated by SIGKILL)
|
||||
2025-12-18 20:53:31,918 INFO waiting for mesh, report to die
|
||||
2026-01-25 19:02:19,595 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.
|
||||
2026-01-25 19:02:19,605 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:19,605 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-01-25 19:02:19,605 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-01-25 19:02:19,977 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:19,977 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:19,977 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:20,988 INFO spawned: 'mesh' with pid 19
|
||||
2026-01-25 19:02:21,087 INFO spawned: 'report' with pid 20
|
||||
2026-01-25 19:02:21,220 INFO spawned: 'taskmgr_worker' with pid 21
|
||||
2026-01-25 19:02:22,225 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,225 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,225 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:21,159 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.
|
||||
2026-02-04 12:30:21,161 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:21,161 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-02-04 12:30:21,161 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 12:30:21,481 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:21,489 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:21,491 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:22,494 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 12:30:22,509 INFO spawned: 'report' with pid 17
|
||||
2026-02-04 12:30:22,546 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2026-02-04 12:30:23,554 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,554 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,554 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,249 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.
|
||||
2026-02-04 14:57:35,282 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,282 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-02-04 14:57:35,282 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 14:57:35,692 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:35,692 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:35,692 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:36,708 INFO spawned: 'mesh' with pid 20
|
||||
2026-02-04 14:57:36,762 INFO spawned: 'report' with pid 21
|
||||
2026-02-04 14:57:36,821 INFO spawned: 'taskmgr_worker' with pid 23
|
||||
2026-02-04 14:57:37,880 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,880 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,880 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,302 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.
|
||||
2026-02-04 17:30:57,305 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:57,305 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-02-04 17:30:57,305 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 17:30:57,654 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:57,666 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:57,666 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:58,669 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 17:30:58,739 INFO spawned: 'report' with pid 18
|
||||
2026-02-04 17:30:58,796 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2026-02-04 17:30:59,838 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:59,838 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:59,838 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:20,451 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.
|
||||
2026-02-07 14:26:20,462 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:20,462 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-02-07 14:26:20,462 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-07 14:26:20,805 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,805 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,806 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,824 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-07 14:26:21,912 INFO spawned: 'report' with pid 18
|
||||
2026-02-07 14:26:21,997 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2026-02-07 14:26:23,021 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,021 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,021 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,557 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.
|
||||
2026-02-20 16:02:21,563 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:21,563 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-02-20 16:02:21,563 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-20 16:02:21,909 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,909 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,929 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,940 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-20 16:02:23,068 INFO spawned: 'report' with pid 18
|
||||
2026-02-20 16:02:23,108 INFO spawned: 'taskmgr_worker' with pid 20
|
||||
2026-02-20 16:02:24,142 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,142 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:24,144 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:30,998 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.
|
||||
2026-03-04 12:10:31,006 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,006 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-03-04 12:10:31,006 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-04 12:10:31,349 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,365 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,365 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,373 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-04 12:10:32,407 INFO spawned: 'report' with pid 24
|
||||
2026-03-04 12:10:32,505 INFO spawned: 'taskmgr_worker' with pid 25
|
||||
2026-03-04 12:10:33,546 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,546 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,546 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:44,727 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.
|
||||
2026-03-23 09:52:44,733 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,733 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-03-23 09:52:44,733 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-23 09:52:45,085 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:45,085 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:45,085 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:46,103 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-23 09:52:46,160 INFO spawned: 'report' with pid 24
|
||||
2026-03-23 09:52:46,250 INFO spawned: 'taskmgr_worker' with pid 25
|
||||
2026-03-23 09:52:47,297 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,297 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:47,297 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:13,093 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.
|
||||
2026-03-25 17:35:13,094 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:13,095 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-03-25 17:35:13,095 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-25 17:35:13,408 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:13,408 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:13,408 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:14,413 INFO spawned: 'mesh' with pid 16
|
||||
2026-03-25 17:35:14,466 INFO spawned: 'report' with pid 17
|
||||
2026-03-25 17:35:14,489 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2026-03-25 17:35:15,540 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:15,540 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:15,540 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:02,569 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.
|
||||
2026-03-26 07:04:02,588 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:02,588 INFO Included extra file "/opt/supervisor.d/report.conf" during parsing
|
||||
2026-03-26 07:04:02,588 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-26 07:04:02,979 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:02,979 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:02,979 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:03,990 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-26 07:04:04,036 INFO spawned: 'report' with pid 23
|
||||
2026-03-26 07:04:04,096 INFO spawned: 'taskmgr_worker' with pid 24
|
||||
2026-03-26 07:04:05,144 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,157 INFO success: report entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,157 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,998 @@
|
||||
2025-11-12 08:50:14,196 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.
|
||||
2025-11-12 08:50:14,198 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-11-12 08:50:14,198 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-11-12 08:50:14,198 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-11-12 08:50:14,198 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-11-12 08:50:14,198 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:14,198 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-11-12 08:50:14,216 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:14,216 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:14,221 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:15,237 INFO spawned: 'mesh' with pid 11
|
||||
2025-11-12 08:50:15,255 INFO spawned: 'cron' with pid 12
|
||||
2025-11-12 08:50:15,318 INFO spawned: 'cron_update_indexes' with pid 13
|
||||
2025-11-12 08:50:15,375 INFO spawned: 'db_connection_checker' with pid 14
|
||||
2025-11-12 08:50:15,474 INFO spawned: 'env' with pid 15
|
||||
2025-11-12 08:50:15,620 INFO spawned: 'search' with pid 19
|
||||
2025-11-12 08:50:15,637 INFO exited: cron (exit status 0; expected)
|
||||
2025-11-12 08:50:15,740 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:15,740 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:15,740 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:15,741 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:15,741 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:15,741 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-11-12 08:50:15,801 INFO exited: env (exit status 0; expected)
|
||||
2025-11-12 08:50:35,002 INFO reaped unknown pid 38 (exit status 0)
|
||||
2025-11-12 08:50:35,010 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-11-17 12:01:30,415 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.
|
||||
2025-11-17 12:01:30,437 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-11-17 12:01:30,437 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-11-17 12:01:30,437 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-11-17 12:01:30,437 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-11-17 12:01:30,437 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:30,437 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-11-17 12:01:30,789 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:30,789 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:30,790 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:31,823 INFO spawned: 'mesh' with pid 10
|
||||
2025-11-17 12:01:31,891 INFO spawned: 'cron' with pid 11
|
||||
2025-11-17 12:01:31,996 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2025-11-17 12:01:32,081 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2025-11-17 12:01:32,138 INFO spawned: 'env' with pid 15
|
||||
2025-11-17 12:01:32,196 INFO spawned: 'search' with pid 18
|
||||
2025-11-17 12:01:32,269 INFO exited: cron (exit status 0; expected)
|
||||
2025-11-17 12:01:32,446 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,483 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,483 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,483 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,483 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,484 INFO exited: env (exit status 0; expected)
|
||||
2025-11-17 12:01:32,550 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-11-17 12:01:47,396 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-11-17 12:01:47,398 INFO reaped unknown pid 37 (exit status 0)
|
||||
2025-11-21 15:30:31,780 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.
|
||||
2025-11-21 15:30:31,797 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-11-21 15:30:31,797 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-11-21 15:30:31,797 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-11-21 15:30:31,797 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-11-21 15:30:31,797 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:31,797 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-11-21 15:30:32,123 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:32,133 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:32,133 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:33,160 INFO spawned: 'mesh' with pid 10
|
||||
2025-11-21 15:30:33,230 INFO spawned: 'cron' with pid 11
|
||||
2025-11-21 15:30:33,304 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2025-11-21 15:30:33,311 INFO spawned: 'db_connection_checker' with pid 16
|
||||
2025-11-21 15:30:33,323 INFO spawned: 'env' with pid 17
|
||||
2025-11-21 15:30:33,335 INFO spawned: 'search' with pid 18
|
||||
2025-11-21 15:30:33,424 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:33,424 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:33,424 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:33,424 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:33,424 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:33,424 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:33,424 INFO exited: cron (exit status 0; expected)
|
||||
2025-11-21 15:30:33,447 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-11-21 15:30:33,680 INFO exited: env (exit status 0; expected)
|
||||
2025-11-21 15:30:51,502 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-11-21 15:30:51,503 INFO reaped unknown pid 37 (exit status 0)
|
||||
2025-11-22 15:19:48,300 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.
|
||||
2025-11-22 15:19:48,301 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-11-22 15:19:48,301 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-11-22 15:19:48,302 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-11-22 15:19:48,302 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-11-22 15:19:48,302 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:48,302 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-11-22 15:19:48,662 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:48,663 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:48,663 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:49,694 INFO spawned: 'mesh' with pid 10
|
||||
2025-11-22 15:19:49,769 INFO spawned: 'cron' with pid 11
|
||||
2025-11-22 15:19:49,891 INFO spawned: 'cron_update_indexes' with pid 13
|
||||
2025-11-22 15:19:50,026 INFO spawned: 'db_connection_checker' with pid 15
|
||||
2025-11-22 15:19:50,138 INFO spawned: 'env' with pid 16
|
||||
2025-11-22 15:19:50,242 INFO spawned: 'search' with pid 17
|
||||
2025-11-22 15:19:50,360 INFO exited: cron (exit status 0; expected)
|
||||
2025-11-22 15:19:50,400 INFO exited: env (exit status 0; expected)
|
||||
2025-11-22 15:19:50,529 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:50,529 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:50,529 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:50,529 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:50,529 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-11-22 15:20:10,067 INFO reaped unknown pid 43 (exit status 0)
|
||||
2025-11-22 15:20:10,068 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-11-22 15:27:57,629 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:57,634 INFO waiting for mesh, search to die
|
||||
2025-11-22 15:27:58,276 INFO stopped: search (exit status 0)
|
||||
2025-11-22 15:28:01,282 INFO waiting for mesh to die
|
||||
2025-11-22 15:28:02,305 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:28,652 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.
|
||||
2025-11-22 15:28:28,675 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-11-22 15:28:28,675 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-11-22 15:28:28,676 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-11-22 15:28:28,676 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-11-22 15:28:28,676 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:28,676 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-11-22 15:28:28,701 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:28,728 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:28,728 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:29,734 INFO spawned: 'mesh' with pid 9
|
||||
2025-11-22 15:28:29,766 INFO spawned: 'cron' with pid 10
|
||||
2025-11-22 15:28:29,828 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2025-11-22 15:28:29,867 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2025-11-22 15:28:29,941 INFO spawned: 'env' with pid 15
|
||||
2025-11-22 15:28:29,981 INFO spawned: 'search' with pid 18
|
||||
2025-11-22 15:28:29,982 INFO exited: cron (exit status 0; expected)
|
||||
2025-11-22 15:28:30,073 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:30,073 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:30,073 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:30,073 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:30,074 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:30,074 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-11-22 15:28:30,116 INFO exited: env (exit status 0; expected)
|
||||
2025-11-22 15:28:46,225 INFO reaped unknown pid 36 (exit status 0)
|
||||
2025-11-22 15:28:46,231 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-11-22 15:30:46,394 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,396 INFO waiting for mesh, search to die
|
||||
2025-11-22 15:30:46,613 INFO stopped: search (exit status 0)
|
||||
2025-11-22 15:30:49,617 INFO waiting for mesh to die
|
||||
2025-11-22 15:30:50,723 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:18,132 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.
|
||||
2025-11-22 15:31:18,137 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-11-22 15:31:18,137 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-11-22 15:31:18,137 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-11-22 15:31:18,137 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-11-22 15:31:18,137 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:18,137 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-11-22 15:31:18,156 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:18,156 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:18,156 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:19,167 INFO spawned: 'mesh' with pid 11
|
||||
2025-11-22 15:31:19,214 INFO spawned: 'cron' with pid 12
|
||||
2025-11-22 15:31:19,277 INFO spawned: 'cron_update_indexes' with pid 14
|
||||
2025-11-22 15:31:19,340 INFO spawned: 'db_connection_checker' with pid 17
|
||||
2025-11-22 15:31:19,424 INFO spawned: 'env' with pid 18
|
||||
2025-11-22 15:31:19,560 INFO spawned: 'search' with pid 23
|
||||
2025-11-22 15:31:19,580 INFO exited: cron (exit status 0; expected)
|
||||
2025-11-22 15:31:19,637 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,638 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,638 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,638 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,638 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,638 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-11-22 15:31:19,741 INFO exited: env (exit status 0; expected)
|
||||
2025-11-22 15:31:36,177 INFO reaped unknown pid 38 (exit status 0)
|
||||
2025-11-22 15:31:36,179 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-11-22 15:37:42,625 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:42,627 INFO waiting for mesh, search to die
|
||||
2025-11-22 15:37:42,821 INFO stopped: search (exit status 0)
|
||||
2025-11-22 15:37:45,825 INFO waiting for mesh to die
|
||||
2025-11-22 15:37:46,931 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:25,289 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.
|
||||
2025-11-22 15:38:25,303 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-11-22 15:38:25,303 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-11-22 15:38:25,303 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-11-22 15:38:25,303 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-11-22 15:38:25,303 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:25,303 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-11-22 15:38:25,329 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:25,350 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:25,350 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:26,358 INFO spawned: 'mesh' with pid 9
|
||||
2025-11-22 15:38:26,419 INFO spawned: 'cron' with pid 10
|
||||
2025-11-22 15:38:26,556 INFO spawned: 'cron_update_indexes' with pid 11
|
||||
2025-11-22 15:38:26,630 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2025-11-22 15:38:26,758 INFO spawned: 'env' with pid 17
|
||||
2025-11-22 15:38:26,850 INFO spawned: 'search' with pid 20
|
||||
2025-11-22 15:38:26,929 INFO exited: cron (exit status 0; expected)
|
||||
2025-11-22 15:38:26,998 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,999 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,999 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,999 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,999 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,999 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-11-22 15:38:27,068 INFO exited: env (exit status 0; expected)
|
||||
2025-11-22 15:38:44,162 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-11-22 15:38:44,163 INFO reaped unknown pid 36 (exit status 0)
|
||||
2025-11-25 15:48:31,955 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.
|
||||
2025-11-25 15:48:31,973 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-11-25 15:48:31,973 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-11-25 15:48:31,973 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-11-25 15:48:31,973 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-11-25 15:48:31,973 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:31,973 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-11-25 15:48:32,300 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:32,321 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:32,322 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:33,335 INFO spawned: 'mesh' with pid 10
|
||||
2025-11-25 15:48:33,386 INFO spawned: 'cron' with pid 11
|
||||
2025-11-25 15:48:33,484 INFO spawned: 'cron_update_indexes' with pid 13
|
||||
2025-11-25 15:48:33,589 INFO spawned: 'db_connection_checker' with pid 16
|
||||
2025-11-25 15:48:33,725 INFO spawned: 'env' with pid 18
|
||||
2025-11-25 15:48:33,812 INFO spawned: 'search' with pid 19
|
||||
2025-11-25 15:48:33,964 INFO exited: cron (exit status 0; expected)
|
||||
2025-11-25 15:48:33,965 INFO exited: env (exit status 0; expected)
|
||||
2025-11-25 15:48:34,042 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:34,042 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:34,042 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:34,042 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:34,042 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-11-25 15:48:50,581 INFO reaped unknown pid 37 (exit status 0)
|
||||
2025-11-25 15:48:50,586 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-12-07 15:52:20,778 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.
|
||||
2025-12-07 15:52:20,801 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-12-07 15:52:20,801 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-12-07 15:52:20,801 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-12-07 15:52:20,801 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-12-07 15:52:20,801 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:20,801 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-12-07 15:52:21,154 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:21,154 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:21,154 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:22,171 INFO spawned: 'mesh' with pid 10
|
||||
2025-12-07 15:52:22,266 INFO spawned: 'cron' with pid 11
|
||||
2025-12-07 15:52:22,340 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2025-12-07 15:52:22,535 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2025-12-07 15:52:22,655 INFO spawned: 'env' with pid 16
|
||||
2025-12-07 15:52:22,844 INFO spawned: 'search' with pid 19
|
||||
2025-12-07 15:52:22,912 INFO exited: cron (exit status 0; expected)
|
||||
2025-12-07 15:52:23,068 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-12-07 15:52:23,069 INFO exited: env (exit status 0; expected)
|
||||
2025-12-07 15:52:24,074 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:24,074 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:24,074 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:42,910 INFO reaped unknown pid 37 (exit status 0)
|
||||
2025-12-07 15:52:42,912 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-12-08 11:39:40,886 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.
|
||||
2025-12-08 11:39:40,903 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-12-08 11:39:40,903 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-12-08 11:39:40,903 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-12-08 11:39:40,903 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-12-08 11:39:40,903 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:40,903 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-12-08 11:39:41,228 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:41,228 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:41,228 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:42,252 INFO spawned: 'mesh' with pid 10
|
||||
2025-12-08 11:39:42,326 INFO spawned: 'cron' with pid 11
|
||||
2025-12-08 11:39:42,403 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2025-12-08 11:39:42,531 INFO spawned: 'db_connection_checker' with pid 14
|
||||
2025-12-08 11:39:42,643 INFO spawned: 'env' with pid 16
|
||||
2025-12-08 11:39:42,744 INFO spawned: 'search' with pid 20
|
||||
2025-12-08 11:39:42,854 INFO exited: cron (exit status 0; expected)
|
||||
2025-12-08 11:39:43,004 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,004 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,004 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,004 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,004 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,004 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-12-08 11:39:43,004 INFO exited: env (exit status 0; expected)
|
||||
2025-12-08 11:39:58,986 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-12-08 11:39:58,992 INFO reaped unknown pid 37 (exit status 0)
|
||||
2025-12-11 15:42:40,788 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.
|
||||
2025-12-11 15:42:40,802 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-12-11 15:42:40,802 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-12-11 15:42:40,802 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-12-11 15:42:40,802 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-12-11 15:42:40,802 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:40,802 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-12-11 15:42:41,148 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:41,175 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:41,175 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:42,202 INFO spawned: 'mesh' with pid 10
|
||||
2025-12-11 15:42:42,345 INFO spawned: 'cron' with pid 11
|
||||
2025-12-11 15:42:42,385 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2025-12-11 15:42:42,497 INFO spawned: 'db_connection_checker' with pid 14
|
||||
2025-12-11 15:42:42,602 INFO spawned: 'env' with pid 15
|
||||
2025-12-11 15:42:42,676 INFO spawned: 'search' with pid 16
|
||||
2025-12-11 15:42:42,738 INFO exited: cron (exit status 0; expected)
|
||||
2025-12-11 15:42:42,838 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,838 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,838 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,838 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,838 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,839 INFO exited: env (exit status 0; expected)
|
||||
2025-12-11 15:42:42,943 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-12-11 15:43:00,451 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-12-11 15:43:00,453 INFO reaped unknown pid 37 (exit status 0)
|
||||
2025-12-14 06:18:25,809 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.
|
||||
2025-12-14 06:18:25,840 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-12-14 06:18:25,840 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-12-14 06:18:25,840 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-12-14 06:18:25,840 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-12-14 06:18:25,840 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,840 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-12-14 06:18:26,170 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:26,173 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:26,173 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:27,188 INFO spawned: 'mesh' with pid 10
|
||||
2025-12-14 06:18:27,286 INFO spawned: 'cron' with pid 11
|
||||
2025-12-14 06:18:27,355 INFO spawned: 'cron_update_indexes' with pid 13
|
||||
2025-12-14 06:18:27,455 INFO spawned: 'db_connection_checker' with pid 14
|
||||
2025-12-14 06:18:27,512 INFO spawned: 'env' with pid 15
|
||||
2025-12-14 06:18:27,592 INFO spawned: 'search' with pid 16
|
||||
2025-12-14 06:18:27,726 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,726 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,726 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,726 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,726 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,726 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,726 INFO exited: cron (exit status 0; expected)
|
||||
2025-12-14 06:18:27,875 INFO exited: env (exit status 0; expected)
|
||||
2025-12-14 06:18:27,912 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-12-14 06:18:46,452 INFO reaped unknown pid 37 (exit status 0)
|
||||
2025-12-14 06:18:46,457 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-12-15 18:35:24,037 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.
|
||||
2025-12-15 18:35:24,040 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-12-15 18:35:24,040 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-12-15 18:35:24,040 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-12-15 18:35:24,040 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-12-15 18:35:24,040 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:24,040 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-12-15 18:35:24,349 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:24,349 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:24,349 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:25,357 INFO spawned: 'mesh' with pid 10
|
||||
2025-12-15 18:35:25,391 INFO spawned: 'cron' with pid 11
|
||||
2025-12-15 18:35:25,447 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2025-12-15 18:35:25,498 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2025-12-15 18:35:25,558 INFO spawned: 'env' with pid 15
|
||||
2025-12-15 18:35:25,621 INFO spawned: 'search' with pid 18
|
||||
2025-12-15 18:35:25,622 INFO exited: cron (exit status 0; expected)
|
||||
2025-12-15 18:35:25,697 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:25,697 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:25,701 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:25,701 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:25,701 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:25,701 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-12-15 18:35:25,706 INFO exited: env (exit status 0; expected)
|
||||
2025-12-15 18:35:25,813 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:25,971 INFO spawned: 'mesh' with pid 23
|
||||
2025-12-15 18:35:25,991 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:25,993 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,016 INFO spawned: 'search' with pid 24
|
||||
2025-12-15 18:35:26,127 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,132 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:26,167 INFO spawned: 'mesh' with pid 27
|
||||
2025-12-15 18:35:26,173 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:26,174 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,187 INFO spawned: 'search' with pid 28
|
||||
2025-12-15 18:35:26,306 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,306 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:26,348 INFO spawned: 'mesh' with pid 31
|
||||
2025-12-15 18:35:26,356 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:26,356 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,377 INFO spawned: 'search' with pid 32
|
||||
2025-12-15 18:35:26,471 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,471 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:26,506 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-15 18:35:26,517 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:26,526 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,536 INFO spawned: 'search' with pid 36
|
||||
2025-12-15 18:35:26,646 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,791 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:26,791 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:26,792 INFO spawned: 'mesh' with pid 39
|
||||
2025-12-15 18:35:26,825 INFO spawned: 'search' with pid 40
|
||||
2025-12-15 18:35:26,993 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,999 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:26,999 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:27,066 INFO spawned: 'mesh' with pid 43
|
||||
2025-12-15 18:35:27,078 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:27,081 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:27,102 INFO spawned: 'search' with pid 44
|
||||
2025-12-15 18:35:27,265 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:27,265 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:27,324 INFO spawned: 'mesh' with pid 47
|
||||
2025-12-15 18:35:27,329 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:27,337 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:27,359 INFO spawned: 'search' with pid 48
|
||||
2025-12-15 18:35:27,472 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:27,479 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:27,534 INFO spawned: 'mesh' with pid 51
|
||||
2025-12-15 18:35:27,550 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:27,550 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:27,593 INFO spawned: 'search' with pid 52
|
||||
2025-12-15 18:35:27,797 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:27,797 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:27,997 INFO spawned: 'mesh' with pid 55
|
||||
2025-12-15 18:35:28,011 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:28,011 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:28,036 INFO spawned: 'search' with pid 56
|
||||
2025-12-15 18:35:28,424 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:28,428 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:28,465 INFO spawned: 'mesh' with pid 59
|
||||
2025-12-15 18:35:28,492 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-15 18:35:28,499 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:28,533 INFO spawned: 'search' with pid 60
|
||||
2025-12-15 18:35:28,755 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:28,769 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:29,778 INFO spawned: 'mesh' with pid 64
|
||||
2025-12-15 18:35:30,796 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:35,011 WARN exited: db_connection_checker (exit status 1; not expected)
|
||||
2025-12-15 18:35:36,013 INFO spawned: 'db_connection_checker' with pid 75
|
||||
2025-12-15 18:35:37,065 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:52,935 INFO reaped unknown pid 87 (exit status 0)
|
||||
2025-12-15 18:35:52,942 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-12-18 15:22:53,399 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.
|
||||
2025-12-18 15:22:53,409 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2025-12-18 15:22:53,409 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2025-12-18 15:22:53,409 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2025-12-18 15:22:53,409 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2025-12-18 15:22:53,409 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:53,409 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2025-12-18 15:22:53,738 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:53,738 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:53,739 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:54,747 INFO spawned: 'mesh' with pid 9
|
||||
2025-12-18 15:22:54,779 INFO spawned: 'cron' with pid 10
|
||||
2025-12-18 15:22:54,818 INFO spawned: 'cron_update_indexes' with pid 11
|
||||
2025-12-18 15:22:54,872 INFO spawned: 'db_connection_checker' with pid 12
|
||||
2025-12-18 15:22:54,918 INFO spawned: 'env' with pid 16
|
||||
2025-12-18 15:22:54,982 INFO spawned: 'search' with pid 18
|
||||
2025-12-18 15:22:55,028 INFO exited: cron (exit status 0; expected)
|
||||
2025-12-18 15:22:55,065 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:55,065 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:55,065 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:55,065 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:55,065 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:55,065 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2025-12-18 15:22:55,109 INFO exited: env (exit status 0; expected)
|
||||
2025-12-18 15:23:02,043 WARN exited: db_connection_checker (exit status 1; not expected)
|
||||
2025-12-18 15:23:03,078 INFO spawned: 'db_connection_checker' with pid 32
|
||||
2025-12-18 15:23:04,085 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:18,676 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2025-12-18 15:23:18,677 INFO reaped unknown pid 44 (exit status 0)
|
||||
2025-12-18 20:53:13,618 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:13,674 INFO spawned: 'mesh' with pid 664
|
||||
2025-12-18 20:53:13,703 WARN exited: search (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:13,871 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,919 INFO spawned: 'search' with pid 666
|
||||
2025-12-18 20:53:13,934 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,024 INFO spawned: 'mesh' with pid 667
|
||||
2025-12-18 20:53:14,024 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,504 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,505 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,680 INFO spawned: 'mesh' with pid 670
|
||||
2025-12-18 20:53:14,681 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,682 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,740 INFO spawned: 'search' with pid 671
|
||||
2025-12-18 20:53:15,029 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,030 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,117 INFO spawned: 'mesh' with pid 674
|
||||
2025-12-18 20:53:15,128 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,129 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,168 INFO spawned: 'search' with pid 675
|
||||
2025-12-18 20:53:15,447 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,502 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,503 INFO spawned: 'mesh' with pid 678
|
||||
2025-12-18 20:53:15,533 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,548 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,581 INFO spawned: 'search' with pid 679
|
||||
2025-12-18 20:53:15,800 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,801 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,893 INFO spawned: 'mesh' with pid 682
|
||||
2025-12-18 20:53:15,894 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,894 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,926 INFO spawned: 'search' with pid 683
|
||||
2025-12-18 20:53:16,175 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,188 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,257 INFO spawned: 'mesh' with pid 686
|
||||
2025-12-18 20:53:16,272 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,272 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,305 INFO spawned: 'search' with pid 687
|
||||
2025-12-18 20:53:16,392 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,392 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,567 INFO spawned: 'mesh' with pid 690
|
||||
2025-12-18 20:53:16,570 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,576 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,615 INFO spawned: 'search' with pid 691
|
||||
2025-12-18 20:53:16,812 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,825 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,903 INFO spawned: 'mesh' with pid 694
|
||||
2025-12-18 20:53:16,914 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,936 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,979 INFO spawned: 'search' with pid 695
|
||||
2025-12-18 20:53:17,173 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,174 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,232 INFO spawned: 'mesh' with pid 698
|
||||
2025-12-18 20:53:17,265 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,266 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,272 INFO spawned: 'search' with pid 700
|
||||
2025-12-18 20:53:17,415 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,429 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,511 INFO spawned: 'mesh' with pid 702
|
||||
2025-12-18 20:53:17,541 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,541 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,568 INFO spawned: 'search' with pid 703
|
||||
2025-12-18 20:53:17,759 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,763 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,838 INFO spawned: 'mesh' with pid 706
|
||||
2025-12-18 20:53:17,861 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,862 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,907 INFO spawned: 'search' with pid 707
|
||||
2025-12-18 20:53:18,152 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,162 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,211 INFO spawned: 'mesh' with pid 710
|
||||
2025-12-18 20:53:18,236 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,237 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,273 INFO spawned: 'search' with pid 711
|
||||
2025-12-18 20:53:18,451 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,456 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,512 INFO spawned: 'mesh' with pid 714
|
||||
2025-12-18 20:53:18,715 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,715 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,775 INFO spawned: 'search' with pid 716
|
||||
2025-12-18 20:53:18,797 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,809 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,006 INFO spawned: 'mesh' with pid 718
|
||||
2025-12-18 20:53:19,029 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,053 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,114 INFO spawned: 'search' with pid 719
|
||||
2025-12-18 20:53:19,427 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,428 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,435 WARN exited: search (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,474 INFO spawned: 'mesh' with pid 722
|
||||
2025-12-18 20:53:19,522 INFO spawned: 'search' with pid 723
|
||||
2025-12-18 20:53:19,735 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,736 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,736 INFO reaped unknown pid 13 (terminated by SIGTERM)
|
||||
2025-12-18 20:53:19,736 WARN exited: search (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,736 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,736 INFO waiting for mesh to die
|
||||
2025-12-18 20:53:19,798 INFO reaped unknown pid 45 (exit status 0)
|
||||
2025-12-18 20:53:19,798 WARN exited: mesh (terminated by SIGTERM; not expected)
|
||||
2026-01-25 19:02:12,747 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.
|
||||
2026-01-25 19:02:12,748 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-01-25 19:02:12,748 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-01-25 19:02:12,748 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-01-25 19:02:12,748 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-01-25 19:02:12,748 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:12,748 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-01-25 19:02:12,758 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:12,758 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:12,759 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:13,774 INFO spawned: 'mesh' with pid 10
|
||||
2026-01-25 19:02:13,800 INFO spawned: 'cron' with pid 11
|
||||
2026-01-25 19:02:13,825 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2026-01-25 19:02:13,853 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2026-01-25 19:02:13,888 INFO spawned: 'env' with pid 14
|
||||
2026-01-25 19:02:13,939 INFO spawned: 'search' with pid 16
|
||||
2026-01-25 19:02:13,959 INFO exited: cron (exit status 0; expected)
|
||||
2026-01-25 19:02:14,011 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,012 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,012 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,012 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,013 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,013 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-01-25 19:02:14,025 INFO exited: env (exit status 0; expected)
|
||||
2026-01-25 19:02:14,247 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:14,259 INFO spawned: 'mesh' with pid 23
|
||||
2026-01-25 19:02:14,259 WARN exited: search (exit status 1; not expected)
|
||||
2026-01-25 19:02:14,386 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,394 INFO spawned: 'search' with pid 25
|
||||
2026-01-25 19:02:14,407 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:14,440 INFO spawned: 'mesh' with pid 26
|
||||
2026-01-25 19:02:14,440 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,580 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,580 WARN exited: search (exit status 1; not expected)
|
||||
2026-01-25 19:02:14,588 INFO spawned: 'search' with pid 29
|
||||
2026-01-25 19:02:14,599 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:14,614 INFO spawned: 'mesh' with pid 30
|
||||
2026-01-25 19:02:14,615 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,727 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,728 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:14,801 INFO spawned: 'mesh' with pid 33
|
||||
2026-01-25 19:02:14,814 WARN exited: search (exit status 1; not expected)
|
||||
2026-01-25 19:02:14,823 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:14,845 INFO spawned: 'search' with pid 34
|
||||
2026-01-25 19:02:14,938 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:15,014 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:15,015 WARN exited: search (exit status 1; not expected)
|
||||
2026-01-25 19:02:15,016 INFO spawned: 'mesh' with pid 37
|
||||
2026-01-25 19:02:15,044 INFO spawned: 'search' with pid 38
|
||||
2026-01-25 19:02:15,208 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:15,208 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:15,208 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:15,208 WARN exited: search (exit status 1; not expected)
|
||||
2026-01-25 19:02:15,227 INFO spawned: 'mesh' with pid 41
|
||||
2026-01-25 19:02:15,279 INFO spawned: 'search' with pid 42
|
||||
2026-01-25 19:02:15,469 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:15,469 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:15,469 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:15,495 INFO spawned: 'mesh' with pid 45
|
||||
2026-01-25 19:02:15,514 WARN exited: search (exit status 1; not expected)
|
||||
2026-01-25 19:02:15,519 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:15,544 INFO spawned: 'search' with pid 46
|
||||
2026-01-25 19:02:15,669 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:15,669 INFO exited: mesh (exit status 0; expected)
|
||||
2026-01-25 19:02:15,783 INFO spawned: 'mesh' with pid 49
|
||||
2026-01-25 19:02:15,783 WARN exited: search (exit status 1; not expected)
|
||||
2026-01-25 19:02:15,796 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:15,803 INFO spawned: 'search' with pid 50
|
||||
2026-01-25 19:02:16,834 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:34,917 INFO reaped unknown pid 67 (exit status 0)
|
||||
2026-01-25 19:02:34,918 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-02-04 12:30:24,574 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.
|
||||
2026-02-04 12:30:24,576 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-02-04 12:30:24,576 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-02-04 12:30:24,576 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-02-04 12:30:24,576 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-02-04 12:30:24,576 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:24,576 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-02-04 12:30:24,896 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:24,896 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:24,898 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:25,910 INFO spawned: 'mesh' with pid 10
|
||||
2026-02-04 12:30:25,932 INFO spawned: 'cron' with pid 11
|
||||
2026-02-04 12:30:25,994 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2026-02-04 12:30:26,058 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2026-02-04 12:30:26,119 INFO spawned: 'env' with pid 16
|
||||
2026-02-04 12:30:26,212 INFO spawned: 'search' with pid 20
|
||||
2026-02-04 12:30:26,250 INFO exited: cron (exit status 0; expected)
|
||||
2026-02-04 12:30:26,285 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-02-04 12:30:26,403 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:26,403 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:26,403 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:26,403 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:26,403 INFO exited: env (exit status 0; expected)
|
||||
2026-02-04 12:30:34,266 WARN exited: db_connection_checker (exit status 1; not expected)
|
||||
2026-02-04 12:30:35,275 INFO spawned: 'db_connection_checker' with pid 33
|
||||
2026-02-04 12:30:36,324 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:54,503 INFO reaped unknown pid 45 (exit status 0)
|
||||
2026-02-04 12:30:54,516 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-02-04 14:57:35,802 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.
|
||||
2026-02-04 14:57:35,836 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-02-04 14:57:35,836 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-02-04 14:57:35,836 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-02-04 14:57:35,836 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-02-04 14:57:35,836 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,836 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-02-04 14:57:36,170 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,170 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,170 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,184 INFO spawned: 'mesh' with pid 10
|
||||
2026-02-04 14:57:37,259 INFO spawned: 'cron' with pid 11
|
||||
2026-02-04 14:57:37,306 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2026-02-04 14:57:37,380 INFO spawned: 'db_connection_checker' with pid 14
|
||||
2026-02-04 14:57:37,455 INFO spawned: 'env' with pid 16
|
||||
2026-02-04 14:57:37,596 INFO spawned: 'search' with pid 20
|
||||
2026-02-04 14:57:37,597 INFO exited: cron (exit status 0; expected)
|
||||
2026-02-04 14:57:37,675 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,675 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,675 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,675 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,675 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,675 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-02-04 14:57:37,775 INFO exited: env (exit status 0; expected)
|
||||
2026-02-04 14:57:56,548 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-02-04 14:57:56,549 INFO reaped unknown pid 37 (exit status 0)
|
||||
2026-02-04 17:30:42,184 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.
|
||||
2026-02-04 17:30:42,189 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-02-04 17:30:42,189 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-02-04 17:30:42,189 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-02-04 17:30:42,189 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-02-04 17:30:42,189 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:42,189 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-02-04 17:30:42,506 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:42,507 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:42,507 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:43,513 INFO spawned: 'mesh' with pid 10
|
||||
2026-02-04 17:30:43,519 INFO spawned: 'cron' with pid 11
|
||||
2026-02-04 17:30:43,528 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2026-02-04 17:30:43,540 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2026-02-04 17:30:43,551 INFO spawned: 'env' with pid 14
|
||||
2026-02-04 17:30:43,560 INFO spawned: 'search' with pid 18
|
||||
2026-02-04 17:30:43,562 INFO exited: cron (exit status 0; expected)
|
||||
2026-02-04 17:30:43,585 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:43,586 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:43,590 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:43,590 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:43,590 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:43,590 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-02-04 17:30:43,599 INFO exited: env (exit status 0; expected)
|
||||
2026-02-04 17:30:45,636 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:45,663 INFO spawned: 'search' with pid 29
|
||||
2026-02-04 17:30:45,667 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:45,676 INFO spawned: 'mesh' with pid 30
|
||||
2026-02-04 17:30:45,676 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:45,714 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:45,715 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:45,830 INFO spawned: 'mesh' with pid 33
|
||||
2026-02-04 17:30:45,842 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:45,842 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:45,855 INFO spawned: 'search' with pid 34
|
||||
2026-02-04 17:30:45,972 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:45,973 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:45,989 INFO spawned: 'mesh' with pid 37
|
||||
2026-02-04 17:30:46,000 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:46,006 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,021 INFO spawned: 'search' with pid 38
|
||||
2026-02-04 17:30:46,096 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,096 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:46,111 INFO spawned: 'mesh' with pid 41
|
||||
2026-02-04 17:30:46,115 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:46,125 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,130 INFO spawned: 'search' with pid 42
|
||||
2026-02-04 17:30:46,213 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,214 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:46,220 INFO spawned: 'search' with pid 45
|
||||
2026-02-04 17:30:46,302 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,302 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:46,319 INFO spawned: 'mesh' with pid 47
|
||||
2026-02-04 17:30:46,321 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:46,328 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,340 INFO spawned: 'search' with pid 48
|
||||
2026-02-04 17:30:46,492 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,505 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:46,510 INFO spawned: 'mesh' with pid 51
|
||||
2026-02-04 17:30:46,516 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:46,522 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,529 INFO spawned: 'search' with pid 52
|
||||
2026-02-04 17:30:46,681 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,681 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:46,704 INFO spawned: 'search' with pid 55
|
||||
2026-02-04 17:30:46,705 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:46,742 INFO spawned: 'mesh' with pid 56
|
||||
2026-02-04 17:30:46,742 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,831 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,833 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:46,846 INFO spawned: 'mesh' with pid 59
|
||||
2026-02-04 17:30:46,853 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:46,855 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,872 INFO spawned: 'search' with pid 60
|
||||
2026-02-04 17:30:46,985 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:46,988 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:47,032 INFO spawned: 'mesh' with pid 63
|
||||
2026-02-04 17:30:47,035 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:47,042 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:47,061 INFO spawned: 'search' with pid 64
|
||||
2026-02-04 17:30:47,202 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:47,202 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:47,225 INFO spawned: 'mesh' with pid 67
|
||||
2026-02-04 17:30:47,293 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:47,306 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:47,361 INFO spawned: 'search' with pid 68
|
||||
2026-02-04 17:30:47,362 WARN exited: db_connection_checker (exit status 1; not expected)
|
||||
2026-02-04 17:30:47,473 INFO spawned: 'db_connection_checker' with pid 71
|
||||
2026-02-04 17:30:47,477 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:47,487 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:47,487 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 17:30:47,560 INFO spawned: 'mesh' with pid 73
|
||||
2026-02-04 17:30:47,588 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-04 17:30:47,589 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:47,631 INFO spawned: 'search' with pid 74
|
||||
2026-02-04 17:30:48,648 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:51,538 WARN exited: db_connection_checker (exit status 1; not expected)
|
||||
2026-02-04 17:30:52,598 INFO spawned: 'db_connection_checker' with pid 87
|
||||
2026-02-04 17:30:53,630 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:59,525 WARN exited: db_connection_checker (exit status 1; not expected)
|
||||
2026-02-04 17:31:00,583 INFO spawned: 'db_connection_checker' with pid 95
|
||||
2026-02-04 17:31:01,608 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:17,337 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-02-04 17:31:17,341 INFO reaped unknown pid 107 (exit status 0)
|
||||
2026-02-07 14:26:13,016 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.
|
||||
2026-02-07 14:26:13,017 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-02-07 14:26:13,017 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-02-07 14:26:13,017 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-02-07 14:26:13,017 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-02-07 14:26:13,017 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:13,017 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-02-07 14:26:13,340 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:13,340 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:13,340 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:14,351 INFO spawned: 'mesh' with pid 10
|
||||
2026-02-07 14:26:14,364 INFO spawned: 'cron' with pid 11
|
||||
2026-02-07 14:26:14,394 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2026-02-07 14:26:14,423 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2026-02-07 14:26:14,459 INFO spawned: 'env' with pid 15
|
||||
2026-02-07 14:26:14,499 INFO spawned: 'search' with pid 19
|
||||
2026-02-07 14:26:14,506 INFO exited: cron (exit status 0; expected)
|
||||
2026-02-07 14:26:14,506 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-02-07 14:26:14,532 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:14,532 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:14,532 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:14,532 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:14,532 INFO exited: env (exit status 0; expected)
|
||||
2026-02-07 14:26:14,552 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-07 14:26:14,683 INFO spawned: 'mesh' with pid 23
|
||||
2026-02-07 14:26:14,695 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:14,696 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:14,756 INFO spawned: 'search' with pid 25
|
||||
2026-02-07 14:26:14,758 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-07 14:26:14,830 INFO spawned: 'mesh' with pid 27
|
||||
2026-02-07 14:26:14,831 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:14,836 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:14,841 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:14,858 INFO spawned: 'search' with pid 28
|
||||
2026-02-07 14:26:14,953 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:14,953 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:14,972 INFO spawned: 'search' with pid 31
|
||||
2026-02-07 14:26:15,051 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:15,052 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-07 14:26:15,161 INFO spawned: 'mesh' with pid 33
|
||||
2026-02-07 14:26:15,173 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:15,179 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:15,196 INFO spawned: 'search' with pid 34
|
||||
2026-02-07 14:26:15,458 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:15,458 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:15,491 INFO spawned: 'search' with pid 37
|
||||
2026-02-07 14:26:15,500 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-07 14:26:15,660 INFO spawned: 'mesh' with pid 39
|
||||
2026-02-07 14:26:15,670 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:15,674 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:15,674 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:15,694 INFO spawned: 'search' with pid 40
|
||||
2026-02-07 14:26:15,877 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:15,878 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:15,914 INFO spawned: 'search' with pid 43
|
||||
2026-02-07 14:26:15,957 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:15,957 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-07 14:26:15,977 INFO spawned: 'mesh' with pid 44
|
||||
2026-02-07 14:26:16,142 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:16,144 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:16,152 INFO spawned: 'search' with pid 47
|
||||
2026-02-07 14:26:16,234 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:16,234 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-07 14:26:16,403 INFO spawned: 'mesh' with pid 49
|
||||
2026-02-07 14:26:16,434 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-07 14:26:16,483 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:16,555 INFO spawned: 'search' with pid 51
|
||||
2026-02-07 14:26:17,563 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:36,732 INFO reaped unknown pid 67 (exit status 0)
|
||||
2026-02-07 14:26:36,738 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-02-20 16:02:14,579 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.
|
||||
2026-02-20 16:02:14,580 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-02-20 16:02:14,580 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-02-20 16:02:14,580 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-02-20 16:02:14,580 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-02-20 16:02:14,580 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:14,580 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-02-20 16:02:14,901 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:14,903 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:14,903 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:15,910 INFO spawned: 'mesh' with pid 10
|
||||
2026-02-20 16:02:15,931 INFO spawned: 'cron' with pid 11
|
||||
2026-02-20 16:02:15,944 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2026-02-20 16:02:15,977 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2026-02-20 16:02:16,043 INFO spawned: 'env' with pid 15
|
||||
2026-02-20 16:02:16,082 INFO spawned: 'search' with pid 19
|
||||
2026-02-20 16:02:16,084 INFO exited: cron (exit status 0; expected)
|
||||
2026-02-20 16:02:16,095 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:16,099 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:16,099 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:16,099 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:16,099 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:16,101 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-02-20 16:02:16,104 INFO exited: env (exit status 0; expected)
|
||||
2026-02-20 16:02:16,179 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-20 16:02:16,490 INFO spawned: 'mesh' with pid 23
|
||||
2026-02-20 16:02:16,502 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-20 16:02:16,503 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:16,555 INFO spawned: 'search' with pid 24
|
||||
2026-02-20 16:02:16,748 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:16,748 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-20 16:02:16,782 INFO spawned: 'mesh' with pid 27
|
||||
2026-02-20 16:02:16,783 WARN exited: search (exit status 1; not expected)
|
||||
2026-02-20 16:02:16,787 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:16,805 INFO spawned: 'search' with pid 28
|
||||
2026-02-20 16:02:17,833 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:35,805 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-02-20 16:02:35,810 INFO reaped unknown pid 45 (exit status 0)
|
||||
2026-03-04 12:10:26,509 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.
|
||||
2026-03-04 12:10:26,514 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-03-04 12:10:26,514 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-03-04 12:10:26,514 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-03-04 12:10:26,515 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-03-04 12:10:26,515 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:26,515 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-03-04 12:10:26,841 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:26,845 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:26,845 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:27,859 INFO spawned: 'mesh' with pid 10
|
||||
2026-03-04 12:10:27,930 INFO spawned: 'cron' with pid 11
|
||||
2026-03-04 12:10:28,013 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2026-03-04 12:10:28,081 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2026-03-04 12:10:28,244 INFO spawned: 'env' with pid 14
|
||||
2026-03-04 12:10:28,505 INFO spawned: 'search' with pid 17
|
||||
2026-03-04 12:10:28,672 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:28,672 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:28,672 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:28,672 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:28,672 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:28,672 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:28,672 INFO exited: cron (exit status 0; expected)
|
||||
2026-03-04 12:10:28,673 INFO exited: env (exit status 0; expected)
|
||||
2026-03-04 12:10:28,835 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-03-04 12:10:49,184 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-03-04 12:10:49,188 INFO reaped unknown pid 37 (exit status 0)
|
||||
2026-03-23 09:52:39,972 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.
|
||||
2026-03-23 09:52:39,987 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-03-23 09:52:39,987 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-03-23 09:52:39,987 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-03-23 09:52:39,987 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-03-23 09:52:39,987 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:39,987 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-03-23 09:52:40,316 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:40,316 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:40,319 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:41,332 INFO spawned: 'mesh' with pid 10
|
||||
2026-03-23 09:52:41,384 INFO spawned: 'cron' with pid 11
|
||||
2026-03-23 09:52:41,442 INFO spawned: 'cron_update_indexes' with pid 12
|
||||
2026-03-23 09:52:41,508 INFO spawned: 'db_connection_checker' with pid 13
|
||||
2026-03-23 09:52:41,588 INFO spawned: 'env' with pid 16
|
||||
2026-03-23 09:52:41,673 INFO spawned: 'search' with pid 22
|
||||
2026-03-23 09:52:41,674 INFO exited: cron (exit status 0; expected)
|
||||
2026-03-23 09:52:41,726 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:41,726 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:41,726 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:41,726 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:41,726 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:41,726 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-03-23 09:52:41,820 INFO exited: env (exit status 0; expected)
|
||||
2026-03-23 09:53:01,582 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-03-23 09:53:01,587 INFO reaped unknown pid 37 (exit status 0)
|
||||
2026-03-25 17:35:17,266 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.
|
||||
2026-03-25 17:35:17,273 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-03-25 17:35:17,273 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-03-25 17:35:17,273 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-03-25 17:35:17,273 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-03-25 17:35:17,273 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:17,273 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-03-25 17:35:17,593 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:17,593 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:17,593 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:18,618 INFO spawned: 'mesh' with pid 10
|
||||
2026-03-25 17:35:18,722 INFO spawned: 'cron' with pid 11
|
||||
2026-03-25 17:35:18,752 INFO spawned: 'cron_update_indexes' with pid 13
|
||||
2026-03-25 17:35:18,906 INFO spawned: 'db_connection_checker' with pid 16
|
||||
2026-03-25 17:35:19,006 INFO spawned: 'env' with pid 18
|
||||
2026-03-25 17:35:19,205 INFO spawned: 'search' with pid 22
|
||||
2026-03-25 17:35:19,206 INFO exited: cron (exit status 0; expected)
|
||||
2026-03-25 17:35:19,325 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,353 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,353 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,353 INFO success: env entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,353 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,353 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-03-25 17:35:19,401 INFO exited: env (exit status 0; expected)
|
||||
2026-03-25 17:35:38,980 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-03-25 17:35:38,982 INFO reaped unknown pid 37 (exit status 0)
|
||||
2026-03-26 07:03:57,312 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.
|
||||
2026-03-26 07:03:57,314 INFO Included extra file "/etc/supervisord.conf.d/cron.conf" during parsing
|
||||
2026-03-26 07:03:57,314 INFO Included extra file "/etc/supervisord.conf.d/cron_update_indexes.conf" during parsing
|
||||
2026-03-26 07:03:57,314 INFO Included extra file "/etc/supervisord.conf.d/db_connection_checker.conf" during parsing
|
||||
2026-03-26 07:03:57,314 INFO Included extra file "/etc/supervisord.conf.d/env.conf" during parsing
|
||||
2026-03-26 07:03:57,314 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-26 07:03:57,314 INFO Included extra file "/etc/supervisord.conf.d/search.conf" during parsing
|
||||
2026-03-26 07:03:57,637 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:03:57,637 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:03:57,642 INFO supervisord started with pid 1
|
||||
2026-03-26 07:03:58,647 INFO spawned: 'mesh' with pid 9
|
||||
2026-03-26 07:03:58,700 INFO spawned: 'cron' with pid 10
|
||||
2026-03-26 07:03:58,766 INFO spawned: 'cron_update_indexes' with pid 11
|
||||
2026-03-26 07:03:58,830 INFO spawned: 'db_connection_checker' with pid 14
|
||||
2026-03-26 07:03:58,902 INFO spawned: 'env' with pid 15
|
||||
2026-03-26 07:03:58,999 INFO spawned: 'search' with pid 16
|
||||
2026-03-26 07:03:59,055 INFO exited: cron (exit status 0; expected)
|
||||
2026-03-26 07:03:59,070 INFO exited: env (exit status 0; expected)
|
||||
2026-03-26 07:03:59,124 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:59,137 INFO success: cron_update_indexes entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:59,138 INFO success: db_connection_checker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:59,138 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:59,138 INFO exited: mesh (exit status 0; expected)
|
||||
2026-03-26 07:03:59,184 INFO spawned: 'mesh' with pid 21
|
||||
2026-03-26 07:03:59,194 INFO exited: cron_update_indexes (exit status 0; expected)
|
||||
2026-03-26 07:03:59,394 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:59,463 INFO exited: mesh (exit status 0; expected)
|
||||
2026-03-26 07:03:59,490 INFO spawned: 'mesh' with pid 24
|
||||
2026-03-26 07:03:59,557 WARN exited: search (exit status 1; not expected)
|
||||
2026-03-26 07:03:59,557 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:59,578 INFO spawned: 'search' with pid 26
|
||||
2026-03-26 07:03:59,675 INFO success: search entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:59,675 INFO exited: mesh (exit status 0; expected)
|
||||
2026-03-26 07:04:00,686 INFO spawned: 'mesh' with pid 29
|
||||
2026-03-26 07:04:01,854 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:20,011 INFO exited: db_connection_checker (exit status 0; expected)
|
||||
2026-03-26 07:04:20,016 INFO reaped unknown pid 44 (exit status 0)
|
||||
File diff suppressed because one or more lines are too long
@@ -0,0 +1,405 @@
|
||||
2025-11-12 08:50:25,712 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.
|
||||
2025-11-12 08:50:25,731 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:25,731 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-11-12 08:50:25,731 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-12 08:50:25,780 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:25,784 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:25,784 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:26,791 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-12 08:50:26,849 INFO spawned: 'taskmgr_reader' with pid 17
|
||||
2025-11-12 08:50:26,994 INFO spawned: 'taskmgr_worker' with pid 22
|
||||
2025-11-12 08:50:27,108 INFO spawned: 'taskmgr_writer' with pid 23
|
||||
2025-11-12 08:50:27,964 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:27,964 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:27,964 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:27,964 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:25,456 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.
|
||||
2025-11-17 12:01:25,462 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:25,462 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-11-17 12:01:25,463 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-17 12:01:25,823 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:25,823 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:25,823 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:26,842 INFO spawned: 'mesh' with pid 22
|
||||
2025-11-17 12:01:26,944 INFO spawned: 'taskmgr_reader' with pid 23
|
||||
2025-11-17 12:01:26,977 INFO spawned: 'taskmgr_worker' with pid 24
|
||||
2025-11-17 12:01:27,197 INFO spawned: 'taskmgr_writer' with pid 26
|
||||
2025-11-17 12:01:28,241 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,241 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,241 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,241 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:42,121 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.
|
||||
2025-11-21 15:30:42,127 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:42,127 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-11-21 15:30:42,127 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-21 15:30:42,459 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:42,459 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:42,459 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:43,471 INFO spawned: 'mesh' with pid 37
|
||||
2025-11-21 15:30:43,549 INFO spawned: 'taskmgr_reader' with pid 38
|
||||
2025-11-21 15:30:43,578 INFO spawned: 'taskmgr_worker' with pid 39
|
||||
2025-11-21 15:30:43,678 INFO spawned: 'taskmgr_writer' with pid 41
|
||||
2025-11-21 15:30:44,614 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:44,614 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:44,615 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:44,626 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,710 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.
|
||||
2025-11-22 15:19:48,718 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:48,719 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-11-22 15:19:48,719 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:19:49,076 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:49,083 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:49,083 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:50,121 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:19:50,186 INFO spawned: 'taskmgr_reader' with pid 18
|
||||
2025-11-22 15:19:50,246 INFO spawned: 'taskmgr_worker' with pid 20
|
||||
2025-11-22 15:19:50,397 INFO spawned: 'taskmgr_writer' with pid 22
|
||||
2025-11-22 15:19:51,477 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,478 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,478 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:51,478 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:04,698 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:28:04,720 INFO waiting for mesh, taskmgr_reader, taskmgr_worker, taskmgr_writer to die
|
||||
2025-11-22 15:28:04,774 INFO stopped: taskmgr_writer (exit status 0)
|
||||
2025-11-22 15:28:04,784 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:28:04,794 INFO stopped: taskmgr_reader (exit status 0)
|
||||
2025-11-22 15:28:04,807 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:33,227 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.
|
||||
2025-11-22 15:28:33,232 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:33,232 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-11-22 15:28:33,232 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:28:33,250 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:33,250 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:33,268 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:34,273 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:28:34,309 INFO spawned: 'taskmgr_reader' with pid 18
|
||||
2025-11-22 15:28:34,361 INFO spawned: 'taskmgr_worker' with pid 19
|
||||
2025-11-22 15:28:34,440 INFO spawned: 'taskmgr_writer' with pid 20
|
||||
2025-11-22 15:28:35,165 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:35,165 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:35,165 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:35,165 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:52,988 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:52,989 INFO waiting for mesh, taskmgr_reader, taskmgr_worker, taskmgr_writer to die
|
||||
2025-11-22 15:30:53,009 INFO stopped: taskmgr_writer (exit status 0)
|
||||
2025-11-22 15:30:53,023 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:30:53,036 INFO stopped: taskmgr_reader (exit status 0)
|
||||
2025-11-22 15:30:53,056 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:23,540 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.
|
||||
2025-11-22 15:31:23,543 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:23,543 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-11-22 15:31:23,543 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:31:23,562 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:23,571 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:23,571 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:24,584 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:31:24,652 INFO spawned: 'taskmgr_reader' with pid 17
|
||||
2025-11-22 15:31:24,679 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-11-22 15:31:24,816 INFO spawned: 'taskmgr_writer' with pid 20
|
||||
2025-11-22 15:31:25,597 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:25,597 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:25,597 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:25,597 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:49,836 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:49,846 INFO waiting for mesh, taskmgr_reader, taskmgr_worker, taskmgr_writer to die
|
||||
2025-11-22 15:37:49,884 INFO stopped: taskmgr_writer (exit status 0)
|
||||
2025-11-22 15:37:49,894 INFO stopped: taskmgr_worker (exit status 0)
|
||||
2025-11-22 15:37:49,903 INFO stopped: taskmgr_reader (exit status 0)
|
||||
2025-11-22 15:37:49,903 INFO reaped unknown pid 44 (terminated by SIGTERM)
|
||||
2025-11-22 15:37:49,911 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:32,809 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.
|
||||
2025-11-22 15:38:32,812 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:32,812 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-11-22 15:38:32,812 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-22 15:38:32,853 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:32,853 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:32,854 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:33,858 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:38:33,918 INFO spawned: 'taskmgr_reader' with pid 17
|
||||
2025-11-22 15:38:33,984 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2025-11-22 15:38:34,101 INFO spawned: 'taskmgr_writer' with pid 19
|
||||
2025-11-22 15:38:35,266 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:35,266 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:35,266 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:35,266 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:28,828 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.
|
||||
2025-11-25 15:48:28,840 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:28,840 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-11-25 15:48:28,840 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-11-25 15:48:29,194 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:29,194 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:29,196 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:30,222 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-25 15:48:30,286 INFO spawned: 'taskmgr_reader' with pid 27
|
||||
2025-11-25 15:48:30,388 INFO spawned: 'taskmgr_worker' with pid 28
|
||||
2025-11-25 15:48:30,491 INFO spawned: 'taskmgr_writer' with pid 31
|
||||
2025-11-25 15:48:31,492 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,493 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,493 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,493 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:24,609 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.
|
||||
2025-12-07 15:52:24,617 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:24,619 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-12-07 15:52:24,621 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-07 15:52:24,950 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:24,950 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:24,953 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:25,979 INFO spawned: 'mesh' with pid 28
|
||||
2025-12-07 15:52:26,024 INFO spawned: 'taskmgr_reader' with pid 29
|
||||
2025-12-07 15:52:26,089 INFO spawned: 'taskmgr_worker' with pid 30
|
||||
2025-12-07 15:52:26,205 INFO spawned: 'taskmgr_writer' with pid 33
|
||||
2025-12-07 15:52:27,245 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,245 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,245 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:27,245 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:43,924 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.
|
||||
2025-12-08 11:39:43,940 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:43,940 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-12-08 11:39:43,940 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-08 11:39:44,277 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:44,278 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:44,278 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:45,286 INFO spawned: 'mesh' with pid 39
|
||||
2025-12-08 11:39:45,364 INFO spawned: 'taskmgr_reader' with pid 41
|
||||
2025-12-08 11:39:45,488 INFO spawned: 'taskmgr_worker' with pid 44
|
||||
2025-12-08 11:39:45,554 INFO spawned: 'taskmgr_writer' with pid 46
|
||||
2025-12-08 11:39:46,613 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:46,613 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:46,613 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:46,613 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:50,758 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.
|
||||
2025-12-11 15:42:50,805 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:50,805 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-12-11 15:42:50,805 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-11 15:42:51,133 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:51,158 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:51,158 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:52,195 INFO spawned: 'mesh' with pid 39
|
||||
2025-12-11 15:42:52,242 INFO spawned: 'taskmgr_reader' with pid 40
|
||||
2025-12-11 15:42:52,352 INFO spawned: 'taskmgr_worker' with pid 41
|
||||
2025-12-11 15:42:52,409 INFO spawned: 'taskmgr_writer' with pid 43
|
||||
2025-12-11 15:42:53,411 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,412 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,412 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:53,412 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:31,423 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.
|
||||
2025-12-14 06:18:31,426 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:31,426 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-12-14 06:18:31,426 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-14 06:18:31,750 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:31,750 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:31,751 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:32,767 INFO spawned: 'mesh' with pid 37
|
||||
2025-12-14 06:18:32,822 INFO spawned: 'taskmgr_reader' with pid 38
|
||||
2025-12-14 06:18:32,904 INFO spawned: 'taskmgr_worker' with pid 40
|
||||
2025-12-14 06:18:32,995 INFO spawned: 'taskmgr_writer' with pid 41
|
||||
2025-12-14 06:18:34,065 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:34,065 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:34,065 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:34,065 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:42,345 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.
|
||||
2025-12-15 18:35:42,347 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:42,348 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-12-15 18:35:42,350 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-15 18:35:42,701 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:42,701 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:42,702 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:43,711 INFO spawned: 'mesh' with pid 46
|
||||
2025-12-15 18:35:43,785 INFO spawned: 'taskmgr_reader' with pid 47
|
||||
2025-12-15 18:35:43,860 INFO spawned: 'taskmgr_worker' with pid 48
|
||||
2025-12-15 18:35:44,006 INFO spawned: 'taskmgr_writer' with pid 52
|
||||
2025-12-15 18:35:45,018 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:45,018 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:45,018 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:45,018 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:08,751 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.
|
||||
2025-12-18 15:23:08,763 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:23:08,763 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2025-12-18 15:23:08,763 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2025-12-18 15:23:09,110 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:09,119 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:09,119 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:10,130 INFO spawned: 'mesh' with pid 37
|
||||
2025-12-18 15:23:10,248 INFO spawned: 'taskmgr_reader' with pid 38
|
||||
2025-12-18 15:23:10,342 INFO spawned: 'taskmgr_worker' with pid 39
|
||||
2025-12-18 15:23:10,447 INFO spawned: 'taskmgr_writer' with pid 41
|
||||
2025-12-18 15:23:11,464 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,465 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,465 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:11,465 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,374 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:18,605 INFO spawned: 'mesh' with pid 66
|
||||
2025-12-18 20:53:18,634 INFO exited: taskmgr_worker (exit status 0; expected)
|
||||
2025-12-18 20:53:18,796 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,809 INFO spawned: 'taskmgr_worker' with pid 68
|
||||
2025-12-18 20:53:18,840 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,886 INFO spawned: 'mesh' with pid 69
|
||||
2025-12-18 20:53:18,913 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,043 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,296 WARN exited: taskmgr_worker (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,297 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,346 INFO spawned: 'mesh' with pid 72
|
||||
2025-12-18 20:53:19,424 INFO spawned: 'taskmgr_worker' with pid 73
|
||||
2025-12-18 20:53:19,433 WARN exited: taskmgr_reader (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,480 INFO reaped unknown pid 63 (exit status 0)
|
||||
2025-12-18 20:53:19,618 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,620 INFO spawned: 'taskmgr_reader' with pid 76
|
||||
2025-12-18 20:53:19,620 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,744 WARN exited: taskmgr_writer (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:19,744 WARN exited: mesh (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,744 WARN exited: taskmgr_worker (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,744 INFO reaped unknown pid 53 (terminated by SIGHUP)
|
||||
2025-12-18 20:53:19,744 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,807 INFO waiting for taskmgr_reader to die
|
||||
2025-12-18 20:53:19,807 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,166 WARN exited: taskmgr_reader (exit status 1; not expected)
|
||||
2026-01-25 19:02:21,716 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.
|
||||
2026-01-25 19:02:21,733 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:21,733 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-01-25 19:02:21,734 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-01-25 19:02:21,792 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:21,792 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:21,792 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:22,800 INFO spawned: 'mesh' with pid 17
|
||||
2026-01-25 19:02:22,876 INFO spawned: 'taskmgr_reader' with pid 18
|
||||
2026-01-25 19:02:22,966 INFO spawned: 'taskmgr_worker' with pid 20
|
||||
2026-01-25 19:02:23,019 INFO spawned: 'taskmgr_writer' with pid 21
|
||||
2026-01-25 19:02:24,051 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,051 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,051 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:24,052 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:42,160 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.
|
||||
2026-02-04 12:30:42,163 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:42,163 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-02-04 12:30:42,166 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 12:30:42,486 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:42,512 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:42,513 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:43,519 INFO spawned: 'mesh' with pid 41
|
||||
2026-02-04 12:30:43,598 INFO spawned: 'taskmgr_reader' with pid 42
|
||||
2026-02-04 12:30:43,683 INFO spawned: 'taskmgr_worker' with pid 44
|
||||
2026-02-04 12:30:43,789 INFO spawned: 'taskmgr_writer' with pid 46
|
||||
2026-02-04 12:30:44,821 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,821 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,821 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:44,821 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:35,544 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.
|
||||
2026-02-04 14:57:35,561 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,561 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-02-04 14:57:35,561 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 14:57:35,894 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:35,894 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:35,895 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:36,931 INFO spawned: 'mesh' with pid 20
|
||||
2026-02-04 14:57:36,954 INFO spawned: 'taskmgr_reader' with pid 21
|
||||
2026-02-04 14:57:37,036 INFO spawned: 'taskmgr_worker' with pid 23
|
||||
2026-02-04 14:57:37,096 INFO spawned: 'taskmgr_writer' with pid 24
|
||||
2026-02-04 14:57:38,122 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,129 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,129 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:38,133 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:03,023 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.
|
||||
2026-02-04 17:31:03,040 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:31:03,041 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-02-04 17:31:03,041 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-04 17:31:03,367 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:31:03,367 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:31:03,367 INFO supervisord started with pid 1
|
||||
2026-02-04 17:31:04,404 INFO spawned: 'mesh' with pid 32
|
||||
2026-02-04 17:31:04,429 INFO spawned: 'taskmgr_reader' with pid 33
|
||||
2026-02-04 17:31:04,532 INFO spawned: 'taskmgr_worker' with pid 34
|
||||
2026-02-04 17:31:04,621 INFO spawned: 'taskmgr_writer' with pid 36
|
||||
2026-02-04 17:31:05,692 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:05,692 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:05,692 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:05,692 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:20,579 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.
|
||||
2026-02-07 14:26:20,582 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:20,582 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-02-07 14:26:20,582 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-07 14:26:20,929 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,929 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,929 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,957 INFO spawned: 'mesh' with pid 25
|
||||
2026-02-07 14:26:22,032 INFO spawned: 'taskmgr_reader' with pid 26
|
||||
2026-02-07 14:26:22,093 INFO spawned: 'taskmgr_worker' with pid 27
|
||||
2026-02-07 14:26:22,201 INFO spawned: 'taskmgr_writer' with pid 29
|
||||
2026-02-07 14:26:23,226 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,226 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,226 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:23,226 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:19,133 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.
|
||||
2026-02-20 16:02:19,154 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:19,154 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-02-20 16:02:19,154 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-02-20 16:02:19,489 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:19,510 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:19,510 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:20,532 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-20 16:02:20,601 INFO spawned: 'taskmgr_reader' with pid 17
|
||||
2026-02-20 16:02:20,795 INFO spawned: 'taskmgr_worker' with pid 18
|
||||
2026-02-20 16:02:20,892 INFO spawned: 'taskmgr_writer' with pid 19
|
||||
2026-02-20 16:02:21,917 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,917 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,917 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,917 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:29,771 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.
|
||||
2026-03-04 12:10:29,781 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:29,795 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-03-04 12:10:29,795 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-04 12:10:30,153 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:30,153 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:30,154 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:31,191 INFO spawned: 'mesh' with pid 25
|
||||
2026-03-04 12:10:31,217 INFO spawned: 'taskmgr_reader' with pid 26
|
||||
2026-03-04 12:10:31,295 INFO spawned: 'taskmgr_worker' with pid 27
|
||||
2026-03-04 12:10:31,376 INFO spawned: 'taskmgr_writer' with pid 28
|
||||
2026-03-04 12:10:32,029 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:32,035 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:32,058 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:32,058 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:48,822 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.
|
||||
2026-03-23 09:52:48,833 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:48,833 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-03-23 09:52:48,833 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-23 09:52:49,151 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:49,151 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:49,170 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:50,176 INFO spawned: 'mesh' with pid 30
|
||||
2026-03-23 09:52:50,248 INFO spawned: 'taskmgr_reader' with pid 31
|
||||
2026-03-23 09:52:50,314 INFO spawned: 'taskmgr_worker' with pid 33
|
||||
2026-03-23 09:52:50,392 INFO spawned: 'taskmgr_writer' with pid 34
|
||||
2026-03-23 09:52:51,455 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:51,455 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:51,456 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:51,456 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:27,847 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.
|
||||
2026-03-25 17:35:27,856 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:27,856 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-03-25 17:35:27,856 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-25 17:35:28,201 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:28,201 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:28,201 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:29,229 INFO spawned: 'mesh' with pid 26
|
||||
2026-03-25 17:35:29,281 INFO spawned: 'taskmgr_reader' with pid 27
|
||||
2026-03-25 17:35:29,369 INFO spawned: 'taskmgr_worker' with pid 29
|
||||
2026-03-25 17:35:29,501 INFO spawned: 'taskmgr_writer' with pid 33
|
||||
2026-03-25 17:35:30,542 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:30,551 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:30,551 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:30,551 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,049 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.
|
||||
2026-03-26 07:04:03,078 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,078 INFO Included extra file "/opt/supervisor.d/taskmgr.conf" during parsing
|
||||
2026-03-26 07:04:03,078 INFO Included extra file "/opt/supervisor.d/worker.conf" during parsing
|
||||
2026-03-26 07:04:03,434 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,435 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,435 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,455 INFO spawned: 'mesh' with pid 20
|
||||
2026-03-26 07:04:04,515 INFO spawned: 'taskmgr_reader' with pid 21
|
||||
2026-03-26 07:04:04,563 INFO spawned: 'taskmgr_worker' with pid 22
|
||||
2026-03-26 07:04:04,700 INFO spawned: 'taskmgr_writer' with pid 25
|
||||
2026-03-26 07:04:05,734 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,771 INFO success: taskmgr_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,771 INFO success: taskmgr_worker entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:05,771 INFO success: taskmgr_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,192 @@
|
||||
2025-11-12 08:50:24,446 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.
|
||||
2025-11-12 08:50:24,446 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-11-12 08:50:24,540 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:24,540 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:24,541 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:25,584 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-11-12 08:50:26,588 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,666 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.
|
||||
2025-11-17 12:01:28,676 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-11-17 12:01:29,041 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:29,042 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:29,042 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:30,051 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-11-17 12:01:31,088 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:26,787 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.
|
||||
2025-11-21 15:30:26,788 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-11-21 15:30:27,111 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:27,111 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:27,112 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:28,121 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-11-21 15:30:29,129 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:44,347 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.
|
||||
2025-11-22 15:19:44,936 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-11-22 15:19:45,308 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:45,308 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:45,308 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:46,342 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-11-22 15:19:47,383 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:58,062 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:58,097 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:28:01,106 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:28:04,109 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:28:07,113 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:28:08,114 WARN killing 'telegram-srv' (15) with SIGKILL
|
||||
2025-11-22 15:28:08,125 WARN stopped: telegram-srv (terminated by SIGKILL)
|
||||
2025-11-22 15:28:33,863 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.
|
||||
2025-11-22 15:28:33,866 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-11-22 15:28:33,891 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:33,891 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:33,894 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:34,905 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-11-22 15:28:35,942 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:46,140 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,144 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:30:49,155 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:30:52,161 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:30:55,165 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:30:56,167 WARN killing 'telegram-srv' (15) with SIGKILL
|
||||
2025-11-22 15:30:56,172 WARN stopped: telegram-srv (terminated by SIGKILL)
|
||||
2025-11-22 15:31:23,664 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.
|
||||
2025-11-22 15:31:23,670 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-11-22 15:31:23,728 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:23,728 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:23,728 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:24,748 INFO spawned: 'telegram-srv' with pid 14
|
||||
2025-11-22 15:31:25,782 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:43,256 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:43,266 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:37:46,281 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:37:49,284 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:37:52,287 INFO waiting for telegram-srv to die
|
||||
2025-11-22 15:37:53,289 WARN killing 'telegram-srv' (14) with SIGKILL
|
||||
2025-11-22 15:37:53,297 WARN stopped: telegram-srv (terminated by SIGKILL)
|
||||
2025-11-22 15:38:34,133 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.
|
||||
2025-11-22 15:38:34,144 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-11-22 15:38:34,221 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:34,223 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:34,230 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:35,301 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-11-22 15:38:36,362 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:31,416 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.
|
||||
2025-11-25 15:48:31,435 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-11-25 15:48:31,780 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:31,804 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:31,805 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:32,842 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-11-25 15:48:33,861 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:19,235 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.
|
||||
2025-12-07 15:52:19,246 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-12-07 15:52:19,609 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:19,609 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:19,610 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:20,652 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-12-07 15:52:21,683 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:37,787 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.
|
||||
2025-12-08 11:39:37,804 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-12-08 11:39:38,138 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:38,138 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:38,138 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:39,156 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-12-08 11:39:40,206 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:37,330 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.
|
||||
2025-12-11 15:42:37,334 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-12-11 15:42:37,666 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:37,667 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:37,668 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:38,677 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-12-11 15:42:39,763 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:23,347 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.
|
||||
2025-12-14 06:18:23,391 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-12-14 06:18:23,803 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:23,804 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:23,804 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:24,823 INFO spawned: 'telegram-srv' with pid 14
|
||||
2025-12-14 06:18:25,873 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:30,860 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.
|
||||
2025-12-15 18:35:30,870 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-12-15 18:35:31,245 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:31,245 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:31,245 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:32,291 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-12-15 18:35:33,315 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:54,424 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.
|
||||
2025-12-18 15:22:54,425 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2025-12-18 15:22:54,766 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:54,772 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:54,773 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:55,796 INFO spawned: 'telegram-srv' with pid 15
|
||||
2025-12-18 15:22:56,821 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,833 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,881 INFO waiting for telegram-srv to die
|
||||
2025-12-18 20:53:20,999 WARN stopped: telegram-srv (exit status 1)
|
||||
2026-01-25 19:02:18,832 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.
|
||||
2026-01-25 19:02:18,849 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-01-25 19:02:18,902 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:18,903 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:18,903 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:19,920 INFO spawned: 'telegram-srv' with pid 15
|
||||
2026-01-25 19:02:20,961 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:21,069 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.
|
||||
2026-02-04 12:30:21,070 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-02-04 12:30:21,402 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:21,402 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:21,403 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:22,412 INFO spawned: 'telegram-srv' with pid 15
|
||||
2026-02-04 12:30:23,426 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:32,413 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.
|
||||
2026-02-04 14:57:32,418 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-02-04 14:57:32,773 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:32,787 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:32,794 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:33,824 INFO spawned: 'telegram-srv' with pid 15
|
||||
2026-02-04 14:57:34,914 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:51,818 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.
|
||||
2026-02-04 17:30:51,820 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-02-04 17:30:52,180 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:52,200 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:52,200 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:53,211 INFO spawned: 'telegram-srv' with pid 15
|
||||
2026-02-04 17:30:54,247 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:11,871 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.
|
||||
2026-02-07 14:26:11,872 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-02-07 14:26:12,193 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:12,193 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:12,194 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:13,201 INFO spawned: 'telegram-srv' with pid 15
|
||||
2026-02-07 14:26:14,210 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:20,933 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.
|
||||
2026-02-20 16:02:20,946 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-02-20 16:02:21,316 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,316 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,316 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,347 INFO spawned: 'telegram-srv' with pid 16
|
||||
2026-02-20 16:02:23,402 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:21,796 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.
|
||||
2026-03-04 12:10:21,797 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-03-04 12:10:22,110 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:22,110 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:22,111 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:23,119 INFO spawned: 'telegram-srv' with pid 15
|
||||
2026-03-04 12:10:24,143 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:35,155 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.
|
||||
2026-03-23 09:52:35,156 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-03-23 09:52:35,470 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:35,470 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:35,470 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:36,475 INFO spawned: 'telegram-srv' with pid 15
|
||||
2026-03-23 09:52:37,488 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:11,731 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.
|
||||
2026-03-25 17:35:11,736 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-03-25 17:35:12,063 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:12,064 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:12,064 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:13,070 INFO spawned: 'telegram-srv' with pid 14
|
||||
2026-03-25 17:35:14,084 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:55,539 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.
|
||||
2026-03-26 07:03:55,541 INFO Included extra file "/opt/supervisor.d/telegramsrv.conf" during parsing
|
||||
2026-03-26 07:03:55,866 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:03:55,866 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:03:55,869 INFO supervisord started with pid 1
|
||||
2026-03-26 07:03:56,883 INFO spawned: 'telegram-srv' with pid 15
|
||||
2026-03-26 07:03:57,899 INFO success: telegram-srv entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,774 @@
|
||||
2025-11-12 08:50:16,155 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.
|
||||
2025-11-12 08:50:16,155 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-11-12 08:50:16,155 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-12 08:50:16,155 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:16,155 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-12 08:50:16,155 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-11-12 08:50:16,220 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:16,220 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:16,220 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:17,254 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-12 08:50:17,272 INFO spawned: 'cron' with pid 18
|
||||
2025-11-12 08:50:17,311 INFO spawned: 'nginx' with pid 19
|
||||
2025-11-12 08:50:17,369 INFO spawned: 'updater_reader' with pid 20
|
||||
2025-11-12 08:50:17,451 INFO spawned: 'updater_writer' with pid 21
|
||||
2025-11-12 08:50:17,676 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:17,676 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:17,676 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:17,676 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:17,676 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:17,676 INFO exited: nginx (exit status 0; expected)
|
||||
2025-11-12 10:25:01,891 INFO reaped unknown pid 88 (exit status 0)
|
||||
2025-11-17 12:01:25,789 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.
|
||||
2025-11-17 12:01:25,810 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-11-17 12:01:25,810 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-17 12:01:25,810 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:25,810 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-17 12:01:25,810 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-11-17 12:01:26,164 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:26,164 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:26,164 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:27,189 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-17 12:01:27,307 INFO spawned: 'cron' with pid 18
|
||||
2025-11-17 12:01:27,368 INFO spawned: 'nginx' with pid 19
|
||||
2025-11-17 12:01:27,497 INFO spawned: 'updater_reader' with pid 20
|
||||
2025-11-17 12:01:27,610 INFO spawned: 'updater_writer' with pid 22
|
||||
2025-11-17 12:01:28,017 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,017 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,017 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,017 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,017 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,017 INFO exited: nginx (exit status 0; expected)
|
||||
2025-11-17 13:27:02,558 INFO reaped unknown pid 108 (exit status 0)
|
||||
2025-11-21 15:30:36,016 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.
|
||||
2025-11-21 15:30:36,029 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-11-21 15:30:36,029 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-21 15:30:36,029 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:36,029 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-21 15:30:36,029 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-11-21 15:30:36,362 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:36,376 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:36,378 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:37,381 INFO spawned: 'mesh' with pid 23
|
||||
2025-11-21 15:30:37,387 INFO spawned: 'cron' with pid 24
|
||||
2025-11-21 15:30:37,433 INFO spawned: 'nginx' with pid 25
|
||||
2025-11-21 15:30:37,438 INFO spawned: 'updater_reader' with pid 26
|
||||
2025-11-21 15:30:37,444 INFO spawned: 'updater_writer' with pid 27
|
||||
2025-11-21 15:30:37,691 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,694 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,695 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,698 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,700 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,702 INFO exited: nginx (exit status 0; expected)
|
||||
2025-11-21 16:31:02,204 INFO reaped unknown pid 107 (exit status 0)
|
||||
2025-11-22 15:19:46,514 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.
|
||||
2025-11-22 15:19:46,516 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-11-22 15:19:46,516 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-22 15:19:46,516 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:46,516 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-22 15:19:46,516 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-11-22 15:19:46,910 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:46,929 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:46,976 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:47,979 INFO spawned: 'mesh' with pid 26
|
||||
2025-11-22 15:19:48,030 INFO spawned: 'cron' with pid 27
|
||||
2025-11-22 15:19:48,145 INFO spawned: 'nginx' with pid 28
|
||||
2025-11-22 15:19:48,198 INFO spawned: 'updater_reader' with pid 32
|
||||
2025-11-22 15:19:48,427 INFO spawned: 'updater_writer' with pid 33
|
||||
2025-11-22 15:19:48,628 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,628 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,628 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,628 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,628 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,629 INFO exited: nginx (exit status 0; expected)
|
||||
2025-11-22 15:27:57,299 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:57,317 INFO waiting for mesh, cron, updater_reader, updater_writer to die
|
||||
2025-11-22 15:27:57,502 INFO stopped: updater_writer (exit status 0)
|
||||
2025-11-22 15:27:58,107 INFO stopped: updater_reader (exit status 0)
|
||||
2025-11-22 15:27:59,126 INFO stopped: cron (exit status 0)
|
||||
2025-11-22 15:27:59,264 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:26,274 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.
|
||||
2025-11-22 15:28:26,276 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-11-22 15:28:26,277 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-22 15:28:26,279 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:26,279 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-22 15:28:26,279 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-11-22 15:28:26,312 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:26,312 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:26,312 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:27,324 INFO spawned: 'mesh' with pid 18
|
||||
2025-11-22 15:28:27,368 INFO spawned: 'cron' with pid 19
|
||||
2025-11-22 15:28:27,392 INFO spawned: 'nginx' with pid 20
|
||||
2025-11-22 15:28:27,517 INFO spawned: 'updater_reader' with pid 22
|
||||
2025-11-22 15:28:27,579 INFO spawned: 'updater_writer' with pid 25
|
||||
2025-11-22 15:28:27,798 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:27,798 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:27,798 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:27,798 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:27,798 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:27,798 INFO exited: nginx (exit status 0; expected)
|
||||
2025-11-22 15:30:46,011 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,054 INFO waiting for mesh, cron, updater_reader, updater_writer to die
|
||||
2025-11-22 15:30:46,383 INFO stopped: updater_writer (exit status 0)
|
||||
2025-11-22 15:30:46,611 INFO stopped: updater_reader (exit status 0)
|
||||
2025-11-22 15:30:47,645 INFO stopped: cron (exit status 0)
|
||||
2025-11-22 15:30:47,710 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:18,022 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.
|
||||
2025-11-22 15:31:18,029 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-11-22 15:31:18,031 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-22 15:31:18,031 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:18,031 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-22 15:31:18,031 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-11-22 15:31:18,063 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:18,065 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:18,065 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:19,076 INFO spawned: 'mesh' with pid 17
|
||||
2025-11-22 15:31:19,127 INFO spawned: 'cron' with pid 18
|
||||
2025-11-22 15:31:19,228 INFO spawned: 'nginx' with pid 19
|
||||
2025-11-22 15:31:19,263 INFO spawned: 'updater_reader' with pid 21
|
||||
2025-11-22 15:31:19,364 INFO spawned: 'updater_writer' with pid 24
|
||||
2025-11-22 15:31:19,578 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,579 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,579 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,579 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,579 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:19,579 INFO exited: nginx (exit status 0; expected)
|
||||
2025-11-22 15:37:43,076 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:43,131 INFO waiting for mesh, cron, updater_reader, updater_writer to die
|
||||
2025-11-22 15:37:43,776 INFO stopped: updater_writer (exit status 0)
|
||||
2025-11-22 15:37:44,271 INFO stopped: updater_reader (exit status 0)
|
||||
2025-11-22 15:37:45,286 INFO stopped: cron (exit status 0)
|
||||
2025-11-22 15:37:45,320 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:25,136 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.
|
||||
2025-11-22 15:38:25,136 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-11-22 15:38:25,136 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-22 15:38:25,136 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:25,136 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-22 15:38:25,136 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-11-22 15:38:25,207 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:25,207 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:25,208 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:26,217 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:38:26,286 INFO spawned: 'cron' with pid 17
|
||||
2025-11-22 15:38:26,342 INFO spawned: 'nginx' with pid 18
|
||||
2025-11-22 15:38:26,458 INFO spawned: 'updater_reader' with pid 20
|
||||
2025-11-22 15:38:26,542 INFO spawned: 'updater_writer' with pid 21
|
||||
2025-11-22 15:38:26,833 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,833 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,833 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,833 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,833 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:26,833 INFO exited: nginx (exit status 0; expected)
|
||||
2025-11-22 16:20:02,034 INFO reaped unknown pid 96 (exit status 0)
|
||||
2025-11-25 15:48:24,927 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.
|
||||
2025-11-25 15:48:24,930 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-11-25 15:48:24,930 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-11-25 15:48:24,930 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:24,930 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-11-25 15:48:24,930 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-11-25 15:48:25,274 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:25,275 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:25,275 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:26,291 INFO spawned: 'mesh' with pid 19
|
||||
2025-11-25 15:48:26,314 INFO spawned: 'cron' with pid 20
|
||||
2025-11-25 15:48:26,369 INFO spawned: 'nginx' with pid 21
|
||||
2025-11-25 15:48:26,407 INFO spawned: 'updater_reader' with pid 22
|
||||
2025-11-25 15:48:26,491 INFO spawned: 'updater_writer' with pid 23
|
||||
2025-11-25 15:48:26,663 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:26,663 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:26,663 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:26,664 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:26,664 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:26,664 INFO exited: nginx (exit status 0; expected)
|
||||
2025-11-25 16:22:02,300 INFO reaped unknown pid 86 (exit status 0)
|
||||
2025-12-07 15:52:23,408 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.
|
||||
2025-12-07 15:52:23,409 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-12-07 15:52:23,409 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-07 15:52:23,409 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:23,409 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-07 15:52:23,409 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-12-07 15:52:23,746 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:23,747 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:23,775 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:24,790 INFO spawned: 'mesh' with pid 25
|
||||
2025-12-07 15:52:24,858 INFO spawned: 'cron' with pid 26
|
||||
2025-12-07 15:52:24,895 INFO spawned: 'nginx' with pid 27
|
||||
2025-12-07 15:52:24,986 INFO spawned: 'updater_reader' with pid 31
|
||||
2025-12-07 15:52:25,100 INFO spawned: 'updater_writer' with pid 32
|
||||
2025-12-07 15:52:25,260 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,261 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,261 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,261 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,261 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:25,261 INFO exited: nginx (exit status 0; expected)
|
||||
2025-12-08 11:39:32,810 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.
|
||||
2025-12-08 11:39:32,813 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-12-08 11:39:32,813 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-08 11:39:32,813 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:32,813 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-08 11:39:32,813 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-12-08 11:39:33,157 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:33,157 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:33,158 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:34,164 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-08 11:39:34,257 INFO spawned: 'cron' with pid 18
|
||||
2025-12-08 11:39:34,310 INFO spawned: 'nginx' with pid 19
|
||||
2025-12-08 11:39:34,389 INFO spawned: 'updater_reader' with pid 21
|
||||
2025-12-08 11:39:34,465 INFO spawned: 'updater_writer' with pid 24
|
||||
2025-12-08 11:39:34,666 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,666 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,666 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,666 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,666 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,666 INFO exited: nginx (exit status 0; expected)
|
||||
2025-12-08 13:02:01,978 INFO reaped unknown pid 88 (exit status 0)
|
||||
2025-12-11 15:42:42,800 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.
|
||||
2025-12-11 15:42:42,808 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-12-11 15:42:42,808 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-11 15:42:42,808 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:42,808 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-11 15:42:42,808 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-12-11 15:42:43,138 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:43,142 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:43,142 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:44,151 INFO spawned: 'mesh' with pid 25
|
||||
2025-12-11 15:42:44,230 INFO spawned: 'cron' with pid 26
|
||||
2025-12-11 15:42:44,300 INFO spawned: 'nginx' with pid 28
|
||||
2025-12-11 15:42:44,365 INFO spawned: 'updater_reader' with pid 29
|
||||
2025-12-11 15:42:44,460 INFO spawned: 'updater_writer' with pid 32
|
||||
2025-12-11 15:42:44,758 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,787 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,787 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,787 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,787 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,787 INFO exited: nginx (exit status 0; expected)
|
||||
2025-12-11 16:49:02,735 INFO reaped unknown pid 92 (exit status 0)
|
||||
2025-12-14 06:18:25,253 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.
|
||||
2025-12-14 06:18:25,256 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-12-14 06:18:25,256 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-14 06:18:25,256 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,256 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-14 06:18:25,256 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-12-14 06:18:25,603 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:25,603 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:25,603 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:26,622 INFO spawned: 'mesh' with pid 23
|
||||
2025-12-14 06:18:26,665 INFO spawned: 'cron' with pid 24
|
||||
2025-12-14 06:18:26,827 INFO spawned: 'nginx' with pid 25
|
||||
2025-12-14 06:18:26,960 INFO spawned: 'updater_reader' with pid 29
|
||||
2025-12-14 06:18:27,028 INFO spawned: 'updater_writer' with pid 30
|
||||
2025-12-14 06:18:27,382 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,382 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,382 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,382 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,382 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:27,385 INFO exited: nginx (exit status 0; expected)
|
||||
2025-12-14 08:29:01,369 INFO reaped unknown pid 104 (exit status 0)
|
||||
2025-12-15 18:35:32,067 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.
|
||||
2025-12-15 18:35:32,094 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-12-15 18:35:32,094 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-15 18:35:32,094 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:32,094 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-15 18:35:32,094 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-12-15 18:35:32,459 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:32,459 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:32,460 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:33,484 INFO spawned: 'mesh' with pid 26
|
||||
2025-12-15 18:35:33,584 INFO spawned: 'cron' with pid 27
|
||||
2025-12-15 18:35:33,779 INFO spawned: 'nginx' with pid 28
|
||||
2025-12-15 18:35:33,912 INFO spawned: 'updater_reader' with pid 29
|
||||
2025-12-15 18:35:34,093 INFO spawned: 'updater_writer' with pid 30
|
||||
2025-12-15 18:35:34,582 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,582 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,582 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,582 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,582 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:34,616 INFO exited: nginx (exit status 0; expected)
|
||||
2025-12-18 15:22:51,687 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.
|
||||
2025-12-18 15:22:51,689 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2025-12-18 15:22:51,689 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2025-12-18 15:22:51,689 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:51,689 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2025-12-18 15:22:51,689 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2025-12-18 15:22:52,024 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:52,024 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:52,024 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:53,034 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-18 15:22:53,102 INFO spawned: 'cron' with pid 18
|
||||
2025-12-18 15:22:53,161 INFO spawned: 'nginx' with pid 19
|
||||
2025-12-18 15:22:53,273 INFO spawned: 'updater_reader' with pid 21
|
||||
2025-12-18 15:22:53,327 INFO spawned: 'updater_writer' with pid 24
|
||||
2025-12-18 15:22:53,491 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:53,491 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:53,491 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:53,491 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:53,491 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:53,492 INFO exited: nginx (exit status 0; expected)
|
||||
2025-12-18 17:00:01,795 INFO reaped unknown pid 95 (exit status 0)
|
||||
2025-12-18 20:53:11,724 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:11,865 INFO spawned: 'mesh' with pid 351
|
||||
2025-12-18 20:53:11,901 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,923 WARN exited: updater_reader (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:11,927 INFO spawned: 'updater_reader' with pid 353
|
||||
2025-12-18 20:53:11,943 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,985 INFO spawned: 'mesh' with pid 355
|
||||
2025-12-18 20:53:11,988 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,988 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,993 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,019 INFO spawned: 'updater_reader' with pid 356
|
||||
2025-12-18 20:53:12,069 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,072 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,082 INFO spawned: 'mesh' with pid 359
|
||||
2025-12-18 20:53:12,086 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,088 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,100 INFO spawned: 'updater_reader' with pid 360
|
||||
2025-12-18 20:53:12,131 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,131 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,143 INFO spawned: 'updater_reader' with pid 363
|
||||
2025-12-18 20:53:12,156 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,161 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,192 INFO spawned: 'mesh' with pid 365
|
||||
2025-12-18 20:53:12,196 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,203 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,230 INFO spawned: 'updater_reader' with pid 366
|
||||
2025-12-18 20:53:12,290 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,290 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,313 INFO spawned: 'updater_reader' with pid 369
|
||||
2025-12-18 20:53:12,333 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,382 INFO spawned: 'mesh' with pid 370
|
||||
2025-12-18 20:53:12,383 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,444 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,466 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,503 INFO spawned: 'updater_reader' with pid 373
|
||||
2025-12-18 20:53:12,530 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,530 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,567 INFO spawned: 'mesh' with pid 375
|
||||
2025-12-18 20:53:12,575 WARN exited: updater_writer (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:12,575 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,583 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,595 INFO spawned: 'updater_reader' with pid 376
|
||||
2025-12-18 20:53:12,636 INFO spawned: 'updater_writer' with pid 377
|
||||
2025-12-18 20:53:12,708 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,709 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,709 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,728 INFO spawned: 'mesh' with pid 381
|
||||
2025-12-18 20:53:12,731 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,732 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,736 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,750 INFO spawned: 'updater_reader' with pid 382
|
||||
2025-12-18 20:53:12,778 INFO spawned: 'updater_writer' with pid 384
|
||||
2025-12-18 20:53:12,822 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,825 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,827 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,872 INFO spawned: 'mesh' with pid 387
|
||||
2025-12-18 20:53:12,878 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,883 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,896 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,928 INFO spawned: 'updater_reader' with pid 388
|
||||
2025-12-18 20:53:12,960 INFO spawned: 'updater_writer' with pid 390
|
||||
2025-12-18 20:53:12,992 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,992 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,992 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,191 INFO spawned: 'mesh' with pid 393
|
||||
2025-12-18 20:53:13,202 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,202 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,208 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,242 INFO spawned: 'updater_reader' with pid 394
|
||||
2025-12-18 20:53:13,269 INFO spawned: 'updater_writer' with pid 396
|
||||
2025-12-18 20:53:13,306 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,306 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,308 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,333 INFO spawned: 'mesh' with pid 399
|
||||
2025-12-18 20:53:13,340 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,343 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,344 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,351 INFO spawned: 'updater_reader' with pid 400
|
||||
2025-12-18 20:53:13,383 INFO spawned: 'updater_writer' with pid 402
|
||||
2025-12-18 20:53:13,435 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,436 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,438 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,467 INFO spawned: 'mesh' with pid 405
|
||||
2025-12-18 20:53:13,480 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,539 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,539 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,556 INFO spawned: 'mesh' with pid 407
|
||||
2025-12-18 20:53:13,657 INFO spawned: 'updater_reader' with pid 408
|
||||
2025-12-18 20:53:13,822 INFO spawned: 'updater_writer' with pid 410
|
||||
2025-12-18 20:53:13,962 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,962 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,962 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,962 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,135 INFO spawned: 'mesh' with pid 413
|
||||
2025-12-18 20:53:14,151 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,168 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,201 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,240 INFO spawned: 'updater_reader' with pid 414
|
||||
2025-12-18 20:53:14,386 INFO spawned: 'updater_writer' with pid 416
|
||||
2025-12-18 20:53:14,522 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,543 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,543 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,672 INFO spawned: 'mesh' with pid 418
|
||||
2025-12-18 20:53:14,734 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,734 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,789 INFO spawned: 'updater_reader' with pid 420
|
||||
2025-12-18 20:53:14,862 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,863 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,933 INFO spawned: 'updater_writer' with pid 422
|
||||
2025-12-18 20:53:14,983 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,033 INFO spawned: 'mesh' with pid 424
|
||||
2025-12-18 20:53:15,033 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,079 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,079 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,152 INFO spawned: 'updater_reader' with pid 426
|
||||
2025-12-18 20:53:15,210 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,218 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,302 INFO spawned: 'updater_writer' with pid 428
|
||||
2025-12-18 20:53:15,303 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,406 INFO spawned: 'mesh' with pid 430
|
||||
2025-12-18 20:53:15,414 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,445 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,445 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,527 INFO spawned: 'updater_reader' with pid 432
|
||||
2025-12-18 20:53:15,531 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,556 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,600 INFO spawned: 'updater_writer' with pid 434
|
||||
2025-12-18 20:53:15,629 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,638 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,673 INFO spawned: 'mesh' with pid 436
|
||||
2025-12-18 20:53:15,707 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,707 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,752 INFO spawned: 'updater_reader' with pid 438
|
||||
2025-12-18 20:53:15,762 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,777 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,806 INFO spawned: 'updater_writer' with pid 440
|
||||
2025-12-18 20:53:15,830 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,835 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,880 INFO spawned: 'mesh' with pid 442
|
||||
2025-12-18 20:53:15,884 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,896 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,934 INFO spawned: 'updater_reader' with pid 444
|
||||
2025-12-18 20:53:15,944 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,944 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,995 INFO spawned: 'updater_writer' with pid 446
|
||||
2025-12-18 20:53:16,017 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,018 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,060 INFO spawned: 'mesh' with pid 449
|
||||
2025-12-18 20:53:16,061 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,079 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,102 INFO spawned: 'updater_reader' with pid 450
|
||||
2025-12-18 20:53:16,113 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,128 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,160 INFO spawned: 'updater_writer' with pid 452
|
||||
2025-12-18 20:53:16,193 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,193 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,229 INFO spawned: 'mesh' with pid 454
|
||||
2025-12-18 20:53:16,243 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,243 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,302 INFO spawned: 'updater_reader' with pid 455
|
||||
2025-12-18 20:53:16,360 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,366 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,429 INFO spawned: 'mesh' with pid 459
|
||||
2025-12-18 20:53:16,435 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,436 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,441 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,450 INFO spawned: 'updater_reader' with pid 460
|
||||
2025-12-18 20:53:16,499 INFO spawned: 'updater_writer' with pid 462
|
||||
2025-12-18 20:53:16,539 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,559 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,561 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,602 INFO spawned: 'mesh' with pid 464
|
||||
2025-12-18 20:53:16,668 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,684 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,713 INFO spawned: 'updater_reader' with pid 466
|
||||
2025-12-18 20:53:16,750 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,751 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,802 INFO spawned: 'updater_writer' with pid 468
|
||||
2025-12-18 20:53:16,860 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,860 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,948 INFO spawned: 'mesh' with pid 471
|
||||
2025-12-18 20:53:16,995 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,995 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,030 INFO spawned: 'updater_reader' with pid 472
|
||||
2025-12-18 20:53:17,031 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,080 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,138 INFO spawned: 'updater_writer' with pid 474
|
||||
2025-12-18 20:53:17,178 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,178 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,238 INFO spawned: 'mesh' with pid 477
|
||||
2025-12-18 20:53:17,282 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,283 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,339 INFO spawned: 'updater_reader' with pid 478
|
||||
2025-12-18 20:53:17,360 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,360 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,454 INFO spawned: 'updater_writer' with pid 480
|
||||
2025-12-18 20:53:17,455 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,533 INFO spawned: 'mesh' with pid 482
|
||||
2025-12-18 20:53:17,547 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,562 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,563 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,630 INFO spawned: 'updater_reader' with pid 484
|
||||
2025-12-18 20:53:17,667 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,672 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,729 INFO spawned: 'updater_writer' with pid 486
|
||||
2025-12-18 20:53:17,820 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,820 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,901 INFO spawned: 'mesh' with pid 489
|
||||
2025-12-18 20:53:17,902 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,932 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,981 INFO spawned: 'updater_reader' with pid 490
|
||||
2025-12-18 20:53:17,987 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,988 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,070 INFO spawned: 'updater_writer' with pid 492
|
||||
2025-12-18 20:53:18,122 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,142 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,206 INFO spawned: 'mesh' with pid 495
|
||||
2025-12-18 20:53:18,300 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,301 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,301 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,324 INFO spawned: 'updater_reader' with pid 496
|
||||
2025-12-18 20:53:18,386 INFO spawned: 'updater_writer' with pid 498
|
||||
2025-12-18 20:53:18,416 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,535 INFO spawned: 'mesh' with pid 500
|
||||
2025-12-18 20:53:18,536 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,536 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,575 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,576 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,636 INFO spawned: 'updater_reader' with pid 502
|
||||
2025-12-18 20:53:18,757 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,757 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,757 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,810 INFO spawned: 'mesh' with pid 504
|
||||
2025-12-18 20:53:18,910 INFO spawned: 'updater_writer' with pid 506
|
||||
2025-12-18 20:53:18,959 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,959 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,075 INFO spawned: 'updater_reader' with pid 507
|
||||
2025-12-18 20:53:19,117 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,249 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,249 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,286 INFO spawned: 'mesh' with pid 511
|
||||
2025-12-18 20:53:19,328 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,328 WARN exited: updater_reader (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,329 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,367 INFO spawned: 'updater_reader' with pid 512
|
||||
2025-12-18 20:53:19,465 INFO spawned: 'updater_writer' with pid 514
|
||||
2025-12-18 20:53:19,656 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,784 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,784 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,784 WARN exited: updater_reader (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,892 INFO spawned: 'mesh' with pid 516
|
||||
2025-12-18 20:53:20,013 INFO spawned: 'updater_reader' with pid 518
|
||||
2025-12-18 20:53:20,096 INFO exited: cron (exit status 0; expected)
|
||||
2025-12-18 20:53:20,096 INFO reaped unknown pid 27 (exit status 0)
|
||||
2025-12-18 20:53:20,110 WARN exited: updater_writer (exit status 1; not expected)
|
||||
2025-12-18 20:53:20,110 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:20,110 INFO waiting for mesh, updater_reader to die
|
||||
2025-12-18 20:53:20,137 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,137 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:20,261 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:20,309 WARN stopped: updater_reader (exit status 1)
|
||||
2026-01-25 19:02:19,286 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.
|
||||
2026-01-25 19:02:19,298 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-01-25 19:02:19,298 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-01-25 19:02:19,298 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:19,298 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-01-25 19:02:19,298 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-01-25 19:02:19,382 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:19,385 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:19,401 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:20,432 INFO spawned: 'mesh' with pid 19
|
||||
2026-01-25 19:02:20,488 INFO spawned: 'cron' with pid 20
|
||||
2026-01-25 19:02:20,576 INFO spawned: 'nginx' with pid 21
|
||||
2026-01-25 19:02:20,678 INFO spawned: 'updater_reader' with pid 22
|
||||
2026-01-25 19:02:20,714 INFO spawned: 'updater_writer' with pid 24
|
||||
2026-01-25 19:02:21,209 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:21,209 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:21,209 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:21,209 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:21,209 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:21,209 INFO exited: nginx (exit status 0; expected)
|
||||
2026-01-25 21:02:02,374 INFO reaped unknown pid 104 (exit status 0)
|
||||
2026-02-04 12:30:28,905 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.
|
||||
2026-02-04 12:30:28,937 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-02-04 12:30:28,938 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-04 12:30:28,938 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:28,938 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-04 12:30:28,938 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-02-04 12:30:29,278 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:29,309 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:29,309 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:30,314 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-04 12:30:30,355 INFO spawned: 'cron' with pid 18
|
||||
2026-02-04 12:30:30,474 INFO spawned: 'nginx' with pid 19
|
||||
2026-02-04 12:30:30,579 INFO spawned: 'updater_reader' with pid 21
|
||||
2026-02-04 12:30:30,694 INFO spawned: 'updater_writer' with pid 22
|
||||
2026-02-04 12:30:30,963 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:30,963 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:30,963 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:30,963 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:30,963 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:30,964 INFO exited: nginx (exit status 0; expected)
|
||||
2026-02-04 13:34:02,459 INFO reaped unknown pid 88 (exit status 0)
|
||||
2026-02-04 14:57:35,637 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.
|
||||
2026-02-04 14:57:35,659 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-02-04 14:57:35,659 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-04 14:57:35,659 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:35,659 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-04 14:57:35,659 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-02-04 14:57:36,004 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:36,004 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:36,022 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:37,037 INFO spawned: 'mesh' with pid 23
|
||||
2026-02-04 14:57:37,061 INFO spawned: 'cron' with pid 24
|
||||
2026-02-04 14:57:37,171 INFO spawned: 'nginx' with pid 25
|
||||
2026-02-04 14:57:37,205 INFO spawned: 'updater_reader' with pid 27
|
||||
2026-02-04 14:57:37,326 INFO spawned: 'updater_writer' with pid 28
|
||||
2026-02-04 14:57:37,452 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,470 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,470 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,470 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,470 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,470 INFO exited: nginx (exit status 0; expected)
|
||||
2026-02-04 17:30:50,782 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.
|
||||
2026-02-04 17:30:50,788 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-02-04 17:30:50,788 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-04 17:30:50,788 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:50,788 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-04 17:30:50,788 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-02-04 17:30:51,125 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:51,125 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:51,125 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:52,146 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 17:30:52,262 INFO spawned: 'cron' with pid 17
|
||||
2026-02-04 17:30:52,347 INFO spawned: 'nginx' with pid 18
|
||||
2026-02-04 17:30:52,508 INFO spawned: 'updater_reader' with pid 20
|
||||
2026-02-04 17:30:52,623 INFO spawned: 'updater_writer' with pid 21
|
||||
2026-02-04 17:30:52,838 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,839 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,839 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,839 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,839 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,846 INFO exited: nginx (exit status 0; expected)
|
||||
2026-02-07 14:26:19,580 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.
|
||||
2026-02-07 14:26:19,602 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-02-07 14:26:19,602 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-07 14:26:19,602 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:19,602 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-07 14:26:19,602 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-02-07 14:26:19,952 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:19,979 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:19,979 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:20,987 INFO spawned: 'mesh' with pid 23
|
||||
2026-02-07 14:26:21,066 INFO spawned: 'cron' with pid 24
|
||||
2026-02-07 14:26:21,142 INFO spawned: 'nginx' with pid 25
|
||||
2026-02-07 14:26:21,181 INFO spawned: 'updater_reader' with pid 27
|
||||
2026-02-07 14:26:21,295 INFO spawned: 'updater_writer' with pid 30
|
||||
2026-02-07 14:26:21,599 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:21,599 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:21,599 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:21,599 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:21,599 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:21,599 INFO exited: nginx (exit status 0; expected)
|
||||
2026-02-07 15:21:01,811 INFO reaped unknown pid 101 (exit status 0)
|
||||
2026-02-20 16:02:20,352 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.
|
||||
2026-02-20 16:02:20,375 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-02-20 16:02:20,375 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-02-20 16:02:20,375 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:20,375 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-02-20 16:02:20,375 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-02-20 16:02:20,731 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:20,751 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:20,751 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:21,780 INFO spawned: 'mesh' with pid 17
|
||||
2026-02-20 16:02:21,817 INFO spawned: 'cron' with pid 18
|
||||
2026-02-20 16:02:21,869 INFO spawned: 'nginx' with pid 19
|
||||
2026-02-20 16:02:21,951 INFO spawned: 'updater_reader' with pid 23
|
||||
2026-02-20 16:02:22,028 INFO spawned: 'updater_writer' with pid 24
|
||||
2026-02-20 16:02:22,228 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,228 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,228 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,228 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,228 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:22,228 INFO exited: nginx (exit status 0; expected)
|
||||
2026-02-20 17:33:02,159 INFO reaped unknown pid 102 (exit status 0)
|
||||
2026-03-04 12:10:31,102 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.
|
||||
2026-03-04 12:10:31,113 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-03-04 12:10:31,118 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-03-04 12:10:31,118 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:31,118 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-03-04 12:10:31,118 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-03-04 12:10:31,448 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,467 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,468 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,490 INFO spawned: 'mesh' with pid 23
|
||||
2026-03-04 12:10:32,609 INFO spawned: 'cron' with pid 24
|
||||
2026-03-04 12:10:32,633 INFO spawned: 'nginx' with pid 25
|
||||
2026-03-04 12:10:32,815 INFO spawned: 'updater_reader' with pid 29
|
||||
2026-03-04 12:10:32,914 INFO spawned: 'updater_writer' with pid 30
|
||||
2026-03-04 12:10:33,209 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,210 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,210 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,210 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,210 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,210 INFO exited: nginx (exit status 0; expected)
|
||||
2026-03-04 14:10:02,375 INFO reaped unknown pid 108 (exit status 0)
|
||||
2026-03-23 09:52:44,885 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.
|
||||
2026-03-23 09:52:44,909 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-03-23 09:52:44,909 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-03-23 09:52:44,909 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,909 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-03-23 09:52:44,909 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-03-23 09:52:45,244 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:45,244 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:45,259 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:46,272 INFO spawned: 'mesh' with pid 26
|
||||
2026-03-23 09:52:46,380 INFO spawned: 'cron' with pid 27
|
||||
2026-03-23 09:52:46,447 INFO spawned: 'nginx' with pid 28
|
||||
2026-03-23 09:52:46,597 INFO spawned: 'updater_reader' with pid 30
|
||||
2026-03-23 09:52:46,667 INFO spawned: 'updater_writer' with pid 31
|
||||
2026-03-23 09:52:46,919 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,919 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,919 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,919 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,919 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,919 INFO exited: nginx (exit status 0; expected)
|
||||
2026-03-23 10:39:02,406 INFO reaped unknown pid 90 (exit status 0)
|
||||
2026-03-25 17:35:22,727 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.
|
||||
2026-03-25 17:35:22,731 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-03-25 17:35:22,731 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-03-25 17:35:22,731 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:22,731 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-03-25 17:35:22,731 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-03-25 17:35:23,078 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:23,109 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:23,109 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:24,122 INFO spawned: 'mesh' with pid 17
|
||||
2026-03-25 17:35:24,183 INFO spawned: 'cron' with pid 18
|
||||
2026-03-25 17:35:24,281 INFO spawned: 'nginx' with pid 19
|
||||
2026-03-25 17:35:24,422 INFO spawned: 'updater_reader' with pid 21
|
||||
2026-03-25 17:35:24,491 INFO spawned: 'updater_writer' with pid 24
|
||||
2026-03-25 17:35:24,790 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:24,854 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:24,854 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:24,854 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:24,854 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:24,854 INFO exited: nginx (exit status 0; expected)
|
||||
2026-03-25 18:08:02,329 INFO reaped unknown pid 88 (exit status 0)
|
||||
2026-03-26 07:04:03,122 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.
|
||||
2026-03-26 07:04:03,151 INFO Included extra file "/opt/supervisor.d/cron.astra.conf" during parsing
|
||||
2026-03-26 07:04:03,151 INFO Included extra file "/opt/supervisor.d/cron.conf" during parsing
|
||||
2026-03-26 07:04:03,151 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,151 INFO Included extra file "/opt/supervisor.d/nginx.conf" during parsing
|
||||
2026-03-26 07:04:03,151 INFO Included extra file "/opt/supervisor.d/updater.conf" during parsing
|
||||
2026-03-26 07:04:03,521 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,521 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,521 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,550 INFO spawned: 'mesh' with pid 20
|
||||
2026-03-26 07:04:04,576 INFO spawned: 'cron' with pid 21
|
||||
2026-03-26 07:04:04,726 INFO spawned: 'nginx' with pid 22
|
||||
2026-03-26 07:04:04,804 INFO spawned: 'updater_reader' with pid 26
|
||||
2026-03-26 07:04:04,898 INFO spawned: 'updater_writer' with pid 28
|
||||
2026-03-26 07:04:04,958 INFO exited: nginx (exit status 0; expected)
|
||||
2026-03-26 07:04:06,014 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,014 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,014 INFO success: updater_reader entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,014 INFO success: updater_writer entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,436 @@
|
||||
2025-11-12 08:50:14,211 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.
|
||||
2025-11-12 08:50:14,211 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:14,219 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-11-12 08:50:14,229 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:14,230 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:14,236 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:15,250 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-12 08:50:15,301 INFO spawned: 'vault' with pid 17
|
||||
2025-11-12 08:50:16,337 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:16,339 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,997 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.
|
||||
2025-11-17 12:01:29,999 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:29,999 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-11-17 12:01:30,358 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:30,379 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:30,379 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:31,391 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-17 12:01:31,466 INFO spawned: 'vault' with pid 17
|
||||
2025-11-17 12:01:32,471 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:32,471 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:35,487 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.
|
||||
2025-11-21 15:30:35,493 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:35,493 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-11-21 15:30:35,838 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:35,838 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:35,838 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:36,851 INFO spawned: 'mesh' with pid 25
|
||||
2025-11-21 15:30:36,880 INFO spawned: 'vault' with pid 26
|
||||
2025-11-21 15:30:37,901 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:37,901 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:47,189 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.
|
||||
2025-11-22 15:19:47,195 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:47,195 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-11-22 15:19:47,608 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,613 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,617 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,623 INFO spawned: 'mesh' with pid 15
|
||||
2025-11-22 15:19:48,725 INFO spawned: 'vault' with pid 16
|
||||
2025-11-22 15:19:49,750 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:49,751 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:06,237 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:28:06,256 INFO waiting for mesh, vault to die
|
||||
2025-11-22 15:28:06,433 WARN stopped: vault (terminated by SIGABRT (core dumped))
|
||||
2025-11-22 15:28:06,578 WARN stopped: mesh (terminated by SIGABRT (core dumped))
|
||||
2025-11-22 15:28:27,333 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.
|
||||
2025-11-22 15:28:27,333 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:27,333 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-11-22 15:28:27,362 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:27,363 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:27,363 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:28,382 INFO spawned: 'mesh' with pid 15
|
||||
2025-11-22 15:28:28,401 INFO spawned: 'vault' with pid 16
|
||||
2025-11-22 15:28:29,416 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:29,416 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:53,163 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:53,166 INFO waiting for mesh, vault to die
|
||||
2025-11-22 15:30:53,188 INFO stopped: vault (exit status 0)
|
||||
2025-11-22 15:30:53,199 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:13,112 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.
|
||||
2025-11-22 15:31:13,114 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:13,114 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-11-22 15:31:13,124 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:13,125 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:13,125 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:14,141 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:31:14,161 INFO spawned: 'vault' with pid 17
|
||||
2025-11-22 15:31:15,176 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:15,176 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:50,436 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:50,462 INFO waiting for mesh, vault to die
|
||||
2025-11-22 15:37:50,492 INFO stopped: vault (exit status 0)
|
||||
2025-11-22 15:37:50,500 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:28,288 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.
|
||||
2025-11-22 15:38:28,288 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:28,288 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-11-22 15:38:28,356 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:28,356 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:28,357 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:29,381 INFO spawned: 'mesh' with pid 16
|
||||
2025-11-22 15:38:29,407 INFO spawned: 'vault' with pid 17
|
||||
2025-11-22 15:38:30,433 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:30,433 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:24,690 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.
|
||||
2025-11-25 15:48:24,694 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:24,694 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-11-25 15:48:25,030 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:25,030 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:25,030 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:26,045 INFO spawned: 'mesh' with pid 19
|
||||
2025-11-25 15:48:26,085 INFO spawned: 'vault' with pid 20
|
||||
2025-11-25 15:48:27,086 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:27,086 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:23,789 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.
|
||||
2025-12-07 15:52:23,797 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:23,797 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-12-07 15:52:24,145 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:24,163 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:24,163 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:25,171 INFO spawned: 'mesh' with pid 19
|
||||
2025-12-07 15:52:25,240 INFO spawned: 'vault' with pid 20
|
||||
2025-12-07 15:52:26,282 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:26,282 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:34,281 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.
|
||||
2025-12-08 11:39:34,286 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:34,286 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-12-08 11:39:34,618 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:34,618 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:34,621 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:35,627 INFO spawned: 'mesh' with pid 15
|
||||
2025-12-08 11:39:35,661 INFO spawned: 'vault' with pid 16
|
||||
2025-12-08 11:39:36,706 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:36,706 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:42,503 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.
|
||||
2025-12-11 15:42:42,504 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:42,504 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-12-11 15:42:42,837 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:42,837 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:42,838 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:43,847 INFO spawned: 'mesh' with pid 22
|
||||
2025-12-11 15:42:43,863 INFO spawned: 'vault' with pid 23
|
||||
2025-12-11 15:42:44,879 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:44,879 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:25,707 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.
|
||||
2025-12-14 06:18:25,709 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:25,709 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-12-14 06:18:26,037 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:26,039 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:26,040 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:27,049 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-14 06:18:27,101 INFO spawned: 'vault' with pid 17
|
||||
2025-12-14 06:18:28,113 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:28,113 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:31,471 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.
|
||||
2025-12-15 18:35:31,485 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:31,486 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-12-15 18:35:31,823 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:31,823 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:31,823 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:32,860 INFO spawned: 'mesh' with pid 22
|
||||
2025-12-15 18:35:32,926 INFO spawned: 'vault' with pid 23
|
||||
2025-12-15 18:35:33,958 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:33,958 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:59,667 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.
|
||||
2025-12-18 15:22:59,671 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:59,671 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2025-12-18 15:23:00,099 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:23:00,099 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:23:00,099 INFO supervisord started with pid 1
|
||||
2025-12-18 15:23:01,117 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-18 15:23:01,144 INFO spawned: 'vault' with pid 17
|
||||
2025-12-18 15:23:02,176 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:02,177 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:09,976 WARN exited: vault (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:09,980 INFO reaped unknown pid 28 (exit status 0)
|
||||
2025-12-18 20:53:10,107 INFO spawned: 'vault' with pid 33
|
||||
2025-12-18 20:53:10,108 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:10,567 INFO spawned: 'mesh' with pid 35
|
||||
2025-12-18 20:53:10,610 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,610 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:10,671 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,686 INFO spawned: 'vault' with pid 36
|
||||
2025-12-18 20:53:10,956 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:10,956 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:10,956 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:10,977 INFO spawned: 'mesh' with pid 39
|
||||
2025-12-18 20:53:11,083 INFO spawned: 'vault' with pid 40
|
||||
2025-12-18 20:53:11,290 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,290 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,290 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,441 INFO spawned: 'mesh' with pid 43
|
||||
2025-12-18 20:53:11,442 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,445 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,465 INFO spawned: 'vault' with pid 44
|
||||
2025-12-18 20:53:11,627 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,628 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,641 INFO spawned: 'mesh' with pid 47
|
||||
2025-12-18 20:53:11,659 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,661 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,683 INFO spawned: 'vault' with pid 48
|
||||
2025-12-18 20:53:11,788 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,793 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,828 INFO spawned: 'vault' with pid 51
|
||||
2025-12-18 20:53:11,850 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:11,975 INFO spawned: 'mesh' with pid 53
|
||||
2025-12-18 20:53:11,986 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:11,991 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:11,993 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,021 INFO spawned: 'vault' with pid 54
|
||||
2025-12-18 20:53:12,113 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,113 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,121 INFO spawned: 'vault' with pid 57
|
||||
2025-12-18 20:53:12,167 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,173 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,192 INFO spawned: 'mesh' with pid 59
|
||||
2025-12-18 20:53:12,196 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,198 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,223 INFO spawned: 'vault' with pid 60
|
||||
2025-12-18 20:53:12,450 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,450 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,456 INFO spawned: 'mesh' with pid 63
|
||||
2025-12-18 20:53:12,477 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,477 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,494 INFO spawned: 'vault' with pid 64
|
||||
2025-12-18 20:53:12,630 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,636 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,660 INFO spawned: 'mesh' with pid 67
|
||||
2025-12-18 20:53:12,673 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,673 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,685 INFO spawned: 'vault' with pid 68
|
||||
2025-12-18 20:53:12,845 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,845 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:12,872 INFO spawned: 'mesh' with pid 71
|
||||
2025-12-18 20:53:12,873 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:12,879 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:12,899 INFO spawned: 'vault' with pid 72
|
||||
2025-12-18 20:53:13,068 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,068 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,091 INFO spawned: 'mesh' with pid 75
|
||||
2025-12-18 20:53:13,100 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,103 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,127 INFO spawned: 'vault' with pid 76
|
||||
2025-12-18 20:53:13,293 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,294 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,309 INFO spawned: 'mesh' with pid 79
|
||||
2025-12-18 20:53:13,322 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,343 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,349 INFO spawned: 'vault' with pid 80
|
||||
2025-12-18 20:53:13,478 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:13,519 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:13,535 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:13,573 INFO spawned: 'mesh' with pid 83
|
||||
2025-12-18 20:53:13,606 INFO spawned: 'vault' with pid 84
|
||||
2025-12-18 20:53:14,018 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,018 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,018 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,151 INFO spawned: 'mesh' with pid 87
|
||||
2025-12-18 20:53:14,154 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,160 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,225 INFO spawned: 'vault' with pid 88
|
||||
2025-12-18 20:53:14,639 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,640 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:14,706 INFO spawned: 'mesh' with pid 91
|
||||
2025-12-18 20:53:14,707 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:14,760 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,821 INFO spawned: 'vault' with pid 92
|
||||
2025-12-18 20:53:15,100 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,125 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,140 INFO spawned: 'mesh' with pid 95
|
||||
2025-12-18 20:53:15,181 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,181 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,215 INFO spawned: 'vault' with pid 96
|
||||
2025-12-18 20:53:15,348 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,352 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,374 INFO spawned: 'vault' with pid 99
|
||||
2025-12-18 20:53:15,492 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,496 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,507 INFO spawned: 'vault' with pid 101
|
||||
2025-12-18 20:53:15,508 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,520 INFO spawned: 'mesh' with pid 102
|
||||
2025-12-18 20:53:15,542 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,703 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,703 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,755 INFO spawned: 'mesh' with pid 105
|
||||
2025-12-18 20:53:15,788 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:15,788 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,814 INFO spawned: 'vault' with pid 106
|
||||
2025-12-18 20:53:16,123 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,123 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,139 INFO spawned: 'mesh' with pid 109
|
||||
2025-12-18 20:53:16,159 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,189 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,217 INFO spawned: 'vault' with pid 110
|
||||
2025-12-18 20:53:16,492 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,492 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,516 INFO spawned: 'mesh' with pid 113
|
||||
2025-12-18 20:53:16,517 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,517 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,582 INFO spawned: 'vault' with pid 114
|
||||
2025-12-18 20:53:16,749 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,750 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:16,841 INFO spawned: 'mesh' with pid 117
|
||||
2025-12-18 20:53:16,842 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:16,842 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,867 INFO spawned: 'vault' with pid 118
|
||||
2025-12-18 20:53:17,064 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,064 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,111 INFO spawned: 'vault' with pid 121
|
||||
2025-12-18 20:53:17,112 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,253 INFO spawned: 'mesh' with pid 123
|
||||
2025-12-18 20:53:17,264 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,265 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,265 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,297 INFO spawned: 'vault' with pid 124
|
||||
2025-12-18 20:53:17,530 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,536 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,547 INFO spawned: 'mesh' with pid 127
|
||||
2025-12-18 20:53:17,561 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,565 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,585 INFO spawned: 'vault' with pid 128
|
||||
2025-12-18 20:53:17,848 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,848 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,893 INFO spawned: 'mesh' with pid 131
|
||||
2025-12-18 20:53:17,893 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:17,894 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:17,936 INFO spawned: 'vault' with pid 132
|
||||
2025-12-18 20:53:18,201 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,205 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,207 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,213 INFO spawned: 'mesh' with pid 135
|
||||
2025-12-18 20:53:18,260 INFO spawned: 'vault' with pid 136
|
||||
2025-12-18 20:53:18,533 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,547 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,549 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:18,571 INFO spawned: 'mesh' with pid 139
|
||||
2025-12-18 20:53:18,593 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,593 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,628 INFO spawned: 'vault' with pid 140
|
||||
2025-12-18 20:53:18,871 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,871 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:18,902 INFO spawned: 'vault' with pid 143
|
||||
2025-12-18 20:53:18,931 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:18,939 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,057 INFO spawned: 'mesh' with pid 145
|
||||
2025-12-18 20:53:19,100 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,100 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,277 INFO spawned: 'vault' with pid 147
|
||||
2025-12-18 20:53:19,277 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,546 INFO spawned: 'mesh' with pid 149
|
||||
2025-12-18 20:53:19,547 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,547 WARN exited: vault (exit status 1; not expected)
|
||||
2025-12-18 20:53:19,590 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,614 INFO spawned: 'vault' with pid 150
|
||||
2025-12-18 20:53:19,737 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,762 INFO waiting for mesh, vault to die
|
||||
2025-12-18 20:53:19,808 WARN exited: mesh (terminated by SIGTERM; not expected)
|
||||
2025-12-18 20:53:19,990 WARN stopped: vault (exit status 1)
|
||||
2026-01-25 19:02:20,028 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.
|
||||
2026-01-25 19:02:20,034 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:20,034 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-01-25 19:02:20,080 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:20,080 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:20,081 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:21,089 INFO spawned: 'mesh' with pid 16
|
||||
2026-01-25 19:02:21,175 INFO spawned: 'vault' with pid 17
|
||||
2026-01-25 19:02:22,258 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:22,258 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:28,343 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.
|
||||
2026-02-04 12:30:28,350 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:28,350 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-02-04 12:30:28,723 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:28,723 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:28,728 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:29,742 INFO spawned: 'mesh' with pid 16
|
||||
2026-02-04 12:30:29,824 INFO spawned: 'vault' with pid 17
|
||||
2026-02-04 12:30:30,832 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:30,832 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:34,802 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.
|
||||
2026-02-04 14:57:34,823 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:34,823 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-02-04 14:57:35,162 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:35,191 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:35,191 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:36,199 INFO spawned: 'mesh' with pid 24
|
||||
2026-02-04 14:57:36,261 INFO spawned: 'vault' with pid 25
|
||||
2026-02-04 14:57:37,270 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:37,270 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:57,090 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.
|
||||
2026-02-04 17:30:57,109 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:57,109 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-02-04 17:30:57,438 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:57,440 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:57,442 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:58,460 INFO spawned: 'mesh' with pid 15
|
||||
2026-02-04 17:30:58,561 INFO spawned: 'vault' with pid 16
|
||||
2026-02-04 17:30:59,588 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:59,588 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:19,974 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.
|
||||
2026-02-07 14:26:19,977 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:19,977 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-02-07 14:26:20,326 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,327 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,327 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,346 INFO spawned: 'mesh' with pid 24
|
||||
2026-02-07 14:26:21,401 INFO spawned: 'vault' with pid 25
|
||||
2026-02-07 14:26:22,451 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,452 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:20,863 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.
|
||||
2026-02-20 16:02:20,872 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:20,872 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-02-20 16:02:21,230 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,231 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,231 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,240 INFO spawned: 'mesh' with pid 25
|
||||
2026-02-20 16:02:22,283 INFO spawned: 'vault' with pid 26
|
||||
2026-02-20 16:02:23,350 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,351 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:30,970 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.
|
||||
2026-03-04 12:10:30,972 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:30,972 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-03-04 12:10:31,316 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:31,316 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:31,316 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:32,326 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-04 12:10:32,365 INFO spawned: 'vault' with pid 23
|
||||
2026-03-04 12:10:33,452 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:33,452 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:44,151 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.
|
||||
2026-03-23 09:52:44,171 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:44,171 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-03-23 09:52:44,524 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:44,551 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:44,551 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:45,557 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-23 09:52:45,615 INFO spawned: 'vault' with pid 23
|
||||
2026-03-23 09:52:46,624 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:46,624 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:19,395 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.
|
||||
2026-03-25 17:35:19,406 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:19,407 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-03-25 17:35:19,751 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:19,751 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:19,751 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:20,767 INFO spawned: 'mesh' with pid 16
|
||||
2026-03-25 17:35:20,842 INFO spawned: 'vault' with pid 17
|
||||
2026-03-25 17:35:21,846 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:21,846 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:03,596 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.
|
||||
2026-03-26 07:04:03,604 INFO Included extra file "/opt/supervisor.d/mesh.conf" during parsing
|
||||
2026-03-26 07:04:03,604 INFO Included extra file "/opt/supervisor.d/vault.conf" during parsing
|
||||
2026-03-26 07:04:03,928 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:04:03,943 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:04:03,943 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:04,946 INFO spawned: 'mesh' with pid 22
|
||||
2026-03-26 07:04:05,037 INFO spawned: 'vault' with pid 23
|
||||
2026-03-26 07:04:06,045 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:06,045 INFO success: vault entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
@@ -0,0 +1,545 @@
|
||||
2025-11-12 08:50:14,264 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.
|
||||
2025-11-12 08:50:14,264 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-12 08:50:14,264 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-11-12 08:50:14,264 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-11-12 08:50:14,283 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-12 08:50:14,284 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-12 08:50:14,284 INFO supervisord started with pid 1
|
||||
2025-11-12 08:50:15,299 INFO spawned: 'mesh' with pid 7
|
||||
2025-11-12 08:50:15,356 INFO spawned: 'tunnel' with pid 8
|
||||
2025-11-12 08:50:15,417 INFO spawned: 'victoria' with pid 9
|
||||
2025-11-12 08:50:15,559 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:15,559 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:15,559 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-12 08:50:27,431 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-12 08:50:28,458 INFO spawned: 'tunnel' with pid 21
|
||||
2025-11-12 08:50:29,462 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:28,054 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.
|
||||
2025-11-17 12:01:28,059 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-17 12:01:28,063 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-11-17 12:01:28,063 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-11-17 12:01:28,399 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-17 12:01:28,399 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-17 12:01:28,411 INFO supervisord started with pid 1
|
||||
2025-11-17 12:01:29,436 INFO spawned: 'mesh' with pid 7
|
||||
2025-11-17 12:01:29,509 INFO spawned: 'tunnel' with pid 8
|
||||
2025-11-17 12:01:29,637 INFO spawned: 'victoria' with pid 9
|
||||
2025-11-17 12:01:29,782 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,783 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:29,783 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-17 12:01:43,120 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-17 12:01:43,139 INFO spawned: 'tunnel' with pid 21
|
||||
2025-11-17 12:01:44,160 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:27,875 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.
|
||||
2025-11-21 15:30:27,876 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-21 15:30:27,876 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-11-21 15:30:27,876 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-11-21 15:30:28,192 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-21 15:30:28,192 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-21 15:30:28,194 INFO supervisord started with pid 1
|
||||
2025-11-21 15:30:29,205 INFO spawned: 'mesh' with pid 7
|
||||
2025-11-21 15:30:29,230 INFO spawned: 'tunnel' with pid 8
|
||||
2025-11-21 15:30:29,244 INFO spawned: 'victoria' with pid 9
|
||||
2025-11-21 15:30:29,272 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:29,274 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:29,274 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:30,471 INFO exited: mesh (exit status 0; expected)
|
||||
2025-11-21 15:30:30,475 INFO spawned: 'mesh' with pid 18
|
||||
2025-11-21 15:30:30,550 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:40,714 INFO exited: mesh (exit status 0; expected)
|
||||
2025-11-21 15:30:40,740 INFO spawned: 'mesh' with pid 22
|
||||
2025-11-21 15:30:40,782 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-21 15:30:41,322 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-21 15:30:42,338 INFO spawned: 'tunnel' with pid 26
|
||||
2025-11-21 15:30:43,360 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:46,683 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.
|
||||
2025-11-22 15:19:46,688 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:19:46,688 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-11-22 15:19:46,688 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-11-22 15:19:47,160 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:19:47,187 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:19:47,187 INFO supervisord started with pid 1
|
||||
2025-11-22 15:19:48,238 INFO spawned: 'mesh' with pid 7
|
||||
2025-11-22 15:19:48,295 INFO spawned: 'tunnel' with pid 8
|
||||
2025-11-22 15:19:48,354 INFO spawned: 'victoria' with pid 9
|
||||
2025-11-22 15:19:48,702 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,702 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:19:48,702 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:20:01,745 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:20:02,752 INFO spawned: 'tunnel' with pid 21
|
||||
2025-11-22 15:20:03,775 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:27:57,348 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:27:57,350 INFO waiting for mesh, tunnel, victoria to die
|
||||
2025-11-22 15:27:57,415 INFO stopped: victoria (exit status 0)
|
||||
2025-11-22 15:27:57,564 INFO stopped: tunnel (exit status 0)
|
||||
2025-11-22 15:27:58,203 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:28:18,165 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.
|
||||
2025-11-22 15:28:18,165 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:28:18,165 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-11-22 15:28:18,166 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-11-22 15:28:18,184 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:28:18,184 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:28:18,184 INFO supervisord started with pid 1
|
||||
2025-11-22 15:28:19,198 INFO spawned: 'mesh' with pid 6
|
||||
2025-11-22 15:28:19,205 INFO spawned: 'tunnel' with pid 7
|
||||
2025-11-22 15:28:19,243 INFO spawned: 'victoria' with pid 11
|
||||
2025-11-22 15:28:19,274 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:19,274 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:19,274 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:30,581 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:28:31,583 INFO spawned: 'tunnel' with pid 20
|
||||
2025-11-22 15:28:32,633 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:28:44,278 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:28:45,281 INFO spawned: 'tunnel' with pid 23
|
||||
2025-11-22 15:28:46,290 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:29:17,617 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:29:18,631 INFO spawned: 'tunnel' with pid 26
|
||||
2025-11-22 15:29:19,649 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:29:49,369 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:29:50,374 INFO spawned: 'tunnel' with pid 29
|
||||
2025-11-22 15:29:51,376 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:30:46,433 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:30:46,435 INFO waiting for mesh, tunnel, victoria to die
|
||||
2025-11-22 15:30:46,689 INFO stopped: victoria (exit status 0)
|
||||
2025-11-22 15:30:47,219 INFO stopped: tunnel (exit status 0)
|
||||
2025-11-22 15:30:47,372 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:31:08,939 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.
|
||||
2025-11-22 15:31:08,939 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:31:08,939 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-11-22 15:31:08,939 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-11-22 15:31:08,943 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:31:08,944 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:31:08,944 INFO supervisord started with pid 1
|
||||
2025-11-22 15:31:09,949 INFO spawned: 'mesh' with pid 6
|
||||
2025-11-22 15:31:09,965 INFO spawned: 'tunnel' with pid 7
|
||||
2025-11-22 15:31:10,005 INFO spawned: 'victoria' with pid 11
|
||||
2025-11-22 15:31:10,035 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:10,036 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:10,036 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:21,386 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:31:22,389 INFO spawned: 'tunnel' with pid 21
|
||||
2025-11-22 15:31:23,544 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:31:34,716 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:31:34,734 INFO spawned: 'tunnel' with pid 24
|
||||
2025-11-22 15:31:35,754 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:37:43,205 WARN received SIGTERM indicating exit request
|
||||
2025-11-22 15:37:43,207 INFO waiting for mesh, tunnel, victoria to die
|
||||
2025-11-22 15:37:43,550 INFO stopped: victoria (exit status 0)
|
||||
2025-11-22 15:37:43,974 INFO stopped: tunnel (exit status 0)
|
||||
2025-11-22 15:37:44,223 INFO stopped: mesh (exit status 0)
|
||||
2025-11-22 15:38:17,075 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.
|
||||
2025-11-22 15:38:17,076 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-22 15:38:17,076 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-11-22 15:38:17,076 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-11-22 15:38:17,090 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-22 15:38:17,090 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-22 15:38:17,090 INFO supervisord started with pid 1
|
||||
2025-11-22 15:38:18,097 INFO spawned: 'mesh' with pid 7
|
||||
2025-11-22 15:38:18,106 INFO spawned: 'tunnel' with pid 8
|
||||
2025-11-22 15:38:18,125 INFO spawned: 'victoria' with pid 9
|
||||
2025-11-22 15:38:18,140 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:18,143 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:18,145 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:30,360 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:38:31,363 INFO spawned: 'tunnel' with pid 21
|
||||
2025-11-22 15:38:32,432 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:38:43,624 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:38:44,632 INFO spawned: 'tunnel' with pid 24
|
||||
2025-11-22 15:38:45,636 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:39:16,620 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:39:17,627 INFO spawned: 'tunnel' with pid 27
|
||||
2025-11-22 15:39:18,633 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-22 15:39:48,123 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-22 15:39:49,128 INFO spawned: 'tunnel' with pid 30
|
||||
2025-11-22 15:39:50,133 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:30,312 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.
|
||||
2025-11-25 15:48:30,316 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-11-25 15:48:30,317 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-11-25 15:48:30,317 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-11-25 15:48:30,686 INFO RPC interface 'supervisor' initialized
|
||||
2025-11-25 15:48:30,686 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-11-25 15:48:30,690 INFO supervisord started with pid 1
|
||||
2025-11-25 15:48:31,732 INFO spawned: 'mesh' with pid 7
|
||||
2025-11-25 15:48:31,790 INFO spawned: 'tunnel' with pid 8
|
||||
2025-11-25 15:48:31,872 INFO spawned: 'victoria' with pid 9
|
||||
2025-11-25 15:48:32,089 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:32,089 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:32,089 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:48:45,491 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-25 15:48:45,512 INFO spawned: 'tunnel' with pid 21
|
||||
2025-11-25 15:48:46,526 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:49:18,088 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-25 15:49:19,092 INFO spawned: 'tunnel' with pid 24
|
||||
2025-11-25 15:49:20,101 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-11-25 15:49:49,980 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-11-25 15:49:50,983 INFO spawned: 'tunnel' with pid 27
|
||||
2025-11-25 15:49:51,985 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:19,703 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.
|
||||
2025-12-07 15:52:19,704 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-07 15:52:19,705 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-12-07 15:52:19,705 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-12-07 15:52:20,048 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-07 15:52:20,048 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-07 15:52:20,048 INFO supervisord started with pid 1
|
||||
2025-12-07 15:52:21,123 INFO spawned: 'mesh' with pid 7
|
||||
2025-12-07 15:52:21,211 INFO spawned: 'tunnel' with pid 8
|
||||
2025-12-07 15:52:21,313 INFO spawned: 'victoria' with pid 9
|
||||
2025-12-07 15:52:21,686 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:21,686 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:21,686 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:52:35,593 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-07 15:52:35,637 INFO spawned: 'tunnel' with pid 21
|
||||
2025-12-07 15:52:36,680 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:53:07,631 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-07 15:53:08,644 INFO spawned: 'tunnel' with pid 24
|
||||
2025-12-07 15:53:09,648 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-07 15:53:40,500 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-07 15:53:41,502 INFO spawned: 'tunnel' with pid 27
|
||||
2025-12-07 15:53:42,511 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:29,252 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.
|
||||
2025-12-08 11:39:29,253 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-08 11:39:29,253 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-12-08 11:39:29,253 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-12-08 11:39:29,566 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-08 11:39:29,566 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-08 11:39:29,568 INFO supervisord started with pid 1
|
||||
2025-12-08 11:39:30,582 INFO spawned: 'mesh' with pid 7
|
||||
2025-12-08 11:39:30,618 INFO spawned: 'tunnel' with pid 8
|
||||
2025-12-08 11:39:30,663 INFO spawned: 'victoria' with pid 9
|
||||
2025-12-08 11:39:30,745 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:30,745 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:39:30,745 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:40:02,193 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-08 11:40:03,241 INFO spawned: 'tunnel' with pid 22
|
||||
2025-12-08 11:40:04,260 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:40:35,830 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-08 11:40:36,843 INFO spawned: 'tunnel' with pid 25
|
||||
2025-12-08 11:40:37,859 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-08 11:41:08,466 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-08 11:41:09,477 INFO spawned: 'tunnel' with pid 28
|
||||
2025-12-08 11:41:10,481 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:36,721 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.
|
||||
2025-12-11 15:42:36,722 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-11 15:42:36,722 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-12-11 15:42:36,722 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-12-11 15:42:37,042 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-11 15:42:37,042 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-11 15:42:37,042 INFO supervisord started with pid 1
|
||||
2025-12-11 15:42:38,061 INFO spawned: 'mesh' with pid 7
|
||||
2025-12-11 15:42:38,092 INFO spawned: 'tunnel' with pid 8
|
||||
2025-12-11 15:42:38,116 INFO spawned: 'victoria' with pid 9
|
||||
2025-12-11 15:42:38,179 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:38,180 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:38,180 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:38,367 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-11 15:42:38,666 INFO spawned: 'mesh' with pid 16
|
||||
2025-12-11 15:42:38,667 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:39,147 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-11 15:42:39,149 INFO spawned: 'mesh' with pid 19
|
||||
2025-12-11 15:42:39,193 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-11 15:42:51,957 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-11 15:42:52,959 INFO spawned: 'tunnel' with pid 25
|
||||
2025-12-11 15:42:54,031 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:19,131 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.
|
||||
2025-12-14 06:18:19,134 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-14 06:18:19,134 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-12-14 06:18:19,134 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-12-14 06:18:19,454 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-14 06:18:19,454 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-14 06:18:19,454 INFO supervisord started with pid 1
|
||||
2025-12-14 06:18:20,472 INFO spawned: 'mesh' with pid 7
|
||||
2025-12-14 06:18:20,499 INFO spawned: 'tunnel' with pid 8
|
||||
2025-12-14 06:18:20,545 INFO spawned: 'victoria' with pid 9
|
||||
2025-12-14 06:18:20,606 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:20,610 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:20,610 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:21,135 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-14 06:18:21,188 INFO spawned: 'mesh' with pid 17
|
||||
2025-12-14 06:18:21,190 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:21,514 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-14 06:18:21,555 INFO spawned: 'mesh' with pid 19
|
||||
2025-12-14 06:18:21,645 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:21,705 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-14 06:18:21,726 INFO spawned: 'mesh' with pid 21
|
||||
2025-12-14 06:18:21,805 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:22,012 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-14 06:18:22,055 INFO spawned: 'mesh' with pid 23
|
||||
2025-12-14 06:18:22,116 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:18:34,383 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-14 06:18:35,386 INFO spawned: 'tunnel' with pid 29
|
||||
2025-12-14 06:18:36,397 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:19:07,911 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-14 06:19:08,917 INFO spawned: 'tunnel' with pid 32
|
||||
2025-12-14 06:19:09,927 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-14 06:19:40,117 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-14 06:19:41,120 INFO spawned: 'tunnel' with pid 35
|
||||
2025-12-14 06:19:42,123 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:23,153 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.
|
||||
2025-12-15 18:35:23,154 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-15 18:35:23,154 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-12-15 18:35:23,154 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-12-15 18:35:23,464 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-15 18:35:23,464 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-15 18:35:23,464 INFO supervisord started with pid 1
|
||||
2025-12-15 18:35:24,473 INFO spawned: 'mesh' with pid 7
|
||||
2025-12-15 18:35:24,481 INFO spawned: 'tunnel' with pid 8
|
||||
2025-12-15 18:35:24,509 INFO spawned: 'victoria' with pid 9
|
||||
2025-12-15 18:35:24,575 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:24,575 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:24,575 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:35,696 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-15 18:35:35,762 INFO spawned: 'mesh' with pid 21
|
||||
2025-12-15 18:35:35,876 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-15 18:35:36,323 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-15 18:35:37,328 INFO spawned: 'tunnel' with pid 25
|
||||
2025-12-15 18:35:38,354 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:52,288 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.
|
||||
2025-12-18 15:22:52,304 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2025-12-18 15:22:52,304 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2025-12-18 15:22:52,304 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2025-12-18 15:22:52,637 INFO RPC interface 'supervisor' initialized
|
||||
2025-12-18 15:22:52,637 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2025-12-18 15:22:52,650 INFO supervisord started with pid 1
|
||||
2025-12-18 15:22:53,661 INFO spawned: 'mesh' with pid 7
|
||||
2025-12-18 15:22:53,706 INFO spawned: 'tunnel' with pid 8
|
||||
2025-12-18 15:22:53,756 INFO spawned: 'victoria' with pid 9
|
||||
2025-12-18 15:22:53,894 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:53,894 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:22:53,902 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 15:23:06,789 WARN exited: tunnel (exit status 1; not expected)
|
||||
2025-12-18 15:23:07,802 INFO spawned: 'tunnel' with pid 22
|
||||
2025-12-18 15:23:08,831 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:14,570 WARN exited: mesh (terminated by SIGABRT (core dumped); not expected)
|
||||
2025-12-18 20:53:15,583 INFO spawned: 'mesh' with pid 24
|
||||
2025-12-18 20:53:15,667 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:15,763 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:15,774 INFO spawned: 'mesh' with pid 26
|
||||
2025-12-18 20:53:15,874 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:16,961 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:17,987 INFO spawned: 'mesh' with pid 28
|
||||
2025-12-18 20:53:18,048 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,160 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:19,833 INFO spawned: 'mesh' with pid 30
|
||||
2025-12-18 20:53:19,886 WARN received SIGTERM indicating exit request
|
||||
2025-12-18 20:53:19,887 INFO waiting for mesh, tunnel, victoria to die
|
||||
2025-12-18 20:53:19,887 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2025-12-18 20:53:19,920 WARN stopped: victoria (terminated by SIGTERM)
|
||||
2025-12-18 20:53:20,243 INFO exited: mesh (exit status 0; expected)
|
||||
2025-12-18 20:53:21,165 WARN stopped: tunnel (exit status 1)
|
||||
2026-01-25 19:02:14,906 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.
|
||||
2026-01-25 19:02:14,910 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-01-25 19:02:14,910 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-01-25 19:02:14,910 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-01-25 19:02:14,921 INFO RPC interface 'supervisor' initialized
|
||||
2026-01-25 19:02:14,922 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-01-25 19:02:14,922 INFO supervisord started with pid 1
|
||||
2026-01-25 19:02:15,936 INFO spawned: 'mesh' with pid 7
|
||||
2026-01-25 19:02:15,964 INFO spawned: 'tunnel' with pid 8
|
||||
2026-01-25 19:02:16,003 INFO spawned: 'victoria' with pid 9
|
||||
2026-01-25 19:02:16,145 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:16,145 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:16,145 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:02:29,821 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-01-25 19:02:30,837 INFO spawned: 'tunnel' with pid 21
|
||||
2026-01-25 19:02:31,847 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:03:02,130 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-01-25 19:03:03,140 INFO spawned: 'tunnel' with pid 24
|
||||
2026-01-25 19:03:04,161 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-01-25 19:03:35,550 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-01-25 19:03:36,553 INFO spawned: 'tunnel' with pid 27
|
||||
2026-01-25 19:03:37,555 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:23,805 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.
|
||||
2026-02-04 12:30:23,806 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 12:30:23,806 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-02-04 12:30:23,806 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-02-04 12:30:24,131 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 12:30:24,131 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 12:30:24,131 INFO supervisord started with pid 1
|
||||
2026-02-04 12:30:25,158 INFO spawned: 'mesh' with pid 7
|
||||
2026-02-04 12:30:25,183 INFO spawned: 'tunnel' with pid 8
|
||||
2026-02-04 12:30:25,236 INFO spawned: 'victoria' with pid 9
|
||||
2026-02-04 12:30:25,388 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,390 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:25,390 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:30:38,507 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 12:30:39,519 INFO spawned: 'tunnel' with pid 21
|
||||
2026-02-04 12:30:40,573 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:31:13,283 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 12:31:14,288 INFO spawned: 'tunnel' with pid 24
|
||||
2026-02-04 12:31:15,311 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 12:31:46,175 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 12:31:47,179 INFO spawned: 'tunnel' with pid 27
|
||||
2026-02-04 12:31:48,185 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:26,814 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.
|
||||
2026-02-04 14:57:26,816 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 14:57:26,816 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-02-04 14:57:26,816 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-02-04 14:57:27,133 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 14:57:27,134 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 14:57:27,134 INFO supervisord started with pid 1
|
||||
2026-02-04 14:57:28,142 INFO spawned: 'mesh' with pid 8
|
||||
2026-02-04 14:57:28,162 INFO spawned: 'tunnel' with pid 9
|
||||
2026-02-04 14:57:28,199 INFO spawned: 'victoria' with pid 10
|
||||
2026-02-04 14:57:28,262 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:28,262 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:28,262 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,430 INFO exited: mesh (exit status 0; expected)
|
||||
2026-02-04 14:57:39,484 INFO spawned: 'mesh' with pid 21
|
||||
2026-02-04 14:57:39,526 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:39,927 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 14:57:40,012 INFO spawned: 'tunnel' with pid 25
|
||||
2026-02-04 14:57:41,040 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:57:52,063 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 14:57:53,086 INFO spawned: 'tunnel' with pid 28
|
||||
2026-02-04 14:57:54,123 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:58:24,715 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 14:58:25,726 INFO spawned: 'tunnel' with pid 31
|
||||
2026-02-04 14:58:26,759 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 14:58:56,647 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 14:58:57,652 INFO spawned: 'tunnel' with pid 34
|
||||
2026-02-04 14:58:58,653 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:52,213 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.
|
||||
2026-02-04 17:30:52,221 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-04 17:30:52,222 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-02-04 17:30:52,222 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-02-04 17:30:52,561 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-04 17:30:52,561 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-04 17:30:52,562 INFO supervisord started with pid 1
|
||||
2026-02-04 17:30:53,616 INFO spawned: 'mesh' with pid 7
|
||||
2026-02-04 17:30:53,700 INFO spawned: 'tunnel' with pid 8
|
||||
2026-02-04 17:30:53,770 INFO spawned: 'victoria' with pid 9
|
||||
2026-02-04 17:30:53,952 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,952 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:30:53,952 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:31:27,694 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 17:31:28,784 INFO spawned: 'tunnel' with pid 21
|
||||
2026-02-04 17:31:29,814 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-04 17:32:00,096 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-04 17:32:01,101 INFO spawned: 'tunnel' with pid 24
|
||||
2026-02-04 17:32:02,104 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:20,506 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.
|
||||
2026-02-07 14:26:20,523 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-07 14:26:20,523 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-02-07 14:26:20,523 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-02-07 14:26:20,870 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-07 14:26:20,870 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-07 14:26:20,871 INFO supervisord started with pid 1
|
||||
2026-02-07 14:26:21,888 INFO spawned: 'mesh' with pid 6
|
||||
2026-02-07 14:26:21,979 INFO spawned: 'tunnel' with pid 7
|
||||
2026-02-07 14:26:22,029 INFO spawned: 'victoria' with pid 8
|
||||
2026-02-07 14:26:22,196 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,197 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:22,197 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:35,279 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-07 14:26:35,309 INFO spawned: 'tunnel' with pid 20
|
||||
2026-02-07 14:26:36,321 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:26:48,122 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-07 14:26:49,131 INFO spawned: 'tunnel' with pid 23
|
||||
2026-02-07 14:26:50,142 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-07 14:27:20,216 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-02-07 14:27:20,227 INFO spawned: 'tunnel' with pid 26
|
||||
2026-02-07 14:27:21,229 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:21,335 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.
|
||||
2026-02-20 16:02:21,347 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-02-20 16:02:21,347 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-02-20 16:02:21,347 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-02-20 16:02:21,674 INFO RPC interface 'supervisor' initialized
|
||||
2026-02-20 16:02:21,692 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-02-20 16:02:21,694 INFO supervisord started with pid 1
|
||||
2026-02-20 16:02:22,722 INFO spawned: 'mesh' with pid 7
|
||||
2026-02-20 16:02:22,830 INFO spawned: 'tunnel' with pid 8
|
||||
2026-02-20 16:02:22,918 INFO spawned: 'victoria' with pid 9
|
||||
2026-02-20 16:02:23,141 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,141 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-02-20 16:02:23,141 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:21,901 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.
|
||||
2026-03-04 12:10:21,901 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-04 12:10:21,901 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-03-04 12:10:21,901 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-03-04 12:10:22,217 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-04 12:10:22,217 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-04 12:10:22,218 INFO supervisord started with pid 1
|
||||
2026-03-04 12:10:23,228 INFO spawned: 'mesh' with pid 7
|
||||
2026-03-04 12:10:23,267 INFO spawned: 'tunnel' with pid 8
|
||||
2026-03-04 12:10:23,284 INFO spawned: 'victoria' with pid 9
|
||||
2026-03-04 12:10:23,350 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:23,350 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:23,350 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,500 INFO exited: mesh (exit status 0; expected)
|
||||
2026-03-04 12:10:35,509 INFO spawned: 'mesh' with pid 20
|
||||
2026-03-04 12:10:35,550 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:10:35,948 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-04 12:10:36,018 INFO spawned: 'tunnel' with pid 24
|
||||
2026-03-04 12:10:36,021 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:11:07,818 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-04 12:11:08,824 INFO spawned: 'tunnel' with pid 27
|
||||
2026-03-04 12:11:09,833 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-04 12:11:40,099 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-04 12:11:41,102 INFO spawned: 'tunnel' with pid 30
|
||||
2026-03-04 12:11:42,103 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:38,712 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.
|
||||
2026-03-23 09:52:38,714 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-23 09:52:38,714 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-03-23 09:52:38,714 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-03-23 09:52:39,049 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-23 09:52:39,049 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-23 09:52:39,055 INFO supervisord started with pid 1
|
||||
2026-03-23 09:52:40,071 INFO spawned: 'mesh' with pid 7
|
||||
2026-03-23 09:52:40,108 INFO spawned: 'tunnel' with pid 8
|
||||
2026-03-23 09:52:40,151 INFO spawned: 'victoria' with pid 9
|
||||
2026-03-23 09:52:40,291 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:40,292 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:40,292 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:40,601 INFO exited: mesh (exit status 0; expected)
|
||||
2026-03-23 09:52:40,941 INFO spawned: 'mesh' with pid 17
|
||||
2026-03-23 09:52:40,977 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:41,373 INFO exited: mesh (exit status 0; expected)
|
||||
2026-03-23 09:52:41,438 INFO spawned: 'mesh' with pid 19
|
||||
2026-03-23 09:52:41,493 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:52:54,373 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-23 09:52:55,382 INFO spawned: 'tunnel' with pid 25
|
||||
2026-03-23 09:52:56,430 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:53:28,154 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-23 09:53:29,161 INFO spawned: 'tunnel' with pid 28
|
||||
2026-03-23 09:53:30,180 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-23 09:54:01,282 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-23 09:54:02,287 INFO spawned: 'tunnel' with pid 31
|
||||
2026-03-23 09:54:03,291 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:10,122 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.
|
||||
2026-03-25 17:35:10,125 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-25 17:35:10,125 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-03-25 17:35:10,125 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-03-25 17:35:10,439 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-25 17:35:10,439 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-25 17:35:10,439 INFO supervisord started with pid 1
|
||||
2026-03-25 17:35:11,447 INFO spawned: 'mesh' with pid 7
|
||||
2026-03-25 17:35:11,472 INFO spawned: 'tunnel' with pid 8
|
||||
2026-03-25 17:35:11,495 INFO spawned: 'victoria' with pid 9
|
||||
2026-03-25 17:35:11,580 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:11,580 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:11,580 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-25 17:35:23,930 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-25 17:35:24,932 INFO spawned: 'tunnel' with pid 21
|
||||
2026-03-25 17:35:25,980 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:03:59,396 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.
|
||||
2026-03-26 07:03:59,453 INFO Included extra file "/etc/supervisord.conf.d/mesh.conf" during parsing
|
||||
2026-03-26 07:03:59,453 INFO Included extra file "/etc/supervisord.conf.d/tunnel.conf" during parsing
|
||||
2026-03-26 07:03:59,453 INFO Included extra file "/etc/supervisord.conf.d/victoria.conf" during parsing
|
||||
2026-03-26 07:03:59,789 INFO RPC interface 'supervisor' initialized
|
||||
2026-03-26 07:03:59,789 CRIT Server 'unix_http_server' running without any HTTP authentication checking
|
||||
2026-03-26 07:03:59,789 INFO supervisord started with pid 1
|
||||
2026-03-26 07:04:00,821 INFO spawned: 'mesh' with pid 7
|
||||
2026-03-26 07:04:00,943 INFO spawned: 'tunnel' with pid 8
|
||||
2026-03-26 07:04:01,000 INFO spawned: 'victoria' with pid 9
|
||||
2026-03-26 07:04:01,303 INFO success: mesh entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:01,303 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:01,303 INFO success: victoria entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:14,794 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-26 07:04:15,798 INFO spawned: 'tunnel' with pid 21
|
||||
2026-03-26 07:04:16,817 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:04:48,237 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-26 07:04:49,249 INFO spawned: 'tunnel' with pid 24
|
||||
2026-03-26 07:04:50,255 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
2026-03-26 07:05:20,150 WARN exited: tunnel (exit status 1; not expected)
|
||||
2026-03-26 07:05:21,158 INFO spawned: 'tunnel' with pid 27
|
||||
2026-03-26 07:05:22,161 INFO success: tunnel entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
|
||||
Reference in New Issue
Block a user