podmieniłem
"COMPOSE_FILE=docker compose.yml:docker compose.standalone.yml:docker compose.arm32v7.ym"
przed uruchomieniem
[tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...
- klimasstudio
- Posty: 1115
- Rejestracja: śr sie 28, 2019 9:35 pm
- Lokalizacja: localhost
- Kontakt:
supla-docker/supla.sh
supla-scripts/docker/suplascripts.sh
Tylko te dwa pliki edytujesz zamieniasz docker-compose na docker compose
EDIT: I jak zadziałało ?
supla-scripts/docker/suplascripts.sh
Tylko te dwa pliki edytujesz zamieniasz docker-compose na docker compose
EDIT: I jak zadziałało ?
Więc chodź OSUPLUJE Ci dom
Druk 3D - > https://klimastech.eu.org/druk-3d
Druk 3D - > https://klimastech.eu.org/druk-3d
Kod: Zaznacz cały
nano supla-docker/supla.sh
Czekam na kolejne Supla Offline Party
Pewnie gdzieś już było ale nie mogę znaleźć:
Jak w supla-cloud wyłączyć wymuszanie protokołu https:?
Jak w supla-cloud wyłączyć wymuszanie protokołu https:?
Widzimy się na Supla Offline Party Season 2
Czekam na kolejne Supla Offline Party
Heh, nie wpadłbym na to...
Zmieniłem port na 444 i już mi się nie zapętla
Zmieniłem port na 444 i już mi się nie zapętla
Widzimy się na Supla Offline Party Season 2
Witajcie, potrzebuję pomocy.
Supla przestała działać lokalnie
Restartuje się kontener supla/supla-cloud:arm32v7 i kompletnie nie wiem czemu.
Dodatkowo pojawił się błąd /usr/local/lib/python3.9/dist-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
Supla przestała działać lokalnie
Kod: Zaznacz cały
./supla.sh upgrade
Making database backup
Database backup saved to ./var/backups/supla11052022091716.sql.gz
Stopping SUPLA containers
/usr/local/lib/python3.9/dist-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
Stopping supla-server ... done
Stopping supla-cloud ... done
Stopping supla-db ... done
SUPLA containers has been stopped.
/usr/local/lib/python3.9/dist-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
Pulling supla-db ... done
Pulling supla-cloud ... done
Pulling supla-server ... done
Starting SUPLA containers
/usr/local/lib/python3.9/dist-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
Starting supla-db ... done
Starting supla-cloud ... done
Starting supla-server ... done
SUPLA containers has been started.
root@orangepi3:/supla-docker# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3c04a85bdcd8 supla/supla-server:arm32v7 "/usr/bin/server-ent…" 6 minutes ago Up 38 seconds 0.0.0.0:2015-2016->2015-2016/tcp, :::2015-2016->2015-2016/tcp supla-server
8b4489260d11 supla/supla-cloud:arm32v7 "docker-php-entrypoi…" 6 minutes ago Restarting (255) 5 seconds ago supla-cloud
600375a22015 mariadb:10.6.4-focal "docker-entrypoint.s…" 6 minutes ago Up 40 seconds 3306/tcp supla-db
Dodatkowo pojawił się błąd /usr/local/lib/python3.9/dist-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
Kod: Zaznacz cały
docker logs --tail=50 supla-cloud
_scene_caption already exists
In PDOConnection.php line 137:
SQLSTATE[42000]: Syntax error or access violation: 1304 PROCEDURE supla_set
_scene_caption already exists
doctrine:migrations:migrate [--write-sql [WRITE-SQL]] [--dry-run] [--query-time] [--allow-no-migration] [--all-or-nothing [ALL-OR-NOTHING]] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--db DB] [--em EM] [--shard SHARD] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<version>]
Database connection has been established.
Application Migrations
Migrating up to 20221020225729 from 20220929090847
++ migrating 20221005003914
-> CREATE PROCEDURE `supla_set_scene_caption`(IN `_user_id` INT, IN `_scene_id` INT, IN `_caption` VARCHAR(255) CHARSET utf8mb4) NOT DETERMINISTIC NO SQL SQL SECURITY DEFINER UPDATE supla_scene SET caption = _caption WHERE id = _scene_id AND user_id = _user_id
Migration 20221005003914 failed during Execution. Error An exception occurred while executing 'CREATE PROCEDURE `supla_set_scene_caption`(IN `_user_id` INT, IN `_scene_id` INT, IN `_caption` VARCHAR(255) CHARSET utf8mb4) NOT DETERMINISTIC NO SQL SQL SECURITY DEFINER UPDATE supla_scene SET caption = _caption WHERE id = _scene_id AND user_id = _user_id':
SQLSTATE[42000]: Syntax error or access violation: 1304 PROCEDURE supla_set_scene_caption already exists
In AbstractMySQLDriver.php line 128:
An exception occurred while executing 'CREATE PROCEDURE `supla_set_scene_ca
ption`(IN `_user_id` INT, IN `_scene_id` INT, IN `_caption` VARCHAR(255) CH
ARSET utf8mb4) NOT DETERMINISTIC NO SQL SQL SECURITY DEFINER UPDATE supla_s
cene SET caption = _caption WHERE id = _scene_id AND user_id = _user_id':
SQLSTATE[42000]: Syntax error or access violation: 1304 PROCEDURE supla_set
_scene_caption already exists
In Exception.php line 18:
SQLSTATE[42000]: Syntax error or access violation: 1304 PROCEDURE supla_set
_scene_caption already exists
In PDOConnection.php line 137:
SQLSTATE[42000]: Syntax error or access violation: 1304 PROCEDURE supla_set
_scene_caption already exists
doctrine:migrations:migrate [--write-sql [WRITE-SQL]] [--dry-run] [--query-time] [--allow-no-migration] [--all-or-nothing [ALL-OR-NOTHING]] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--db DB] [--em EM] [--shard SHARD] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<version>]
Kod: Zaznacz cały
docker logs --tail=50 supla-server
ERR[1667636976.82334] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1667636976.89771] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1667636977.84102] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1667636977.91544] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1667636978.95484] Incorrect database version! Expected: 20221020225729
2022-11-05 08:29:38,098 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1667636978.100659] Incorrect database version! Expected: 20221020225729
2022-11-05 08:29:38,104 INFO spawned: 'supla-scheduler' with pid 21
2022-11-05 08:29:38,106 INFO exited: supla-server (exit status 1; not expected)
2022-11-05 08:29:38,111 INFO spawned: 'supla-server' with pid 22
INFO[1667636978.127746] Scheduler version 22.07.01
INFO[1667636978.127921] Started at Sat Nov 5 08:29:38 2022
ERR[1667636978.140618] Incorrect database version! Expected: 20221020225729
INFO[1667636978.141411] Server version 22.11 [Protocol v19]
INFO[1667636978.141674] Started at Sat Nov 5 08:29:38 2022
2022-11-05 08:29:38,144 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1667636978.151213] Incorrect database version! Expected: 20221020225729
2022-11-05 08:29:38,153 INFO exited: supla-server (exit status 1; not expected)
2022-11-05 08:29:39,159 INFO spawned: 'supla-scheduler' with pid 23
2022-11-05 08:29:39,164 INFO spawned: 'supla-server' with pid 24
INFO[1667636979.180044] Scheduler version 22.07.01
INFO[1667636979.180229] Started at Sat Nov 5 08:29:39 2022
INFO[1667636979.193336] Server version 22.11 [Protocol v19]
INFO[1667636979.193756] Started at Sat Nov 5 08:29:39 2022
ERR[1667636979.205318] Incorrect database version! Expected: 20221020225729
ERR[1667636979.207599] Incorrect database version! Expected: 20221020225729
2022-11-05 08:29:39,209 INFO exited: supla-scheduler (exit status 1; not expected)
2022-11-05 08:29:39,212 INFO exited: supla-server (exit status 1; not expected)
2022-11-05 08:29:41,218 INFO spawned: 'supla-scheduler' with pid 25
2022-11-05 08:29:41,223 INFO spawned: 'supla-server' with pid 26
INFO[1667636981.240969] Scheduler version 22.07.01
INFO[1667636981.242732] Started at Sat Nov 5 08:29:41 2022
ERR[1667636981.257167] Incorrect database version! Expected: 20221020225729
INFO[1667636981.259690] Server version 22.11 [Protocol v19]
2022-11-05 08:29:41,261 INFO exited: supla-scheduler (exit status 1; not expected)
INFO[1667636981.263420] Started at Sat Nov 5 08:29:41 2022
ERR[1667636981.275463] Incorrect database version! Expected: 20221020225729
2022-11-05 08:29:41,283 INFO exited: supla-server (exit status 1; not expected)
2022-11-05 08:29:44,291 INFO spawned: 'supla-scheduler' with pid 27
2022-11-05 08:29:44,295 INFO spawned: 'supla-server' with pid 28
INFO[1667636984.310082] Scheduler version 22.07.01
INFO[1667636984.310238] Started at Sat Nov 5 08:29:44 2022
ERR[1667636984.317368] Incorrect database version! Expected: 20221020225729
2022-11-05 08:29:44,319 INFO exited: supla-scheduler (exit status 1; not expected)
INFO[1667636984.321307] Server version 22.11 [Protocol v19]
2022-11-05 08:29:44,321 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
INFO[1667636984.321511] Started at Sat Nov 5 08:29:44 2022
ERR[1667636984.328035] Incorrect database version! Expected: 20221020225729
2022-11-05 08:29:44,330 INFO exited: supla-server (exit status 1; not expected)
2022-11-05 08:29:45,331 INFO gave up: supla-server entered FATAL state, too many start retries too quickly