Gitlab 5.0: sudo service gitlab stop must stop all gitlab processes at all times.

[sivabalan]

On running sudo service gitlab start the following processes start up:

git 2507 24.3 0.6 918716 110576 pts/5 Sl 21:44 0:19 unicorn_rails master -c /home/git/gitlab/config/unicorn.rb -E production
git 2577 0.1 0.0 50860 10468 pts/5 S 21:44 0:00 python2 /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/gitlab-pygments.rb-0.3.2/lib/pygments/mentos.py
git 2594 26.0 0.6 3070944 114068 pts/5 Sl 21:44 0:18 sidekiq 2.7.5 gitlab [0 of 25 busy]
git 2618 0.1 0.0 49400 10412 pts/5 S 21:44 0:00 python2 /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/gitlab-pygments.rb-0.3.2/lib/pygments/mentos.py
git 2628 0.0 0.6 919376 104624 pts/5 Sl 21:44 0:00 unicorn_rails worker[0] -c /home/git/gitlab/config/unicorn.rb -E production
git 2634 0.0 0.6 919376 104600 pts/5 Sl 21:44 0:00 unicorn_rails worker[1] -c /home/git/gitlab/config/unicorn.rb -E production
postgres 2646 0.0 0.0 128376 6376 ? Ss 21:44 0:00 postgres: gitlab gitlabhq_production [local] idle
After that, if the service is stopped and started in quick succession a few times, (More specifically on quick repetitions of sudo service gitlab restart) from then on a subset of the processes listed above seem to keep on running forever unless manually terminated.

This problem seems to get in the way mainly when testing out various configurations of the gitlab server ie,. in the case when quick reloads of the gitlab server are required.

[axilleas]

This seems to have happened because sidekiq was being started in the background and it couldn't follow the other services. I believe this is now fixed with commit gitlabhq/gitlabhq@ec38d62#L0R86. If this persists please fill a bug report in https://github.com/gitlabhq/gitlabhq/issues.

Thank you.