4

gitlab looks like it should be ok, but it is not - page returns always:

502 Whoops, GitLab is taking too much time to respond.

Status:

$ gitlab-ctl status
run: gitlab-workhorse: (pid 10244) 718s; run: log: (pid 6421) 2922s
run: logrotate: (pid 10252) 717s; run: log: (pid 6541) 2920s
run: nginx: (pid 10258) 717s; run: log: (pid 6422) 2922s
run: postgresql: (pid 10270) 716s; run: log: (pid 6486) 2921s
run: redis: (pid 10282) 716s; run: log: (pid 6420) 2922s
run: sidekiq: (pid 20207) 6s; run: log: (pid 6426) 2922s
run: unicorn: (pid 20224) 1s; run: log: (pid 6484) 2921s

Tail shows these lines repeatedly:

$ gitlab-ctl tail
==> /var/log/gitlab/unicorn/current <==
2015-12-29_15:16:53.75860 master failed to start, check stderr log for details
2015-12-29_15:16:54.76660 failed to start a new unicorn master
2015-12-29_15:16:54.77909 starting new unicorn master

==> /var/log/gitlab/unicorn/unicorn_stderr.log <==
I, [2015-12-29T16:16:55.903009 #20344]  INFO -- : Refreshing Gem list

==> /var/log/gitlab/unicorn/current <==
2015-12-29_15:17:01.52470 master failed to start, check stderr log for details
2015-12-29_15:17:02.53403 failed to start a new unicorn master
2015-12-29_15:17:02.55003 starting new unicorn master

==> /var/log/gitlab/unicorn/unicorn_stderr.log <==
I, [2015-12-29T16:17:03.876169 #20426]  INFO -- : Refreshing Gem list

I know that this is not enough but I don't know how to tell unicorn to tell me whats wrong with it :)

Any recommendations, how to debug this further?

Blaskovic
  • 61
  • 1
  • 5

0 Answers0