GitLab Maintenance commands
The following commands can be run after installation. Get service status Run sudo gitlab-ctl status to see the current state and uptime of each GitLab component. The output will look similar to this: run: nginx: (pid 972) 7s; run: log: (pid 971) 7s run: postgresql: (pid 962) 7s; run: log: (pid 959) 7s run: redis: (pid 964) 7s; run: log: (pid 963) 7s run: sidekiq: (pid 967) 7s; run: log: (pid 966) 7s run: puma: (pid 961) 7s; run: log: (pid 960) 7s As a demonstration, the first line of the previous example can be interpreted as follows: Nginx is the process name. 972 is the process identifier. NGINX has been running for 7 seconds ( 7s ). log indicates a svlogd logging process attached to the preceding process. 971 is the process identifier for the logging process. The logging process has been running for 7 seconds ( 7s ). Tail process logs See settings/logs.md. Starting and stopping After Omnibus GitLab is installed and configured, your server has a runit service directory ( r