Zmiana sprzętu na serwer supli

makrz · Post Wed Mar 30, 2022 7:11 pm

Witam
Wymieniłem RPI na HP z debianem, postawiłem serwer supli wgrałem bazę z backupu z RPI.
Wszystko jest, urządzenia, lokalizacje, smartfony ale offline.
Z suplą łączę się po domenie, urządzenia łączą się po IP.
IP tego HP jest takie jakie była dla RPI.
Jak to naprawić? Czekam na pomysły.

log

Code: Select all

pi@supla:~$ docker logs --tail=50 supla-server
INFO[1648668053.5932] Device registration started. ClientSD: 41 Protocol Version: 16 ThreadID: 2606 GUID: 55B5C200
ERR[1648668053.23709] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668053.941973] Connection accepted: 192.168.0.30:35396 ClientSD: 24 Secure: 1
INFO[1648668053.974666] Cipher: ECDHE-RSA-AES256-GCM-SHA384, ClientSD: 24
INFO[1648668053.981115] Device registration started. ClientSD: 24 Protocol Version: 12 ThreadID: 2607 GUID: 1389623D
ERR[1648668054.8012] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668055.383389] Connection accepted: 192.168.0.41:63771 ClientSD: 28 Secure: 0
INFO[1648668055.582644] Device registration started. ClientSD: 28 Protocol Version: 16 ThreadID: 2608 GUID: 770D064E
ERR[1648668055.602026] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668056.277509] Connection accepted: 192.168.0.233:39614 ClientSD: 14 Secure: 1
INFO[1648668056.380655] Cipher: AES128-SHA, ClientSD: 14
INFO[1648668056.493506] Device registration started. ClientSD: 14 Protocol Version: 10 ThreadID: 2609 GUID: E4ECCD54
ERR[1648668056.513939] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668057.85853] Connection accepted: 192.168.0.115:60902 ClientSD: 17 Secure: 0
INFO[1648668057.544556] Connection accepted: 192.168.0.35:61548 ClientSD: 23 Secure: 0
INFO[1648668057.682918] Device registration started. ClientSD: 23 Protocol Version: 16 ThreadID: 2611 GUID: 23D5C8E4
ERR[1648668057.702844] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668057.732593] Connection accepted: 192.168.0.34:63526 ClientSD: 27 Secure: 0
INFO[1648668057.737969] Device registration started. ClientSD: 27 Protocol Version: 12 ThreadID: 2612 GUID: E9469D66
ERR[1648668057.755497] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668057.892215] Device registration started. ClientSD: 17 Protocol Version: 9 ThreadID: 2610 GUID: 4B7D0000
ERR[1648668057.934670] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668058.27707] Connection accepted: 192.168.0.30:35398 ClientSD: 20 Secure: 1
INFO[1648668058.73803] Cipher: ECDHE-RSA-AES256-GCM-SHA384, ClientSD: 20
INFO[1648668058.87772] Device registration started. ClientSD: 20 Protocol Version: 12 ThreadID: 2613 GUID: 1389623D
ERR[1648668058.114612] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668058.749347] Connection accepted: 192.168.0.43:64828 ClientSD: 28 Secure: 0
INFO[1648668058.755061] Device registration started. ClientSD: 28 Protocol Version: 16 ThreadID: 2615 GUID: BEBE17EF
ERR[1648668058.772385] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668059.45936] Connection accepted: 192.168.0.33:60654 ClientSD: 29 Secure: 0
INFO[1648668059.50469] Device registration started. ClientSD: 29 Protocol Version: 16 ThreadID: 2616 GUID: 75395C73
ERR[1648668059.69913] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668059.260259] Connection accepted: 192.168.0.32:50527 ClientSD: 32 Secure: 0
INFO[1648668059.434447] Device registration started. ClientSD: 32 Protocol Version: 16 ThreadID: 2617 GUID: 7255BA5A
INFO[1648668059.440763] Connection accepted: 192.168.0.155:64018 ClientSD: 35 Secure: 0
INFO[1648668059.448733] Device registration started. ClientSD: 35 Protocol Version: 16 ThreadID: 2618 GUID: 69DF7F00
ERR[1648668059.456888] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
ERR[1648668059.468625] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668059.554662] Connection accepted: 192.168.0.42:64529 ClientSD: 39 Secure: 0
INFO[1648668059.558850] Device registration started. ClientSD: 39 Protocol Version: 16 ThreadID: 2619 GUID: 04207853
ERR[1648668059.576232] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668059.616001] Connection accepted: 192.168.0.123:60137 ClientSD: 41 Secure: 0
INFO[1648668059.620953] Device registration started. ClientSD: 41 Protocol Version: 12 ThreadID: 2620 GUID: 53C9E3DE
ERR[1648668059.635914] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668059.866870] Connection accepted: 192.168.0.181:50262 ClientSD: 44 Secure: 0
INFO[1648668060.49665] Device registration started. ClientSD: 44 Protocol Version: 16 ThreadID: 2622 GUID: E36C4DF1
ERR[1648668060.68885] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
INFO[1648668060.81822] Connection accepted: 192.168.0.31:55029 ClientSD: 50 Secure: 0
INFO[1648668060.282927] Device registration started. ClientSD: 50 Protocol Version: 16 ThreadID: 2623 GUID: 55B5C200
ERR[1648668060.301224] MySQL - execute error: Incorrect number of arguments for PROCEDURE supla.supla_update_iodevice; expected 7, got 8
pi@supla:~$

