supla-cloud i supla-server mam unhealthy, czy może Wam logi coś mówią? Mi się skończyły pomysły
Wygląda to tak jaby baza supli nie istniała
2024-02-09 09:32:38,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.
2024-02-09 09:32:38,686 INFO supervisord started with pid 1
2024-02-09 09:32:39,687 INFO spawned: 'supla-scheduler' with pid 20
2024-02-09 09:32:39,690 INFO spawned: 'supla-server' with pid 21
INFO[09:32:39.723956] Scheduler version 22.07.01
INFO[09:32:39.724022] Started at Fri Feb 9 09:32:39 2024
ERR[09:32:39.745333] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
INFO[09:32:39.745564] Connecting to database ....
INFO[09:32:39.835703] Server version 23.12.01 [Protocol v22]
INFO[09:32:39.835761] Started at Fri Feb 9 09:32:39 2024
ERR[09:32:39.837831] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
INFO[09:32:39.837842] Connecting to database ....
ERR[09:32:40.746352] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
2024-02-09 09:32:40,746 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-09 09:32:40,746 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ERR[09:32:40.838519] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:41.747498] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:41.839210] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:42.748432] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:42.839931] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:43.749389] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:43.844378] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:44.750313] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:44.845304] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:45.751079] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:45.846167] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:46.752845] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)
ERR[09:32:46.849537] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[09:32:46.849619] The version of the database can not be determined!
ERR[09:32:47.754371] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
2024-02-09 09:32:47,754 INFO exited: supla-server (exit status 1; not expected)
ERR[09:32:47.754896] The version of the database can not be determined!
2024-02-09 09:32:47,756 INFO spawned: 'supla-server' with pid 22
2024-02-09 09:32:47,758 INFO exited: supla-scheduler (exit status 1; not expected)
INFO[09:32:47.776778] Server version 23.12.01 [Protocol v22]
2024-02-09 09:32:47,778 INFO spawned: 'supla-scheduler' with pid 23
INFO[09:32:47.779039] Started at Fri Feb 9 09:32:47 2024
ERR[09:32:47.781113] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[09:32:47.781471] The version of the database can not be determined!
INFO[09:32:47.792741] Scheduler version 22.07.01
2024-02-09 09:32:47,793 INFO exited: supla-server (exit status 1; not expected)
INFO[09:32:47.793513] Started at Fri Feb 9 09:32:47 2024
ERR[09:32:47.796963] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[09:32:47.797369] The version of the database can not be determined!
2024-02-09 09:32:48,799 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-09 09:32:48,800 INFO spawned: 'supla-server' with pid 24
2024-02-09 09:32:48,801 INFO exited: supla-scheduler (exit status 1; not expected)
INFO[09:32:48.817298] Server version 23.12.01 [Protocol v22]
2024-02-09 09:32:48,826 INFO spawned: 'supla-scheduler' with pid 25
INFO[09:32:48.826486] Started at Fri Feb 9 09:32:48 2024
ERR[09:32:48.832343] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[09:32:48.832767] The version of the database can not be determined!
INFO[09:32:48.837713] Scheduler version 22.07.01
INFO[09:32:48.838064] Started at Fri Feb 9 09:32:48 2024
ERR[09:32:48.882127] Incorrect database version! Expected: 20231219083453
2024-02-09 09:32:48,882 INFO exited: supla-server (exit status 1; not expected)
2024-02-09 09:32:48,883 INFO exited: supla-scheduler (exit status 1; not expected)
2024-02-09 09:32:49,886 INFO spawned: 'supla-scheduler' with pid 26
INFO[09:32:49.894588] Scheduler version 22.07.01
INFO[09:32:49.895490] Started at Fri Feb 9 09:32:49 2024
ERR[09:32:49.901274] Incorrect database version! Expected: 20231219083453
2024-02-09 09:32:49,902 INFO exited: supla-scheduler (exit status 1; not expected)
2024-02-09 09:32:50,904 INFO spawned: 'supla-server' with pid 27
INFO[09:32:50.919933] Server version 23.12.01 [Protocol v22]
INFO[09:32:50.919987] Started at Fri Feb 9 09:32:50 2024
ERR[09:32:50.922086] Incorrect database version! Expected: 20231219083453
2024-02-09 09:32:50,923 INFO exited: supla-server (exit status 1; not expected)
2024-02-09 09:32:51,926 INFO spawned: 'supla-scheduler' with pid 28
INFO[09:32:51.934097] Scheduler version 22.07.01
INFO[09:32:51.934461] Started at Fri Feb 9 09:32:51 2024
ERR[09:32:51.940282] Incorrect database version! Expected: 20231219083453
2024-02-09 09:32:52,942 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-09 09:32:52,942 INFO exited: supla-scheduler (exit status 1; not expected)
2024-02-09 09:32:53,945 INFO spawned: 'supla-scheduler' with pid 29
2024-02-09 09:32:53,946 INFO spawned: 'supla-server' with pid 30
INFO[09:32:53.952794] Scheduler version 22.07.01
INFO[09:32:53.952857] Started at Fri Feb 9 09:32:53 2024
ERR[09:32:53.958593] Incorrect database version! Expected: 20231219083453
2024-02-09 09:32:53,959 INFO exited: supla-scheduler (exit status 1; not expected)
INFO[09:32:53.965974] Server version 23.12.01 [Protocol v22]
INFO[09:32:53.966194] Started at Fri Feb 9 09:32:53 2024
ERR[09:32:53.979502] Incorrect database version! Expected: 20231219083453
2024-02-09 09:32:53,981 INFO exited: supla-server (exit status 1; not expected)
2024-02-09 09:32:54,983 INFO spawned: 'supla-scheduler' with pid 31
2024-02-09 09:32:54,984 INFO gave up: supla-server entered FATAL state, too many start retries too quickly
INFO[09:32:54.991594] Scheduler version 22.07.01
INFO[09:32:54.991668] Started at Fri Feb 9 09:32:54 2024
ERR[09:32:54.994986] Incorrect database version! Expected: 20231219083453
2024-02-09 09:32:54,995 INFO exited: supla-scheduler (exit status 1; not expected)
2024-02-09 09:32:56,999 INFO spawned: 'supla-scheduler' with pid 32
INFO[09:32:57.007998] Scheduler version 22.07.01
INFO[09:32:57.008312] Started at Fri Feb 9 09:32:57 2024
ERR[09:32:57.013106] Incorrect database version! Expected: 20231219083453
2024-02-09 09:32:57,013 INFO exited: supla-scheduler (exit status 1; not expected)
2024-02-09 09:33:00,018 INFO spawned: 'supla-scheduler' with pid 33
INFO[09:33:00.027577] Scheduler version 22.07.01
INFO[09:33:00.027639] Started at Fri Feb 9 09:33:00 2024
ERR[09:33:00.031805] Incorrect database version! Expected: 20231219083453
2024-02-09 09:33:00,032 INFO exited: supla-scheduler (exit status 1; not expected)
2024-02-09 09:33:01,034 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly