Ferramentas de Utilizador

Ferramentas de Site


sistemas:gitlab

Corrigindo problema: runsv not running após queda de energia

Exemplo:

root@gitlab:~# gitlab-ctl status
fail: gitlab-workhorse: runsv not running
fail: logrotate: runsv not running
fail: nginx: runsv not running
fail: postgresql: runsv not running
fail: redis: runsv not running
fail: registry: runsv not running
fail: sidekiq: runsv not running
fail: unicorn: runsv not running
root@gitlab:~# gitlab-ctl stop
fail: gitlab-workhorse: runsv not running
fail: logrotate: runsv not running
fail: nginx: runsv not running
fail: postgresql: runsv not running
fail: redis: runsv not running
fail: registry: runsv not running
fail: sidekiq: runsv not running
fail: unicorn: runsv not running

Passo 1: parar o gitlab-runsvdir

root@gitlab:~# initctl stop gitlab-runsvdir
gitlab-runsvdir stop/waiting

Passo 2: acessar o gitlab-runsvdir

root@gitlab:~# initctl start gitlab-runsvdir
gitlab-runsvdir start/running, process 1708

Passo 3: ver o status do gitlab

root@gitlab:~# gitlab-ctl status
run: gitlab-workhorse: (pid 18665) 4s; run: log: (pid 18775) 0s
run: logrotate: (pid 18672) 4s; run: log: (pid 18776) 0s
run: nginx: (pid 18759) 1s; run: log: (pid 18778) 0s
down: postgresql: 0s, normally up, want up; run: log: (pid 18769) 0s
run: redis: (pid 18674) 4s; run: log: (pid 18772) 0s
down: registry: 0s, normally up, want up; run: log: (pid 18773) 0s
run: sidekiq: (pid 18675) 4s; run: log: (pid 18771) 0s
run: unicorn: (pid 18669) 4s; run: log: (pid 18777) 0s
sistemas/gitlab.txt · Esta página foi modificada pela última vez em: 2017/03/28 15:35 (Edição externa)