Oczywiście u mnie musiał być jakiś problem
Sama aktualizacja pomyślnie, bez błędów...
Nie mogę połączyć się z cloud, app też nie działa.
Nie używam standardowych portów, ale dotychczas wszystko działało bez błędów.
Update z 2.1 na 2.2 bez błędów..
A logi:
Kod: Zaznacz cały
2019-02-13 19:44:41,532 INFO exited: supla-scheduler (exit status 1;
not expected)
INFO[1550087081.731881] Server version 2.3.0 [Protocol v10]
2019-02-13 19:44:41,734 INFO spawned: 'supla-scheduler' with pid 15
INFO[1550087081.736272] Started at Wed Feb 13 19:44:41 2019
ERR[1550087081.762953] MySQL - Failed to connect to database.
ERR[1550087081.762988] Can't connect to database!
2019-02-13 19:44:41,764 INFO exited: supla-server (exit status 1; not expected)
INFO[1550087081.784437] Scheduler version 2.3.0
INFO[1550087081.785140] Started at Wed Feb 13 19:44:41 2019
ERR[1550087081.791421] MySQL - Failed to connect to database.
ERR[1550087081.792170] Can't connect to database!
2019-02-13 19:44:41,796 INFO exited: supla-scheduler (exit status 1;
not expected)
2019-02-13 19:44:42,823 INFO spawned: 'supla-scheduler' with pid 18
2019-02-13 19:44:42,854 INFO spawned: 'supla-server' with pid 19
INFO[1550087082.978763] Scheduler version 2.3.0
INFO[1550087082.978965] Started at Wed Feb 13 19:44:42 2019
INFO[1550087083.28475] Server version 2.3.0 [Protocol v10]
INFO[1550087083.29114] Started at Wed Feb 13 19:44:43 2019
ERR[1550087083.42062] MySQL - Failed to connect to database.
ERR[1550087083.42105] Can't connect to database!
ERR[1550087083.43120] MySQL - Failed to connect to database.
ERR[1550087083.43142] Can't connect to database!
2019-02-13 19:44:43,059 INFO exited: supla-scheduler (exit status 1;
not expected)
2019-02-13 19:44:43,059 INFO exited: supla-server (exit status 1; not expected)
2019-02-13 19:44:45,068 INFO spawned: 'supla-scheduler' with pid 22
2019-02-13 19:44:45,111 INFO spawned: 'supla-server' with pid 23
INFO[1550087085.117985] Scheduler version 2.3.0
INFO[1550087085.119338] Started at Wed Feb 13 19:44:45 2019
ERR[1550087085.123720] MySQL - Failed to connect to database.
ERR[1550087085.124140] Can't connect to database!
2019-02-13 19:44:45,126 INFO exited: supla-scheduler (exit status 1;
not expected)
INFO[1550087085.167822] Server version 2.3.0 [Protocol v10]
INFO[1550087085.168855] Started at Wed Feb 13 19:44:45 2019
ERR[1550087085.172953] MySQL - Failed to connect to database.
ERR[1550087085.173824] Can't connect to database!
2019-02-13 19:44:45,175 INFO exited: supla-server (exit status 1; not expected)
2019-02-13 19:44:48,192 INFO spawned: 'supla-scheduler' with pid 26
2019-02-13 19:44:48,222 INFO spawned: 'supla-server' with pid 27
INFO[1550087088.301178] Server version 2.3.0 [Protocol v10]
INFO[1550087088.304685] Started at Wed Feb 13 19:44:48 2019
INFO[1550087088.307402] Scheduler version 2.3.0
INFO[1550087088.308071] Started at Wed Feb 13 19:44:48 2019
ERR[1550087088.312798] MySQL - Failed to connect to database.
ERR[1550087088.312831] Can't connect to database!
2019-02-13 19:44:48,314 INFO exited: supla-server (exit status 1; not expected)
ERR[1550087088.320380] MySQL - Failed to connect to database.
2019-02-13 19:44:48,320 INFO gave up: supla-server entered FATAL
state, too many start retries too quickly
ERR[1550087088.321037] Can't connect to database!
2019-02-13 19:44:48,322 INFO exited: supla-scheduler (exit status 1;
not expected)
2019-02-13 19:44:49,324 INFO gave up: supla-scheduler entered FATAL
state, too many start retries too quickly