SUPLA (Docker) - zarządzanie własną instancją

User avatar
paco52327
Posts: 89
Joined: Tue Apr 02, 2019 12:57 pm

Post

Naprowadźcie, mam bardzo starą instancję supli na dockerze, aktualizowaną na bieżąco. Chciałem postawić ją od nowa, ze zmianą cloud_domain jedynie. Backup idzie bez problemu, później wszystkie kroki instalacja dokera, supli, wsio ok. Problemem jest przywrócenie backupu który wychodzi bez błędów ale jak wejdę na serwer mam tylko jedno urządzenie suplaemu, a rolety, meki, liwki już nie.
Jedyny błąd który widzę to błąd wersji bazy danych i nie mogę temu zaradzić. supla-cloud bez błędów, supla-server poniżej.

Code: Select all

INFO[08:56:17.044198] Server version 22.12.01 [Protocol v19]
INFO[08:56:17.044353] Started at Fri Apr 14 08:56:17 2023
ERR[08:56:17.058383] Incorrect database version! Expected: 20221219113615
2023-04-14 08:56:17,060 INFO exited: supla-server (exit status 1; not expected)
2023-04-14 08:56:20,066 INFO spawned: 'supla-scheduler' with pid 24
2023-04-14 08:56:20,069 INFO spawned: 'supla-server' with pid 25
INFO[08:56:20.081667] Scheduler version 22.07.01
INFO[08:56:20.081842] Started at Fri Apr 14 08:56:20 2023
INFO[08:56:20.091694] Server version 22.12.01 [Protocol v19]
INFO[08:56:20.091868] Started at Fri Apr 14 08:56:20 2023
ERR[08:56:20.094678] Incorrect database version! Expected: 20221219113615
2023-04-14 08:56:20,096 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[08:56:20.105956] Incorrect database version! Expected: 20221219113615
2023-04-14 08:56:20,106 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
2023-04-14 08:56:20,107 INFO exited: supla-server (exit status 1; not expected)
2023-04-14 08:56:21,108 INFO gave up: supla-server entered FATAL state, too many start retries too quickly
2023-04-14 08:57:54,833 WARN received SIGTERM indicating exit request
2023-04-14 08:58:12,373 CRIT Supervisor running as root (no user in config file)
2023-04-14 08:58:12,376 INFO supervisord started with pid 1
2023-04-14 08:58:13,379 INFO spawned: 'supla-scheduler' with pid 18
2023-04-14 08:58:13,383 INFO spawned: 'supla-server' with pid 19
INFO[08:58:13.393695] Server version 22.12.01 [Protocol v19]
INFO[08:58:13.393795] Started at Fri Apr 14 08:58:13 2023
INFO[08:58:13.394396] Scheduler version 22.07.01
INFO[08:58:13.394553] Started at Fri Apr 14 08:58:13 2023
INFO[08:58:13.406687] SSL version: LibreSSL 3.5.3
2023-04-14 08:58:14,408 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-14 08:58:14,408 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-14 09:09:50,512 WARN received SIGTERM indicating exit request
2023-04-14 09:09:50,513 INFO waiting for supla-scheduler, supla-server to die
INFO[09:09:50.513217] Shutting down...
ERR[09:09:50.514138] IPC connection accept error 9
ERR[09:09:50.515107] Connection accept error 9
ERR[09:09:50.515455] Connection accept error 9
INFO[09:09:50.516363] Stopped at Fri Apr 14 09:09:50 2023
2023-04-14 09:09:50,517 INFO stopped: supla-server (exit status 0)
INFO[09:09:50.518643] Shutting down...
INFO[09:09:50.519153] Stopped at Fri Apr 14 09:09:50 2023
2023-04-14 09:09:50,520 INFO stopped: supla-scheduler (exit status 0)
2023-04-14 09:10:08,409 CRIT Supervisor running as root (no user in config file)
2023-04-14 09:10:08,413 INFO supervisord started with pid 1
2023-04-14 09:10:09,417 INFO spawned: 'supla-scheduler' with pid 18
2023-04-14 09:10:09,421 INFO spawned: 'supla-server' with pid 19
INFO[09:10:09.433113] Scheduler version 22.07.01
INFO[09:10:09.433244] Started at Fri Apr 14 09:10:09 2023
INFO[09:10:09.434258] Server version 22.12.01 [Protocol v19]
INFO[09:10:09.434363] Started at Fri Apr 14 09:10:09 2023
INFO[09:10:09.447602] SSL version: LibreSSL 3.5.3
2023-04-14 09:10:10,450 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-14 09:10:10,450 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Top
User avatar
lesny8
Posts: 3132
Joined: Mon Dec 11, 2017 9:43 pm
Has thanked: 10 times
Been thanked: 9 times

Post

Jaką masz wersję Cloud na starej instancji?

Według tego błędu struktura baza danych z odtworzonego backupu jest nieaktualna

Code: Select all

ERR[08:56:17.058383] Incorrect database version! Expected: 20221219113615
Nowy Cloud to wersja zapewne ostatnia, czyli 22.12