pzygmunt · Post Wed Mar 30, 2022 7:49 pm

Uruchom supla:initialize coś się wersje bazy Ci rozjechały.

makrz · Post Wed Mar 30, 2022 8:12 pm

pzygmunt wrote: Wed Mar 30, 2022 7:49 pm Uruchom supla:initialize coś się wersje bazy Ci rozjechały.

Dziękuję za odpowiedź.
Jeszcze pytanie, gdzie i jak?
Supla jest w /home/pi/supla-docker/
Pozdrawiam

pzygmunt · Post Wed Mar 30, 2022 8:24 pm

docker exec -u www-data supla-cloud php bin/console supla:initialize

makrz · Post Wed Mar 30, 2022 8:33 pm

pzygmunt wrote: Wed Mar 30, 2022 8:24 pm docker exec -u www-data supla-cloud php bin/console supla:initialize

Code: Select all

pi@supla:~/supla-docker$ docker exec -u www-data supla-cloud php bin/console supla:initialize
Database connection has been established.

                    Application Migrations


No migrations to execute.

 [OK] The "async" transport was set up successfully.

Client for webapp exists.
pi@supla:~/supla-docker$ cd
pi@supla:~$ docker exec -u www-data supla-cloud php bin/console supla:initialize
Database connection has been established.

                    Application Migrations


No migrations to execute.

 [OK] The "async" transport was set up successfully.

Client for webapp exists.
pi@supla:~$

Niestety nie pomogło.

pzygmunt · Post Wed Mar 30, 2022 8:40 pm

Możliwe, że przywróciłeś bazę po jej zainicjowaniu, a backup mialeś w starszej wersji.

Z poziomu MySQL-a Usuń bazę. Utwórz ją ponownie (pustą).
Wtedy przywróć backup i na koniec supla:initialize

makrz · Post Thu Mar 31, 2022 6:15 am

pzygmunt wrote: Wed Mar 30, 2022 8:40 pm Możliwe, że przywróciłeś bazę po jej zainicjowaniu, a backup mialeś w starszej wersji.

Z poziomu MySQL-a Usuń bazę. Utwórz ją ponownie (pustą).
Wtedy przywróć backup i na koniec supla:initialize

Dziękuję bardzo, po usunięciu i utworzeniu bazy wszystko działa.
Pozdrzwiam