Re: Supla ❤ Docker
: pt paź 19, 2018 12:00 pm
Hej,
Mam problemy z postawieniem dockera, w teori wszystko wstało i z tego co mi się zdaje nie ma żadnych błędów, ale gdy próbuje wejść na adres który podałem w .env nic mi nie odpowiada, czy jest jakaś możliwość sprawdzenia gdzie jest pod jakim adresem strona działa?
Logi z cloud:
Log supla-server
Mam problemy z postawieniem dockera, w teori wszystko wstało i z tego co mi się zdaje nie ma żadnych błędów, ale gdy próbuje wejść na adres który podałem w .env nic mi nie odpowiada, czy jest jakaś możliwość sprawdzenia gdzie jest pod jakim adresem strona działa?
Logi z cloud:
Kod: Zaznacz cały
[Fri Oct 19 07:29:43.621352 2018] [mpm_prefork:notice] [pid 49] AH00169: caught SIGTERM, shutting down
2018-10-19 07:29:43,647 INFO stopped: apache (exit status 0)
Database connection has been established.
Application Migrations
No migrations to execute.
// Warming up the cache for the prod environment with debug
// false
[OK] Cache for the "prod" environment (debug=false) was successfully warmed.
2018-10-19 07:29:53,701 CRIT Supervisor running as root (no user in config file)
2018-10-19 07:29:53,703 INFO supervisord started with pid 1
2018-10-19 07:29:54,710 INFO spawned: 'apache' with pid 49
2018-10-19 07:29:54,758 INFO spawned: 'cron' with pid 50
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
[Fri Oct 19 07:29:54.912591 2018] [ssl:warn] [pid 49] AH01906: 172.18.0.3:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Fri Oct 19 07:29:54.912766 2018] [ssl:warn] [pid 49] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
[Fri Oct 19 07:29:54.941141 2018] [ssl:warn] [pid 49] AH01906: 172.18.0.3:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Fri Oct 19 07:29:54.941534 2018] [ssl:warn] [pid 49] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
[Fri Oct 19 07:29:54.943146 2018] [mpm_prefork:notice] [pid 49] AH00163: Apache/2.4.10 (Debian) PHP/7.0.26 OpenSSL/1.0.1t configured -- resuming normal operations
[Fri Oct 19 07:29:54.943332 2018] [core:notice] [pid 49] AH00094: Command line: 'apache2 -D FOREGROUND'
2018-10-19 07:29:55,950 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-10-19 07:29:55,953 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Kod: Zaznacz cały
2018-10-19 07:26:45,943 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-10-19 07:29:43,103 WARN received SIGTERM indicating exit request
2018-10-19 07:29:43,103 INFO waiting for supla-scheduler, supla-server to die
INFO[1539934183.103904] Shutting down...
ERR[1539934183.104007] IPC connection accept error 9
ERR[1539934183.104248] Connection accept error 9
ERR[1539934183.104291] Connection accept error 9
INFO[1539934183.104417] Stopped at Fri Oct 19 07:29:43 2018
2018-10-19 07:29:43,105 INFO stopped: supla-server (exit status 0)
INFO[1539934183.105311] Shutting down...
INFO[1539934183.105517] Stopped at Fri Oct 19 07:29:43 2018
2018-10-19 07:29:43,106 INFO stopped: supla-scheduler (exit status 0)
2018-10-19 07:29:49,608 CRIT Supervisor running as root (no user in config file)
2018-10-19 07:29:49,610 INFO supervisord started with pid 1
2018-10-19 07:29:50,618 INFO spawned: 'supla-scheduler' with pid 9
2018-10-19 07:29:50,655 INFO spawned: 'supla-server' with pid 10
INFO[1539934190.676215] Scheduler version 2.2.0
INFO[1539934190.677415] Server version 2.2.0 [Protocol v9], 32
INFO[1539934190.678186] Started at Fri Oct 19 07:29:50 2018
INFO[1539934190.681202] Started at Fri Oct 19 07:29:50 2018
INFO[1539934190.692863] SSL version: OpenSSL 1.0.1t 3 May 2016
2018-10-19 07:29:51,694 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-10-19 07:29:51,694 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)