Przy takim przenoszeniu trzeba najpierw na dotychczasowej instancji zrobić upgrade Supli do najnowszej wersji i potem zrobić backup bazy i odtworzyć na nowej instancji, albo zainstalować nową instancję w takiej wersji jak jest na starej, odtworzyć bazę ze starej instancji, a potem upgradować nową. U Ciebie te dwie instancje się różnią wersjami.

A spróbuj jeszcze na tej nowej instancji

Code: Select all

./supla.sh upgrade
SOP 2023 :heavy_check_mark:
SOP 2024 :heavy_check_mark:
Czekam na kolejne Supla Offline Party :upside_down_face:
🧩: 🔑cz->b ⛴️+ila
Top
User avatar
paco52327
Posts: 89
Joined: Tue Apr 02, 2019 12:57 pm

Post

lesny8 wrote: Fri Apr 14, 2023 9:45 am Jaką masz wersję Cloud na starej instancji?

Według tego błędu struktura baza danych z odtworzonego backupu jest nieaktualna

Code: Select all

ERR[08:56:17.058383] Incorrect database version! Expected: 20221219113615
Nowy Cloud to wersja zapewne ostatnia, czyli 22.12

Przy takim przenoszeniu trzeba najpierw na dotychczasowej instancji zrobić upgrade Supli do najnowszej wersji i potem zrobić backup bazy i odtworzyć na nowej instancji, albo zainstalować nową instancję w takiej wersji jak jest na starej, odtworzyć bazę ze starej instancji, a potem upgradować nową. U Ciebie te dwie instancje się różnią wersjami.

A spróbuj jeszcze na tej nowej instancji

Code: Select all

./supla.sh upgrade
Dzięki za odpowiedź. Męczę to już kilka dni, robiłem upgrade na starcie ale wtedy inne kombinacje robiłem i przez te klika dni mogła być jakaś aktualizacja.
Zrobiłem upgrade i wszystko od nowa ten sam błąd, i tylko to jedno urządzenie suplaemu

Code: Select all

INFO[10:45:10.215355] Started at Fri Apr 14 10:45:10 2023
ERR[10:45:10.240904] Incorrect database version! Expected: 20221219113615
ERR[10:45:10.242132] Incorrect database version! Expected: 20221219113615
2023-04-14 10:45:10,242 INFO exited: supla-scheduler (exit status 1; not expected)
2023-04-14 10:45:10,243 INFO exited: supla-server (exit status 1; not expected)
2023-04-14 10:45:13,249 INFO spawned: 'supla-scheduler' with pid 31
2023-04-14 10:45:13,252 INFO spawned: 'supla-server' with pid 32
INFO[10:45:13.264147] Scheduler version 22.07.01
INFO[10:45:13.264365] Started at Fri Apr 14 10:45:13 2023
INFO[10:45:13.271475] Server version 22.12.01 [Protocol v19]
INFO[10:45:13.271625] Started at Fri Apr 14 10:45:13 2023
ERR[10:45:13.274195] Incorrect database version! Expected: 20221219113615
2023-04-14 10:45:13,275 INFO exited: supla-scheduler (exit status 1; not expected)
2023-04-14 10:45:13,276 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
ERR[10:45:13.278395] Incorrect database version! Expected: 20221219113615
2023-04-14 10:45:13,279 INFO exited: supla-server (exit status 1; not expected)
2023-04-14 10:45:13,280 INFO gave up: supla-server entered FATAL state, too many start retries too quickly
2023-04-14 10:46:39,953 WARN received SIGTERM indicating exit request
2023-04-14 10:46:57,503 CRIT Supervisor running as root (no user in config file)
2023-04-14 10:46:57,507 INFO supervisord started with pid 1
2023-04-14 10:46:58,511 INFO spawned: 'supla-scheduler' with pid 18
2023-04-14 10:46:58,515 INFO spawned: 'supla-server' with pid 19
INFO[10:46:58.525093] Server version 22.12.01 [Protocol v19]
INFO[10:46:58.525206] Started at Fri Apr 14 10:46:58 2023
INFO[10:46:58.526383] Scheduler version 22.07.01
INFO[10:46:58.526523] Started at Fri Apr 14 10:46:58 2023
INFO[10:46:58.539732] SSL version: LibreSSL 3.5.3
2023-04-14 10:46:59,541 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-14 10:46:59,541 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Edyta.
W obu wersja mysql:5.7.20
Top
tijo
Posts: 264
Joined: Fri Dec 01, 2017 12:44 pm
Been thanked: 1 time

Post

pzygmunt wrote: Thu Mar 07, 2019 10:20 am supla_temperature_log
a gdzie tego szukać na rpi?
Top
User avatar
pzygmunt
Posts: 20302
Joined: Tue Jan 19, 2016 9:26 am
Location: Paczków
Been thanked: 59 times

Post

