502 Bad Gateway when trying to add new user or when consulting background jobs
Created by: sinosoidal
Hi,
Today I wanted to add a new user to Gitlab. Usually I would just make it login with it's LDAP credentials. It always worked. Last time I did that was 4 months ago and everything worked fine. I'm pretty sure there wasn't udpates to this machine as it is only used for this end.
I have version 6.0.1 and when I try to run the tests this is the result:
RAILS_ENV=production bundle exec rake gitlab:test --trace
** Invoke gitlab:test (first_time)
rake aborted!
Don't know how to build task 'spinach'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task_manager.rb:49:in []' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:53:in
lookup_prerequisite'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:49:in block in prerequisite_tasks' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:49:in
map'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:49:in prerequisite_tasks' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:195:in
invoke_prerequisites'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:174:in block in invoke_with_call_chain' /usr/local/lib/ruby/2.0.0/monitor.rb:211:in
mon_synchronize'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:168:in invoke_with_call_chain' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:161:in
invoke'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:149:in invoke_task' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:106:in
block (2 levels) in top_level'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:106:in each' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:106:in
block in top_level'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:115:in run_with_threads' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:100:in
top_level'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:78:in block in run' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:165:in
standard_exception_handling'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:75:in run' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/rake-10.1.0/bin/rake:33:in
<top (required)>'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/bin/rake:23:in load' /home/git/gitlab/vendor/bundle/ruby/2.0.0/bin/rake:23:in
'
Tasks: TOP => gitlab:test
Consulting the logs I have the following:
cat unicord.stderr.log:
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.12.4/web/views/dashboard.slim:131071:in instance_eval' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.12.4/web/views/dashboard.slim:39:in
block in singleton class'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.12.4/web/views/dashboard.slim:39:in !~' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.12.4/web/views/dashboard.slim:39:in
=~'
-- C level backtrace information ------------------------------------------- E, [2014-01-14T21:46:09.706908 #578 (closed)] ERROR -- : reaped #<Process::Status: pid 835 SIGSEGV (signal 11)> worker=1 I, [2014-01-14T21:46:09.711131 #987 (closed)] INFO -- : worker=1 ready
cat sidekiq.log
b759a000-b75d9000 rw-p 00000000 00:00 0 b75d9000-b75da000 ---p 00000000 00:00 0 b75da000-b775f000 rw-p 00000000 00:00 0 b7761000-b7762000 ---p 00000000 00:00 0 b7762000-b7767000 rw-p 00000000 00:00 0 bfd58000-bfd6d000 rw-p 00000000 00:00 0 [stack]
[NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html
cat gitlab_error.log
2014/01/14 21:46:09 [error] 433#0: *39 upstream prematurely closed connection while reading response header from upstream, client: 192.168.3.174, server: skinlab.global, request: "GET /admin/sidekiq HTTP/1.1", upstream: "http://unix:/home/git/gitlab/tmp/sockets/gitlab.socket:/admin/sidekiq", host: "skinlab.global", referrer: "http://skinlab.global/admin/background_jobs"
Does anyone has a clue on how to fix this?
Thanks
With my best regards,
Nuno Santos