Over a million developers have joined DZone.

GitLab Service Control Commands

DZone's Guide to

GitLab Service Control Commands

We take a quick look at how to get GitLab to start on system startup with some helpful commands. Read on for the details.

· DevOps Zone ·
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

After installing GitLab from the omnibus install, use the gitlab-ctl command to query status, and start/stop the GitLab service (see here):

$ sudo gitlab-ctl status

If GitLab's main service has been disabled, all the sub-services will report ‘runsv not running’:

fail: gitaly: runsv not running

You can reset the main service to run at startup with (see here):

sudo systemctl enable gitlab-runsvdir.service

To disable startup at boot:

sudo systemctl disable gitlab-runsvdir.service

If runsvdir is not enabled to start at boot, then start with:

sudo systemctl start gitlab-runsvdir.service

To start/stop GitLab:

$ sudo gitlab-ctl start

$ sudo gitlab-ctl stop

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

gitlab ,devops ,commands

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}