GitLab

Created by: MagicMicky

EDIT: solved by increasing timeout in config/unicorn.rb and restarting gitlab. You can delete/close the issue if you want.

Hi. I'm using a gitlab recipe to install gitlab on my dedicated server (Intel Atom CPU N2800 and 2GB of RAM) After installing, everything seemed to be alright. But, when I open my browser to my host, it doesn't work and I have a 502 Bad Gateway

Here are my logs: /home/gitlab/gitlab/log/unicorn.stderr.log

I, [2013-10-09T19:18:03.174288 #4015]  INFO -- : Refreshing Gem list
I, [2013-10-09T19:18:54.109896 #4015]  INFO -- : unlinking existing socket=/home/gitlab/gitlab//tmp/sockets/gitlab.socket
I, [2013-10-09T19:18:54.110397 #4015]  INFO -- : listening on addr=/home/gitlab/gitlab//tmp/sockets/gitlab.socket fd=12
I, [2013-10-09T19:18:54.117804 #4015]  INFO -- : master process ready
I, [2013-10-09T19:18:54.367829 #4178]  INFO -- : worker=0 ready
I, [2013-10-09T19:18:54.367844 #4181]  INFO -- : worker=1 ready
E, [2013-10-09T19:19:54.173837 #4015] ERROR -- : worker=0 PID:4178 timeout (31s > 30s), killing
E, [2013-10-09T19:19:54.198484 #4015] ERROR -- : reaped #<Process::Status: pid 4178 SIGKILL (signal 9)> worker=0
I, [2013-10-09T19:19:54.406727 #4431]  INFO -- : worker=0 ready

/var/log/nginx/gitlab_error.log

2013/10/09 19:17:01 [error] 29378#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 82.236.21.184, server: git.HOSTNAME, request: "GET /users/sign_in HTTP/1.1", upstream: "http://unix:/home/gitlab/gitlab/tmp/sockets/gitlab.socket:/users/sign_in", host: "git.HOSTNAME
2013/10/09 19:19:54 [error] 3750#0: *2 upstream prematurely closed connection while reading response header from upstream, client: 82.236.21.184, server: git.HOSTNAME, request: "GET /users/sign_in HTTP/1.1", upstream: "http://unix:/home/gitlab/gitlab/tmp/sockets/gitlab.socket:/users/sign_in", host: "git.HOSTNAME"

What happend during the install? Could this be an issue with my server's config?