GitLab

Created by: ghislainf

After follow the update guide i have an error when i start the gitlab service.

$ sudo service gitlab start

Response :

Puma 2.0.0.b7 starting...
* Min threads: 0, max threads: 16
* Environment: production
* Listening on unix:///home/git/gitlab/tmp/sockets/gitlab.socket
/home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/lib/puma/binder.rb:234:in `initialize': No such file or directory - /home/git/gitlab/tmp/sockets/gitlab.socket (Errno::ENOENT)
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/lib/puma/binder.rb:234:in `new'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/lib/puma/binder.rb:234:in `add_unix_listener'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/lib/puma/binder.rb:96:in `block in parse'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/lib/puma/binder.rb:64:in `each'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/lib/puma/binder.rb:64:in `parse'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/lib/puma/cli.rb:414:in `run_single'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/lib/puma/cli.rb:402:in `run'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/puma-2.0.0.b7/bin/puma:10:in `<top (required)>'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/bin/puma:23:in `load'
    from /home/git/gitlab/vendor/bundle/ruby/1.9.1/bin/puma:23:in `<main>'
Gitlab service started

Created by: Razer6

Solution in #3663

By Administrator on 2013-04-22T19:48:02 (imported from GitLab project)

Created by: ghislainf

Thanks ! It's work now

By Administrator on 2013-04-22T19:57:09 (imported from GitLab project)

Created by: dhampik

That is not a fix acually. That is a hack. I get this error everytime I do sudo /etc/init.d gitlab stop and then trying to start gitlab again I had to sudo rm -f /home/git/gitlab/tmp/sockets/gitlab.socket everytime!

By Administrator on 2013-05-12T09:35:11 (imported from GitLab project)