Skip to content

Instantly share code, notes, and snippets.

@hgomez
Last active August 29, 2015 13:56
Show Gist options
  • Select an option

  • Save hgomez/9253016 to your computer and use it in GitHub Desktop.

Select an option

Save hgomez/9253016 to your computer and use it in GitHub Desktop.
Update to gitlab 6.6.4 worked but system didn't start
Starting the GitLab Unicorn web server...
Starting the GitLab Sidekiq event dispatcher...
** Invoke sidekiq:start (first_time)
** Execute sidekiq:start
rake aborted!
SIGTERM
/var/lib/mycorp/gitlab/gitlab/lib/tasks/sidekiq.rake:9:in `system'
/var/lib/mycorp/gitlab/gitlab/lib/tasks/sidekiq.rake:9:in `block (2 levels) in <top (required)>'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/task.rb:236:in `call'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/task.rb:236:in `block in execute'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/task.rb:231:in `each'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/task.rb:231:in `execute'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/task.rb:175:in `block in invoke_with_call_chain'
/usr/lib64/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/task.rb:168:in `invoke_with_call_chain'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/task.rb:161:in `invoke'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:149:in `invoke_task'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:106:in `block (2 levels) in top_level'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:106:in `each'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:106:in `block in top_level'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:115:in `run_with_threads'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:100:in `top_level'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:78:in `block in run'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:165:in `standard_exception_handling'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/lib/rake/application.rb:75:in `run'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.1.1/bin/rake:33:in `<top (required)>'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/bin/rake:23:in `load'
/var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/1.9.1/bin/rake:23:in `<main>'
Tasks: TOP => sidekiq:start
The GitLab Unicorn webserver with pid 10327 is running.
The GitLab Sidekiq job dispatcher with pid 10373 is running.
GitLab and all it's components are up and running.
@ruurdadema

Copy link
Copy Markdown

What did the test tell you?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment