postgres error updating to 12.1.6
Summary
Upgrading to gitlab 12.1.6 with docker-compose causes error in postgresql:
==> /var/log/gitlab/postgresql/current <==
2019-08-19_16:02:59.04344 LOG: parameter "ssl" requires a Boolean value
2019-08-19_16:02:59.04346 FATAL: configuration file "/var/opt/gitlab/postgresql/data/postgresql.conf" contains errors
Steps to reproduce
docker-compose pull && docker-compose up -d
What is the current bug behavior?
Gitlab is stuck not starting correctly.
What is the expected correct behavior?
Gitlab should come back up correctly after update
Relevant logs and/or screenshots
==> /var/log/gitlab/postgresql/current <==
2019-08-19_16:18:23.53421 LOG: parameter "ssl" requires a Boolean value
2019-08-19_16:18:23.53424 FATAL: configuration file "/var/opt/gitlab/postgresql/data/postgresql.conf" contains errors
Output of checks
# gitlab-ctl status
run: alertmanager: (pid 16275) 128s; run: log: (pid 630) 3421s
run: crond: (pid 16294) 127s; run: log: (pid 762) 3409s
run: gitaly: (pid 6551) 2407s; run: log: (pid 397) 3444s
run: gitlab-monitor: (pid 16304) 127s; run: log: (pid 571) 3426s
run: gitlab-workhorse: (pid 16312) 126s; run: log: (pid 499) 3430s
run: grafana: (pid 16326) 126s; run: log: (pid 700) 3415s
run: logrotate: (pid 16347) 125s; run: log: (pid 532) 3428s
run: nginx: (pid 16354) 125s; run: log: (pid 510) 3429s
run: postgres-exporter: (pid 16366) 125s; run: log: (pid 678) 3416s
down: postgresql: 1s, normally up, want up; run: log: (pid 410) 3438s
run: prometheus: (pid 16379) 122s; run: log: (pid 606) 3424s
run: redis: (pid 6907) 2374s; run: log: (pid 265) 3450s
run: redis-exporter: (pid 16396) 122s; run: log: (pid 602) 3425s
run: registry: (pid 16401) 122s; run: log: (pid 554) 3427s
run: sidekiq: (pid 17064) 7s; run: log: (pid 480) 3431s
run: sshd: (pid 16423) 121s; run: log: (pid 25) 3462s
run: unicorn: (pid 17034) 11s; run: log: (pid 463) 3432s
Results of GitLab environment info
System information
System:
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.6.3p62
Gem Version: 2.7.9
Bundler Version:1.17.3
Rake Version: 12.3.2
Redis Version: 3.2.12
Git Version: 2.21.0
Sidekiq Version:5.2.7
Go Version: unknown
rake aborted!
PG::ConnectionBad: could not connect to server: Connection refused
Is the server running on host "172.17.0.2" and accepting
TCP/IP connections on port 5432?
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/info.rake:48:in `block (3 levels) in <top (required)>'
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'
Tasks: TOP => gitlab:env:info
(See full trace by running task with --trace)
Results of GitLab application Check
# gitlab-rake gitlab:check SANITIZE=true
Checking GitLab subtasks ...
rake aborted!
PG::ConnectionBad: could not connect to server: Connection refused
Is the server running on host "172.17.0.2" and accepting
TCP/IP connections on port 5432?
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:36:in `block in enabled?'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:96:in `block (2 levels) in cache_value'
/opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/json_cache.rb:51:in `fetch'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:96:in `block in cache_value'
/opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/json_cache.rb:51:in `fetch'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:95:in `cache_value'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:36:in `enabled?'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/ee/system_check/rake_task/gitlab_task.rb:16:in `subtasks'
/opt/gitlab/embedded/service/gitlab-rails/lib/system_check/rake_task/gitlab_task.rb:16:in `manual_run_checks!'
/opt/gitlab/embedded/service/gitlab-rails/lib/system_check/rake_task/rake_task_helpers.rb:13:in `run!'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/check.rake:4:in `block (2 levels) in <top (required)>'
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'
Tasks: TOP => gitlab:check
(See full trace by running task with --trace)
Possible fixes
Unknown