Skip to content

GitLab

Closed
Created by Administrator@rootOwner

master failed to start

Created by: ReidWeb

I've followed the GitLab installation, and had no errors along the way, but when attempting to run

sudo service gitlab start

The following is returned

Starting the GitLab Unicorn web server...
master failed to start, check stderr log for details
Starting the GitLab Sidekiq event dispatcher...
The GitLab Unicorn webserver is not running.
The GitLab Sidekiq job dispatcher with pid 6516 is running.

The contents of the stderr log file are:

I, [2013-10-26T20:52:35.998816 #765]  INFO -- : Refreshing Gem list
I, [2013-10-26T20:52:58.543399 #765]  INFO -- : listening on addr=/home/git/gitlab/tmp/sockets/gitlab.socket fd=16
E, [2013-10-26T20:52:58.544667 #765] ERROR -- : adding listener failed addr=127.0.0.1:8080 (in use)
E, [2013-10-26T20:52:58.544937 #765] ERROR -- : retrying in 0.5 seconds (4 tries left)
E, [2013-10-26T20:52:59.045557 #765] ERROR -- : adding listener failed addr=127.0.0.1:8080 (in use)
E, [2013-10-26T20:52:59.045767 #765] ERROR -- : retrying in 0.5 seconds (3 tries left)
E, [2013-10-26T20:52:59.546346 #765] ERROR -- : adding listener failed addr=127.0.0.1:8080 (in use)
E, [2013-10-26T20:52:59.546557 #765] ERROR -- : retrying in 0.5 seconds (2 tries left)
E, [2013-10-26T20:53:00.047128 #765] ERROR -- : adding listener failed addr=127.0.0.1:8080 (in use)
E, [2013-10-26T20:53:00.047333 #765] ERROR -- : retrying in 0.5 seconds (1 tries left)
E, [2013-10-26T20:53:00.547915 #765] ERROR -- : adding listener failed addr=127.0.0.1:8080 (in use)
E, [2013-10-26T20:53:00.548121 #765] ERROR -- : retrying in 0.5 seconds (0 tries left)
E, [2013-10-26T20:53:01.048675 #765] ERROR -- : adding listener failed addr=127.0.0.1:8080 (in use)
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/socket_helper.rb:147:in `initialize': Address already in use - bind(2) (Errno::EADDRINUSE)
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/socket_helper.rb:147:in `new'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/socket_helper.rb:147:in `bind_listen'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:229:in `listen'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:773:in `block in bind_new_listeners!'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:773:in `each'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:773:in `bind_new_listeners!'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:141:in `start'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/bin/unicorn_rails:209:in `<top (required)>'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/bin/unicorn_rails:23:in `load'
    from /home/git/gitlab/vendor/bundle/ruby/2.0.0/bin/unicorn_rails:23:in `<main>'

Any thoughts on what is causing this issue?