gitlab启动失败,如何解决

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

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

相关推荐
__Smile°21 小时前
Gitlab+Jenkins+K8S+Registry 建立 CI/CD 流水线
linux·ci/cd·docker·kubernetes·gitlab·jenkins
yangrenrui1 天前
GitLab:一站式 DevOps 平台的全方位解析
运维·gitlab·devops
流泪兔兔头2 天前
GitLab 同时拣选多个分支
gitlab
hi_link3 天前
idea添加gitlab访问令牌
gitlab
gs801403 天前
解决 GitLab external_url 修改无效的问题:保留数据重新生成配置
gitlab
gs801404 天前
GitLab Docker Compose 迁移后 Redis 权限问题排查与解决
redis·docker·gitlab
Doris_LMS4 天前
Git、Gitee、GitHub、GitLab完整讲解:从基础到进阶
git·gitee·gitlab·github
Allen正心正念20255 天前
GitLab 中的分支和标签的定义及操作
gitlab