gitlab启动失败,如何解决

发布于:2025-08-06 ⋅ 阅读:(17) ⋅ 点赞:(0)

gitlab重启失败,即使重新初始化也不能将组件重新运行怎么办?

情况如下:


[root@lvs2 ~]# gitlab-ctl restart
fail: gitaly: runsv not running
fail: gitlab-kas: runsv not running
fail: gitlab-workhorse: runsv not running
fail: logrotate: runsv not running
fail: nginx: runsv not running
fail: postgresql: runsv not running
fail: puma: runsv not running
fail: redis: runsv not running
fail: sidekiq: runsv not running
[root@lvs2 ~]# gitlab-ctl status
fail: gitaly: runsv not running
fail: gitlab-kas: runsv not running
fail: gitlab-workhorse: runsv not running
fail: logrotate: runsv not running
fail: nginx: runsv not running
fail: postgresql: runsv not running
fail: puma: runsv not running
fail: redis: runsv not running
fail: sidekiq: runsv not running

所有 GitLab 服务都显示 runsv not running 的问题,99% 是因为底层的 gitlab-runsvdir 服务没有启动。

直接按下面 2 步即可恢复,无需重装:

步骤 1:手动启动 GitLab 的 runsvdir 服务

sudo systemctl start gitlab-runsvdir.service

步骤 2:重启 GitLab 所有组件

sudo gitlab-ctl restart

验证

sudo gitlab-ctl status

正常情况下应该看到所有服务状态为 run

如果 systemctl start gitlab-runsvdir.service 卡住不动
极个别机器可能因为 plymouth-quit-wait.service 阻塞,先停掉它再继续:

sudo systemctl stop plymouth-quit-wait.service
sudo systemctl start gitlab-runsvdir.service
sudo gitlab-ctl restart

网页访问即可,可能反应没那么快刷新即可


网站公告

今日签到

点亮在社区的每一天
去签到