Keywords: GitLab - Virtual Machines - How to - Upgrade
Description:
Hello,
I'm trying to upgrade our Gitlab CE 8.14.3 to 9.1.10 by following support's suggestion here:
https://community.bitnami.com/t/upgrade-bitnami-gitlab-ce-version/48641
I'm already in step 4 but could not startup the Gitlab Omnibus 9.1.10. I get this error:
ok: down: gitlab-workhorse: 0s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 1s, normally up
ok: down: postgresql: 0s, normally up
ok: down: redis: 1s, normally up
ok: down: sidekiq: 0s, normally up
ok: down: unicorn: 0s, normally up
timeout: down: postgresql: 1s, normally up, want up
ok: run: redis: (pid 25298) 0s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1711s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1712s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1713s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1714s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1715s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1716s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1717s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1718s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1719s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1720s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1721s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1722s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1723s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1724s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1725s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1726s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1727s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1728s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1729s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1730s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1731s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1732s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1733s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1734s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1735s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1736s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1737s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1738s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1739s
down: postgresql: 0s, normally up, want up; run: log: (pid 17140) 1740s
Failed to start postgresql for migrations
dpkg: error processing package gitlab-ce (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.19-0ubuntu6.15) ...
Processing triggers for initramfs-tools (0.103ubuntu4.11) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-105-generic
Processing triggers for ureadahead (0.100.0-16) ...
Processing triggers for ca-certificates (20170717~14.04.2) ...
Updating certificates in /etc/ssl/certs... 17 added, 42 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Errors were encountered while processing:
gitlab-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have already tried cleaning the package manager using these commands:
sudo apt-get clean
sudo dpkg --configure -a
sudo apt-get install -f
sudo apt-get autoremove
Also removing and rebuild the package list
sudo rm -rf /var/lib/apt/lists/*
sudo apt-get update
sudo apt-get clean
But still could not run postgresql.
Thanks!