Skip to content

Disable start on reboot

reboot
gitlab-ctl status
Output: 
run: alertmanager: (pid 7450) 33s; run: log: (pid 7441) 33s
run: gitaly: (pid 7444) 33s; run: log: (pid 7435) 33s
run: gitlab-exporter: (pid 7445) 33s; run: log: (pid 7434) 33s
run: gitlab-kas: (pid 7455) 33s; run: log: (pid 7439) 33s
run: gitlab-workhorse: (pid 7459) 33s; run: log: (pid 7454) 33s
run: logrotate: (pid 7457) 33s; run: log: (pid 7446) 33s
run: node-exporter: (pid 7449) 33s; run: log: (pid 7437) 33s
run: postgres-exporter: (pid 7453) 33s; run: log: (pid 7440) 33s
run: postgresql: (pid 7460) 33s; run: log: (pid 7447) 33s
run: prometheus: (pid 7442) 33s; run: log: (pid 7433) 33s
run: puma: (pid 7451) 33s; run: log: (pid 7436) 33s
run: redis: (pid 7452) 33s; run: log: (pid 7443) 33s
run: redis-exporter: (pid 7456) 33s; run: log: (pid 7438) 33s
run: sidekiq: (pid 7458) 33s; run: log: (pid 7448) 33s
time gitlab-ctl stop
Output: 
ok: down: alertmanager: 0s, normally up
ok: down: gitaly: 0s, normally up
ok: down: gitlab-exporter: 0s, normally up
ok: down: gitlab-kas: 0s, normally up
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: node-exporter: 1s, normally up
ok: down: postgres-exporter: 0s, normally up
ok: down: postgresql: 0s, normally up
ok: down: prometheus: 0s, normally up
ok: down: puma: 1s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 0s, normally up
ok: down: sidekiq: 0s, normally up
gitlab-ctl status
Output: 
down: alertmanager: 95s, normally up; run: log: (pid 7441) 133s
down: gitaly: 95s, normally up; run: log: (pid 7435) 133s
down: gitlab-exporter: 94s, normally up; run: log: (pid 7434) 133s
down: gitlab-kas: 83s, normally up; run: log: (pid 7439) 133s
down: gitlab-workhorse: 83s, normally up; run: log: (pid 7454) 133s
down: logrotate: 82s, normally up; run: log: (pid 7446) 133s
down: node-exporter: 82s, normally up; run: log: (pid 7437) 133s
down: postgres-exporter: 81s, normally up; run: log: (pid 7440) 133s
down: postgresql: 80s, normally up; run: log: (pid 7447) 133s
down: prometheus: 80s, normally up; run: log: (pid 7433) 133s
down: puma: 80s, normally up; run: log: (pid 7436) 133s
down: redis: 79s, normally up; run: log: (pid 7443) 133s
down: redis-exporter: 78s, normally up; run: log: (pid 7438) 133s
down: sidekiq: 77s, normally up; run: log: (pid 7448) 133s
systemctl disable gitlab-runsvdir
Removed "/etc/systemd/system/multi-user.target.wants/gitlab-runsvdir.service".

Source: the Super User answer 1760179

reboot
gitlab-ctl status
Output: 
fail: alertmanager: runsv not running
fail: gitaly: runsv not running
fail: gitlab-exporter: runsv not running
fail: gitlab-kas: runsv not running
fail: gitlab-workhorse: runsv not running
fail: logrotate: 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: puma: runsv not running
fail: redis: runsv not running
fail: redis-exporter: runsv not running
fail: sidekiq: runsv not running

Related to OverClock3000/issues/12.

Before raising an issue to the GitLab issue tracker, please read through our guide for finding help to determine the best place to post:

If you are experiencing an issue when using GitLab.com, your first port of call should be the Community Forum. Your issue may have already been reported there by another user. Please check:

If you feel that your issue can be categorized as a reproducible bug or a feature proposal, please use one of the issue templates provided and include as much information as possible.

Thank you for helping to make GitLab a better product.

Edited by Benjamin Loison