Skip to content

Instantly share code, notes, and snippets.

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

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

Select an option

Save hgomez/9736430 to your computer and use it in GitHub Desktop.
gitlab-sidekiq-error

Error at server start

Starting the GitLab Unicorn web server...
Starting the GitLab Sidekiq event dispatcher...
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)>'
Tasks: TOP => sidekiq:start
(See full trace by running task with --trace)
The GitLab Unicorn webserver with pid 2710 is running.
The GitLab Sidekiq job dispatcher with pid 2854 is running.
GitLab and all it's components are up and running.

All processes are up

gitlab    2710 16.9  3.3 382012 136396 ?       Sl   09:32   0:21 unicorn_rails master -D -c /var/lib/mycorp/gitlab/gitlab/config/unicorn.rb -E production                                                           
gitlab    2788  0.0  3.1 382012 129188 ?       Sl   09:33   0:00 unicorn_rails worker[0] -D -c /var/lib/mycorp/gitlab/gitlab/config/unicorn.rb -E production                                                        
gitlab    2791  0.0  3.1 382012 129192 ?       Sl   09:33   0:00 unicorn_rails worker[1] -D -c /var/lib/mycorp/gitlab/gitlab/config/unicorn.rb -E production                                                        
gitlab    2794  0.0  3.1 382012 129212 ?       Sl   09:33   0:00 unicorn_rails worker[2] -D -c /var/lib/mycorp/gitlab/gitlab/config/unicorn.rb -E production                                                        
gitlab    2797  0.0  3.1 382012 129228 ?       Sl   09:33   0:00 unicorn_rails worker[3] -D -c /var/lib/mycorp/gitlab/gitlab/config/unicorn.rb -E production                                                        
gitlab    2854 23.8  3.2 2386860 132868 ?      Sl   09:33   0:21 sidekiq 2.17.0 gitlab [0 of 25 busy]                                                          

sidekick log :

2014-03-24T08:29:43Z 31837 TID-oqhz8 INFO: Pushed 0 messages back to Redis
2014-03-24T08:29:43Z 31837 TID-oqhz8 INFO: Pushed 0 messages back to Redis
2014-03-24T08:29:43Z 31837 TID-oqhz8 INFO: Pushed 0 messages back to Redis
2014-03-24T08:29:43Z 31837 TID-oqhz8 INFO: Pushed 0 messages back to Redis
2014-03-24T08:29:43Z 31837 TID-oqhz8 INFO: Pushed 0 messages back to Redis
2014-03-24T08:29:43Z 31837 TID-oqhz8 INFO: Pushed 0 messages back to Redis
2014-03-24T08:29:43Z 31837 TID-oqhz8 INFO: Pushed 0 messages back to Redis
2014-03-24T08:29:43Z 31837 TID-oqhz8 INFO: Pushed 0 messages back to Redis
Sidekiq shut down gracefully.
Instance method "lock!" is already defined in ActiveRecord::Base, use generic helper instead or set StateMachine::Machine.ignore_method_conflicts = true.
Sidekiq shut down gracefully.
Instance method "lock!" is already defined in ActiveRecord::Base, use generic helper instead or set StateMachine::Machine.ignore_method_conflicts = true.
Both MergeRequestDiff and its :state machine have defined a different default for "state". Use only one or the other for defining defaults to avoid unexpected behaviors.
2014-03-24T08:33:55Z 2854 TID-bpi8s INFO: Booting Sidekiq 2.17.0 with redis options {:url=>"redis://localhost:6379", :namespace=>"resque:gitlab"}
2014-03-24T08:33:56Z 2854 TID-bpi8s INFO: Running in ruby 1.9.3p392 (2013-02-22) [x86_64-linux]
2014-03-24T08:33:56Z 2854 TID-bpi8s INFO: See LICENSE and the LGPL-3.0 for licensing details.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment