Witam ponownie !
Uwaga długi i nudny post
Dzięki za podpowiedź - po zmianie portów z istniejących
na
w pliku docker-compose.yml spróbowałem jeszcze raz odpalić skrypt
Trzy nowe kontenery uruchamiają się prawidłowo, ale podczas uruchamiania zatrzymują się z kolei oryginalne kontenery i widać że ten nowo postawiony serwer ma w jakiś sposób wpływ na działanie oryginalnego - pierwotnego serwera.
Zrobiło się o tyle niefajnie, że niestety, ale już połączone i działające od jakiegoś czasu urządzenia do mojego oryginalnego serwera supla wysypały się całkowicie, nie mogły sie połączyć, serwer przestał odpowiadać i w ogóle tragedia
W tym momencie musiałem przyswoić wiedzę w zakresie bacupowania i przywracania danych.
W jakiś sposób są oone jednak ze sobą połączone - nie wiem jeszcze gdzie.
Pomyślałem, że to może poprzez nazwy uruchomionych w pliku docker-compose.yml serwisów następuje jakieś połączenie - nie wiem.
W działającym już serwerze w pliku docker-compose.yml są zdefiniowane przecież takie same nazwy jak w tym nowym.
Dalej działałem trochę na czuja - pogrzebanie w pliku docker-compose.yml wydawało mi się dobrym kierunkiem.
Przypominam, że w moim przypadku jest to wersja docker, ale standalone.
Pozmieniałem go więc w poniższy sposób:
Kod: Zaznacz cały
version: '3'
services:
supla2-cloud:
container_name: ${COMPOSE_PROJECT_NAME}-cloud
restart: unless-stopped
image: supla/supla-cloud
env_file:
- .env.default
- .env
volumes:
- ./ssl/cloud:/etc/apache2/ssl:z
- ${VOLUME_DATA}/cloud-local:/var/www/cloud/var/local
- ${VOLUME_DATA}/cloud-logs:/var/www/cloud/var/logs
- supla-server-socket:/supla-server:z
links:
- supla2-db
depends_on:
- supla2-db
supla2-db:
container_name: ${COMPOSE_PROJECT_NAME}-db
restart: unless-stopped
image: mysql:5.7.20
env_file:
- .env.default
- .env
environment:
MYSQL_ROOT_PASSWORD: ${DB_PASSWORD}
MYSQL_DATABASE: supla
MYSQL_USER: supla
MYSQL_PASSWORD: ${DB_PASSWORD}
volumes:
- ${VOLUME_DATA}/mysql:/var/lib/mysql:z
supla2-server:
container_name: ${COMPOSE_PROJECT_NAME}-server
restart: unless-stopped
image: supla/supla-server
env_file:
- .env.default
- .env
volumes:
- ./ssl/server:/etc/supla-server/ssl:z
- supla-server-socket:/var/run/supla:z
ports:
- "2014:2016"
- "2013:2015"
links:
- supla2-db
depends_on:
- supla2-cloud
volumes:
supla-server-socket: {}
Jak widać pozmieniałem (dopisałem cyfrę 2) do nazw serwisów oraz pozmieniałem nazwy powiązań.
Zmieniłem jeszcze nazwę serwisu w pliku docker-compose.standalone.yml bo podczas uruchomienia skryptu
zgłosił mi błąd
Kod: Zaznacz cały
ERROR: The Compose file is invalid because:
Service supla-cloud has neither an image nor a build context specified. At least one must be provided.
Dopisałem tradycyjnie cyfrę 2:
Kod: Zaznacz cały
version: '3'
services:
supla2-cloud:
ports:
- "${PORT_HTTP}:80"
- "${PORT_HTTPS}:443"
Po ponownym uruchomieniu skryptu
wygląda to lepiej, ale ciągle niezbyt dobrze - trzy kontenery uruchamiają się prawidłowo, nie widać żeby miały jakiś wpływ na pierwotny serwer, nie pokazują się błędy.
Działające kontenery - trzy pierwsze to testowa supla, trzy następne to podstawowa (takie nazwy projektów z plików .env żeby je rozróżnić):
Kod: Zaznacz cały
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1522b14e8850 supla/supla-server "/usr/bin/server-ent…" 5 hours ago Up 5 hours 0.0.0.0:2013->2015/tcp, 0.0.0.0:2014->2016/tcp testowa_supla-server
a5f6921c550f supla/supla-cloud "docker-php-entrypoi…" 5 hours ago Up About a minute 0.0.0.0:8082->80/tcp, 0.0.0.0:4445->443/tcp testowa_supla-cloud
32278b934143 mysql:5.7.20 "docker-entrypoint.s…" 5 hours ago Up 5 hours 3306/tcp testowa_supla-db
f8a426634c7e supla/supla-server "/usr/bin/server-ent…" 29 hours ago Up 29 hours 0.0.0.0:2015-2016->2015-2016/tcp podstawowa_supla-server
71acf0483c2f supla/supla-cloud "docker-php-entrypoi…" 29 hours ago Up 29 hours 0.0.0.0:8080->80/tcp, 0.0.0.0:4443->443/tcp podstawowa_supla-cloud
169f3984e590 mysql:5.7.20 "docker-entrypoint.s…" 29 hours ago Up 29 hours 3306/tcp podstawowa_supla-db
Niestety, ale kontener testowa_supla_cloud restartuje się co minutę:
Kod: Zaznacz cały
Waiting for database connection (10)...
Waiting for database connection (9)...
Waiting for database connection (8)...
Waiting for database connection (7)...
Waiting for database connection (6)...
Waiting for database connection (5)...
Waiting for database connection (4)...
Waiting for database connection (3)...
Waiting for database connection (2)...
Waiting for database connection (1)...
In AbstractMySQLDriver.php line 103:
An exception occured in driver: SQLSTATE[HY000] [2002] php_network_getaddre
sses: getaddrinfo failed: Name or service not known
In PDOConnection.php line 47:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name o
r service not known
In PDOConnection.php line 43:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name o
r service not known
In PDOConnection.php line 43:
PDO::__construct(): php_network_getaddresses: getaddrinfo failed: Name or s
ervice not known
doctrine:database:create [--shard SHARD] [--connection [CONNECTION]] [--if-not-exists] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command>
In CheckDbConnectionCommand.php line 28:
Could not connect to to the database.
Application Migrations
In AbstractMySQLDriver.php line 103:
An exception occured in driver: SQLSTATE[HY000] [2002] php_network_getaddre
sses: getaddrinfo failed: Name or service not known
In PDOConnection.php line 47:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name o
r service not known
In PDOConnection.php line 43:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name o
r service not known
In PDOConnection.php line 43:
PDO::__construct(): php_network_getaddresses: getaddrinfo failed: Name or s
ervice not known
doctrine:migrations:migrate [--write-sql] [--dry-run] [--query-time] [--allow-no-migration] [--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>]
Najwyrażniej nie może połączyć się do bazy danych ...
Logi z testowa_supla-db:
Kod: Zaznacz cały
2019-10-06T17:46:26.209909Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-06T17:46:26.213083Z 0 [Note] mysqld (mysqld 5.7.20) starting as process 1 ...
2019-10-06T17:46:26.222064Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-06T17:46:26.222132Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-06T17:46:26.222147Z 0 [Note] InnoDB: Uses event mutexes
2019-10-06T17:46:26.222159Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-06T17:46:26.222172Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-10-06T17:46:26.222183Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-06T17:46:26.222826Z 0 [Note] InnoDB: Number of pools: 1
2019-10-06T17:46:26.223065Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-06T17:46:26.226653Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-10-06T17:46:26.252532Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-06T17:46:26.256407Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-06T17:46:26.513071Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-06T17:46:26.876153Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-06T17:46:26.876952Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-06T17:46:27.087790Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-06T17:46:27.090624Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-06T17:46:27.090681Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-06T17:46:27.091572Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-06T17:46:27.141874Z 0 [Note] InnoDB: 5.7.20 started; log sequence number 12157750
2019-10-06T17:46:27.142527Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2019-10-06T17:46:27.144054Z 0 [Note] Plugin 'FEDERATED' is disabled.
2019-10-06T17:46:27.273372Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2019-10-06T17:46:27.274157Z 0 [Warning] CA certificate ca.pem is self signed.
2019-10-06T17:46:27.278982Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2019-10-06T17:46:27.279081Z 0 [Note] IPv6 is available.
2019-10-06T17:46:27.279102Z 0 [Note] - '::' resolves to '::';
2019-10-06T17:46:27.279152Z 0 [Note] Server socket created on IP: '::'.
2019-10-06T17:46:27.299405Z 0 [Note] InnoDB: Buffer pool(s) load completed at 191006 17:46:27
2019-10-06T17:46:27.389592Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
2019-10-06T17:46:27.389688Z 0 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.
2019-10-06T17:46:27.389715Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
2019-10-06T17:46:27.389821Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.
2019-10-06T17:46:27.389858Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2019-10-06T17:46:27.389916Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2019-10-06T17:46:27.625469Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.
2019-10-06T17:46:27.625616Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2019-10-06T17:46:27.891880Z 0 [Note] Event Scheduler: Loaded 0 events
2019-10-06T17:46:27.892665Z 0 [Note] mysqld: ready for connections.
Version: '5.7.20' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)
2019-10-06T17:46:27.892707Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
2019-10-06T17:46:27.892716Z 0 [Note] Beginning of list of non-natively partitioned tables
2019-10-06T17:46:29.212350Z 0 [Note] End of list of non-natively partitioned tables
I ostatnie logi testowa_supla-server:
Kod: Zaznacz cały
INFO[1570384001.647797] Scheduler version 2.3.4
INFO[1570384001.647968] Started at Sun Oct 6 17:46:41 2019
ERR[1570384001.710933] MySQL - Failed to connect to database.
ERR[1570384001.710959] Can't connect to database!
2019-10-06 17:46:41,712 INFO exited: supla-scheduler (exit status 1; not expected)
2019-10-06 17:46:43,717 INFO spawned: 'supla-server' with pid 17
INFO[1570384003.733984] Server version 2.3.13 [Protocol v10]
INFO[1570384003.734133] Started at Sun Oct 6 17:46:43 2019
ERR[1570384003.795289] MySQL - Failed to connect to database.
ERR[1570384003.795311] Can't connect to database!
2019-10-06 17:46:43,796 INFO exited: supla-server (exit status 1; not expected)
2019-10-06 17:46:44,799 INFO spawned: 'supla-scheduler' with pid 18
2019-10-06 17:46:44,800 INFO gave up: supla-server entered FATAL state, too many start retries too quickly
INFO[1570384004.814121] Scheduler version 2.3.4
INFO[1570384004.814264] Started at Sun Oct 6 17:46:44 2019
ERR[1570384004.886694] MySQL - Failed to connect to database.
ERR[1570384004.886719] Can't connect to database!
2019-10-06 17:46:44,887 INFO exited: supla-scheduler (exit status 1; not expected)
2019-10-06 17:46:45,889 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
W tym miejscu ugrzązłem, nie wiem co dalej ...