Installation production config files

cveronese · December 30, 2021, 2:25pm

Hi folks,
is anybody so kind to provide config files to install production version of Corteza with MySQL?
I’m struggling to use those provided in the documentation but no way.
Each time I start all the containers, I have the reply “503 Service Temporarily unavailable”

Thanks for all your help

darh · December 30, 2021, 2:37pm

Do you have access to corteza server logs?
503 error can mean 1001 thing…

cveronese · January 1, 2022, 11:49pm

Problem is not corteza server but nginx-proxy that somehow is not able to handle requests. Here below the log

Setting up DH Parameters…
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: using the “epoll” event method
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: nginx/1.21.5
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: built by gcc 10.2.1 20210110 (Debian 10.2.1-6)
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: OS: Linux 5.13.0-22-generic
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: getrlimit(RLIMIT_NOFILE): 1048576:1048576
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: start worker processes
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: start worker process 20
dockergen.1 | 2022/01/01 23:36:02 Generated ‘/etc/nginx/conf.d/default.conf’ from 2 containers
dockergen.1 | 2022/01/01 23:36:02 Running ‘nginx -s reload’
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: signal 1 (SIGHUP) received from 22, reconfiguring
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: reconfiguring
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: using the “epoll” event method
dockergen.1 | 2022/01/01 23:36:03 Watching docker events
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: start worker processes
nginx.1 | 2022/01/01 23:36:02 [notice] 16#16: start worker process 27
dockergen.1 | 2022/01/01 23:36:03 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ‘nginx -s reload’
nginx.1 | 2022/01/01 23:36:03 [notice] 20#20: gracefully shutting down
nginx.1 | 2022/01/01 23:36:03 [notice] 20#20: exiting
nginx.1 | 2022/01/01 23:36:03 [notice] 20#20: exit
nginx.1 | 2022/01/01 23:36:03 [notice] 16#16: signal 17 (SIGCHLD) received from 20
nginx.1 | 2022/01/01 23:36:03 [notice] 16#16: worker process 20 exited with code 0
nginx.1 | 2022/01/01 23:36:03 [notice] 16#16: signal 29 (SIGIO) received
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: signal 1 (SIGHUP) received from 38, reconfiguring
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: reconfiguring
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: using the “epoll” event method
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: start worker processes
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: start worker process 39
nginx.1 | 2022/01/01 23:36:05 [notice] 27#27: gracefully shutting down
nginx.1 | 2022/01/01 23:36:05 [notice] 27#27: exiting
nginx.1 | 2022/01/01 23:36:05 [notice] 27#27: exit
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: signal 17 (SIGCHLD) received from 27
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: worker process 27 exited with code 0
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: signal 29 (SIGIO) received
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: signal 1 (SIGHUP) received from 50, reconfiguring
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: reconfiguring
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: using the “epoll” event method
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: start worker processes
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: start worker process 51
nginx.1 | 2022/01/01 23:36:05 [notice] 39#39: gracefully shutting down
nginx.1 | 2022/01/01 23:36:05 [notice] 39#39: exiting
nginx.1 | 2022/01/01 23:36:05 [notice] 39#39: exit
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: signal 17 (SIGCHLD) received from 39
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: worker process 39 exited with code 0
nginx.1 | 2022/01/01 23:36:05 [notice] 16#16: signal 29 (SIGIO) received
nginx.1 | localhost 172.18.0.1 - - [01/Jan/2022:23:37:12 +0000] “GET / HTTP/1.1” 503 190 “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:95.0) Gecko/20100101 Firefox/95.0” “-”
nginx.1 | localhost 172.18.0.1 - - [01/Jan/2022:23:37:12 +0000] “GET /favicon.ico HTTP/1.1” 503 190 “http://localhost/” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:95.0) Gecko/20100101 Firefox/95.0” “-”
nginx.1 | localhost 172.18.0.1 - - [01/Jan/2022:23:40:12 +0000] “GET / HTTP/1.1” 503 190 “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:95.0) Gecko/20100101 Firefox/95.0” “-”

Tried with different versions of LTS Ubuntu server

darh · January 2, 2022, 10:30am

i don’t want to jump into any assumptions but the problem is usually misconfigured docker network settings on either host, nginx container or the final container (corteza in this case).

So…

you can reach your nginx container
Judging from the last lines of the provided log,
nginx container can detect docker events
see signal 1 (SIGHUP) received from 22, reconfiguring
“config did not change skipping” usually means some kind of misconfiguration.

might be that Nginx proxy container is not on the same (external) network (named proxy in corteza’s docs) as your corteza container?
maybe you forgot to set VIRTUAL_HOST env-var on corteza container?

cheers