首页 > 解决方案 > 升级到 Ubuntu 18.04 后 Gitlab 未启动

问题描述

我已在 Ubuntu 16.04 上成功将 Gitlab 升级到 12.1.6,并检查了一切正常。在确保 Ubuntu 完全是最新的之后,我再次检查:Gitlab 工作。然后我使用该do-release-upgrade命令更新到 Ubuntu 18.04。重启后,似乎一切正常,但 Gitlab 拒绝启动。

我收到以下错误:

fail: alertmanager: runsv not running
fail: gitaly: runsv not running
fail: gitlab-exporter: runsv not running
fail: gitlab-workhorse: runsv not running
fail: grafana: runsv not running
fail: logrotate: runsv not running
fail: nginx: runsv not running
fail: node-exporter: runsv not running
fail: postgres-exporter: runsv not running
fail: postgresql: runsv not running
fail: prometheus: runsv not running
fail: redis: runsv not running
fail: redis-exporter: runsv not running
fail: sidekiq: runsv not running
fail: unicorn: runsv not running

我试过了:

gitlab-ctl reconfigure --> runs with success

我成功安装了runit,重新启动了机器,但错误仍然存​​在

我在这里发现了一个类似的问题:在 Stackoverflow 上,按照说明进行操作(yum --> apt),仍然没有成功

Gitlab 上。这建议运行

sudo systemctl restart gitlab-runsvdir
sudo gitlab-ctl restart

但是第一个命令永远不会完成

我发现了这个:在 Gitlab上运行

sudo gitlab-rake gitlab:env:info --trace

输出:

** Invoke gitlab:env:info (first_time)
** Invoke gitlab_environment (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute gitlab_environment
** Execute gitlab:env:info

System information
System:     Ubuntu 18.04
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.3
Redis Version:  3.2.12
Git Version:    2.24.1
Sidekiq Version:5.2.7
Go Version: unknown
rake aborted!
PG::ConnectionBad: could not connect to server: No such file or directory
    Is the server running locally and accepting
    connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `initialize'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `new'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `connect'

这表明 Postgresql 服务器没有运行。我不知道如何开始。有任何想法吗?

标签: postgresqlgitlabubuntu-18.04

解决方案


遇到同样的问题,我最终/opt/gitlab/embedded/bin/runsvdir-start手动运行。我解决了我的问题,启动了重新配置,然后它从那里开始工作。


推荐阅读