Depending on how you installed GitSwarm, there are different methods to restart its service(s).
If you want the TL;DR versions, jump to:
If you have used the GitSwarm packages for installation, then you should already have gitswarm-ctl in your PATH.
gitswarm-ctl interacts with the packages and can be used to restart GitSwarm, specifically the Unicorn web server, as well as the other components:
There may be times in the documentation where you will be asked to restart GitSwarm. In that case, you need to run the following command:
sudo gitswarm-ctl restartThe output should be similar to this:
ok: run: gitlab-workhorse: (pid 11291) 1s
ok: run: logrotate: (pid 11299) 0s
ok: run: mailroom: (pid 11306) 0s
ok: run: nginx: (pid 11309) 0s
ok: run: postgresql: (pid 11316) 1s
ok: run: redis: (pid 11325) 0s
ok: run: sidekiq: (pid 11331) 1s
ok: run: unicorn: (pid 11338) 0sTo restart a component separately, you can append its service name to the restart command. For example, to restart only Nginx you would run:
sudo gitswarm-ctl restart nginxTo check the status of GitSwarm services, run:
sudo gitswarm-ctl statusNotice that all services say ok: run.
Sometimes, components time out during the restart and sometimes they get stuck. In that case, you can use gitswarm-ctl kill <service> to send the SIGKILL signal to the service, for example sidekiq. After that, a restart should perform fine.
As a last resort, you can try to reconfigure GitSwarm instead.
There may be times in the documentation where you will be asked to reconfigure GitSwarm. Remember that this method applies only for package installations.
Reconfigure GitSwarm with:
sudo gitswarm-ctl reconfigureReconfiguring GitSwarm should occur in the event that something in its configuration (/etc/gitswarm/gitswarm.rb) has changed.
When you run this command, Chef, the underlying configuration management application that powers GitSwarm, ensures that all directories, permissions, services, etc., are in place and in the same shape that they were initially shipped.
It also restarts GitSwarm components where needed, if any of their configuration files have changed.
If you manually edit any files in /var/opt/gitswarm that are managed by Chef, running reconfigure reverts the changes AND restarts the services that depend on those files.
If you have followed the official installation guide to install GitSwarm from source, run the following command to restart GitSwarm:
sudo service gitswarm restartThe output should be similar to this:
Shutting down GitLab Unicorn
Shutting down GitLab Sidekiq
Shutting down GitLab Workhorse
Shutting down GitLab MailRoom
...
GitLab is not running.
Starting GitLab Unicorn
Starting GitLab Sidekiq
Starting GitLab Workhorse
Starting GitLab MailRoom
...
The GitLab Unicorn web server with pid 28059 is running.
The GitLab Sidekiq job dispatcher with pid 28176 is running.
The GitLab Workhorse with pid 28122 is running.
The GitLab MailRoom email processor with pid 28114 is running.
GitLab and all its components are up and running.This should restart Unicorn, Sidekiq, GitLab Workhorse and Mailroom (if enabled). The init service file that does all the magic can be found on your server in /etc/init.d/gitswarm.
If you are using other init systems, like systemd, you can check the GitLab Recipes repository for some unofficial services. These are not officially supported so use them at your own risk.