Postgres not starting up after upgrade to 10.1.0-co
After upgrading to latest from the version installed following the Azure setup tutorial at
https://about.gitlab.com/2016/07/13/how-to-setup-a-gitlab-instance-on-microsoft-azure/
I was able to play around with the new server, but following the update advice from above page:
sudo apt-get update && sudo apt-get install gitlab-ce
, gitlab shows a "502 Gitlab is not responding" pages.
The update had trouble connecting to postgres, so I looked at the postgres logs at /var/log/gitlab/postgresql/current and found this:
2017-10-26_09:28:20.23412 FATAL: configuration file "/var/opt/gitlab/postgresql/data/runtime.conf" contains errors
2017-10-26_09:28:21.23792 LOG: skipping missing configuration file "/var/opt/gitlab/postgresql/data/postgresql.auto.conf"
2017-10-26_09:28:21.23793 LOG: unrecognized configuration parameter "unix_socket_directory" in file "/var/opt/gitlab/postgresql/data/postgresql.conf" line 72
2017-10-26_09:28:21.23794 LOG: unrecognized configuration parameter "checkpoint_segments" in file "/var/opt/gitlab/postgresql/data/runtime.conf" line 14
repeated all over.
Additional infos:
xxxx@Gitlab:~$ dpkg -s gitlab-ce
Package: gitlab-ce
Status: install ok installed
Priority: extra
Section: misc
Installed-Size: 1094496
Maintainer: GitLab, Inc. <support@gitlab.com>
Architecture: amd64
Version: 10.1.0-ce.0
Replaces: gitlab-ee, gitlab
Depends: openssh-server
Conflicts: gitlab-ee, gitlab
Description: GitLab Community Edition (including NGINX, Postgres, Redis)
License: MIT
Vendor: Omnibus <omnibus@getchef.com>
Homepage: https://about.gitlab.com/
xxx2@Gitlab:~$ sudo gitlab-ctl status
run: gitlab-workhorse: (pid 1132) 1748s; run: log: (pid 1131) 1748s
run: logrotate: (pid 1137) 1748s; run: log: (pid 1135) 1748s
run: nginx: (pid 1095) 1748s; run: log: (pid 1094) 1748s
down: postgresql: 0s, normally up, want up; run: log: (pid 1130) 1748s
run: redis: (pid 1133) 1748s; run: log: (pid 1097) 1748s
run: sidekiq: (pid 7304) 8s; run: log: (pid 1091) 1748s
run: unicorn: (pid 7318) 5s; run: log: (pid 1093) 1748s