Troubleshooting your GitLab installation

When your GitLab instance does not work the way you expect it to work, it's nice to have a way to check what parts of your installation are not working properly. In this recipe, we will take a look at the self-diagnostic tools provided by GitLab.

How to do it…

Learn how to troubleshoot your GitLab server with the following steps:

1. Log in to your server using SSH.

   The first case shows troubleshooting in the case of a GitLab source installation.

2. Go to your gitlab folder:

   $ cd /home/git/gitlab
   

3. To autodiagnose your installation, run the following command:

   $ sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
   

4. When there is a problem with your GitLab installation, it will be outputted in red text, as shown in the following screenshot:

   

5. The solution for the problem is also given; just follow the explanation given by the problem you walk into. In this case, we have to run the following command:

   $ sudo-u git -h bundle exec rake  gitlab:satellites:create...