GitLab

Created by: pspoerri

1. Summary: Gitlab 5-2-stable won't start sidekiq if application is started through mod_passenger

2. Steps: Install Passenger See http://www.modrails.com/documentation/Users%20guide%20Apache.html#rubygems_generic_install for install instructions. But gem install passenger should be sufficient:

   gem install passenger

   Then run

   passenger-install-apache2-module

   to compile passenger. Follow the installation instruction printed to stdout. Files in /etc/apache/ need to be created and modified. Restart apache. Create a vhost for gitlab and setup gitlab in /home/git/ according to the setup guide https://github.com/gitlabhq/gitlabhq/blob/5-2-stable/doc/install/installation.md :

   <VirtualHost *:443>
     ServerName git.example.net
     DocumentRoot /home/git/gitlab/public
     <Directory /home/git/gitlab/public >
          Allow from all
          Options -MultiViews
     </Directory>
     [...] 
   </VirtualHost>

   Restart apache.

3. Expected behavior: Gitlab should now be available on git.example.net.

4. Observed behavior: The website is available but services that are executed with sidekiq are not executed.

5. Relevant logs: Rack starts instances of gitlab: git 15220 0.0 0.4 38260 8372 ? S 11:22 0:00 python2 /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/gitlab-pygments.rb-0.3.2/lib/pygments/mentos.py git 15245 0.0 5.2 354196 108176 ? Sl 11:22 0:00 Rack: /home/git/gitlab git 15253 0.1 6.0 371224 123904 ? Sl 11:22 0:04 Rack: /home/git/gitlab git 15259 0.0 5.0 351300 104324 ? Sl 11:22 0:00 Rack: /home/git/gitlab

6. Output of checks: All checks are good. Except for sidekiq. Sorry I can't provide detailed checks since it's currently running in a productive environment.

7. Possible fixes:

   • Start sidekiq with an init script
   • Setup sidekiq in rails rack middleware config config.ru. Unfortunately I'm not really familiar with these settings. So I don't have an idea on how to setup this. Configuring this in apache would be beneficial.