解决GITLAB无法启动runsv no running

可以先尝试用

systemctl start gitlab-runsvdir.service

如果冻结不动的话，就需要查看系统服务项了

systemctl -t target

如果系统正常的话，所有任务应该是loaded active active，如果存在inactive dead选型，意味着有些服务出错了。

UNIT                   LOAD   ACTIVE SUB    DESCRIPTION
basic.target           loaded active active Basic System
cloud-config.target    loaded active active Cloud-config availability
cloud-init.target      loaded active active Cloud-init target
cryptsetup.target      loaded active active Encrypted Volumes
getty.target           loaded active active Login Prompts
graphical.target       loaded active active Graphical Interface
local-fs-pre.target    loaded active active Local File Systems (Pre)
local-fs.target        loaded active active Local File Systems
multi-user.target      loaded active active Multi-User System
network-online.target  loaded active active Network is Online
network-pre.target     loaded active active Network (Pre)
network.target         loaded active active Network
nss-user-lookup.target loaded active active User and Group Name Lookups
paths.target           loaded active active Paths
remote-fs-pre.target   loaded active active Remote File Systems (Pre)
remote-fs.target       loaded active active Remote File Systems
slices.target          loaded active active Slices
sockets.target         loaded active active Sockets
swap.target            loaded active active Swap
sysinit.target         loaded active active System Initialization
time-sync.target       loaded active active System Time Synchronized
timers.target          loaded active active Timers

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

multi-user.target      loaded inactive dead   start Multi-User System

这时候使用

systemctl list-jobs

如果存在某个任务是running，则是该任务堵塞了其他所有服务。

  graphical.target                     start waiting
 plymouth-quit-wait.service           start running
   multi-user.target                    start waiting
 ureadahead-stop.timer                start waiting
 gitlab-runsvdir.service              start waiting
 system-getty.slice                   start waiting
  setvtrgb.service                     start waiting
 systemd-update-utmp-runlevel.service start waiting

此时就可以利用 systemctl stop plymouth-quit-wait.service结束该任务。

然后重启gitlab即可。

https://docs.gitlab.com/omnibus/common_installation_problems/#gitlab-runsvdir-not-starting