W bazie danych
SUPLA.... Nareszcie w domu.
Top
User avatar
paco52327
Posts: 89
Joined: Tue Apr 02, 2019 12:57 pm

Post

paco52327 wrote: Fri Apr 14, 2023 9:19 am Naprowadźcie, mam bardzo starą instancję supli na dockerze, aktualizowaną na bieżąco. Chciałem postawić ją od nowa, ze zmianą cloud_domain jedynie. Backup idzie bez problemu, później wszystkie kroki instalacja dokera, supli, wsio ok. Problemem jest przywrócenie backupu który wychodzi bez błędów ale jak wejdę na serwer mam tylko jedno urządzenie suplaemu, a rolety, meki, liwki już nie.
Jedyny błąd który widzę to błąd wersji bazy danych i nie mogę temu zaradzić. supla-cloud bez błędów, supla-server poniżej.

Code: Select all

INFO[08:56:17.044198] Server version 22.12.01 [Protocol v19]
INFO[08:56:17.044353] Started at Fri Apr 14 08:56:17 2023
ERR[08:56:17.058383] Incorrect database version! Expected: 20221219113615
2023-04-14 08:56:17,060 INFO exited: supla-server (exit status 1; not expected)
2023-04-14 08:56:20,066 INFO spawned: 'supla-scheduler' with pid 24
2023-04-14 08:56:20,069 INFO spawned: 'supla-server' with pid 25
INFO[08:56:20.081667] Scheduler version 22.07.01
INFO[08:56:20.081842] Started at Fri Apr 14 08:56:20 2023
INFO[08:56:20.091694] Server version 22.12.01 [Protocol v19]
INFO[08:56:20.091868] Started at Fri Apr 14 08:56:20 2023
ERR[08:56:20.094678] Incorrect database version! Expected: 20221219113615
2023-04-14 08:56:20,096 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[08:56:20.105956] Incorrect database version! Expected: 20221219113615
2023-04-14 08:56:20,106 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
2023-04-14 08:56:20,107 INFO exited: supla-server (exit status 1; not expected)
2023-04-14 08:56:21,108 INFO gave up: supla-server entered FATAL state, too many start retries too quickly
2023-04-14 08:57:54,833 WARN received SIGTERM indicating exit request
2023-04-14 08:58:12,373 CRIT Supervisor running as root (no user in config file)
2023-04-14 08:58:12,376 INFO supervisord started with pid 1
2023-04-14 08:58:13,379 INFO spawned: 'supla-scheduler' with pid 18
2023-04-14 08:58:13,383 INFO spawned: 'supla-server' with pid 19
INFO[08:58:13.393695] Server version 22.12.01 [Protocol v19]
INFO[08:58:13.393795] Started at Fri Apr 14 08:58:13 2023
INFO[08:58:13.394396] Scheduler version 22.07.01
INFO[08:58:13.394553] Started at Fri Apr 14 08:58:13 2023
INFO[08:58:13.406687] SSL version: LibreSSL 3.5.3
2023-04-14 08:58:14,408 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-14 08:58:14,408 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-14 09:09:50,512 WARN received SIGTERM indicating exit request
2023-04-14 09:09:50,513 INFO waiting for supla-scheduler, supla-server to die
INFO[09:09:50.513217] Shutting down...
ERR[09:09:50.514138] IPC connection accept error 9
ERR[09:09:50.515107] Connection accept error 9
ERR[09:09:50.515455] Connection accept error 9
INFO[09:09:50.516363] Stopped at Fri Apr 14 09:09:50 2023
2023-04-14 09:09:50,517 INFO stopped: supla-server (exit status 0)
INFO[09:09:50.518643] Shutting down...
INFO[09:09:50.519153] Stopped at Fri Apr 14 09:09:50 2023
2023-04-14 09:09:50,520 INFO stopped: supla-scheduler (exit status 0)
2023-04-14 09:10:08,409 CRIT Supervisor running as root (no user in config file)
2023-04-14 09:10:08,413 INFO supervisord started with pid 1
2023-04-14 09:10:09,417 INFO spawned: 'supla-scheduler' with pid 18
2023-04-14 09:10:09,421 INFO spawned: 'supla-server' with pid 19
INFO[09:10:09.433113] Scheduler version 22.07.01
INFO[09:10:09.433244] Started at Fri Apr 14 09:10:09 2023
INFO[09:10:09.434258] Server version 22.12.01 [Protocol v19]
INFO[09:10:09.434363] Started at Fri Apr 14 09:10:09 2023
INFO[09:10:09.447602] SSL version: LibreSSL 3.5.3
2023-04-14 09:10:10,450 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-14 09:10:10,450 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Odpowiem sobie może dla potomnych. Chciałem przywrócić starą bazę na świeżym obrazie dockera ale ze zmianą domeny i nie wiem dlaczego mnie pokusiło na zmianę domeny w FIRST_USER_EMAIL, grzebiąc w bazie danych zorientowałem się że stary mail użytkownika tam gdzieś lata i to był trop.
Top

Return to “FAQ / Jak to zrobić”