Error creating listening on port
Created by: frostyfrog
So I kinda followed a mix of https://github.com/gitlabhq/gitlabhq/blob/stable/doc/install/installation.md and https://wiki.archlinux.org/index.php/Gitlab but I've run into a snag. If I use the systemd init script suggested somewhere in this issue tracker, Gitlab opens on port 3000. But If I try the suggested init script from the arch wiki, It fails to listen on my customized port.
Sorry for vagueness, I'm kinda tired...
journalctl -xn
Dec 09 18:08:53 Atlanta su[15616]: (to gitlab) frosty on /dev/pts/7
Dec 09 18:08:53 Atlanta su[15616]: pam_unix(su:session): session opened for user gitlab by frosty(uid=0)
Dec 09 18:09:17 Atlanta su[15616]: pam_unix(su:session): session closed for user gitlab
Dec 09 18:09:25 Atlanta systemd[1]: Starting Gitlab Unicorn Rails server...
-- Subject: Unit gitlab.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
--
-- Unit gitlab.service has begun starting up.
Dec 09 18:10:03 Atlanta gl-unicorn[15642]: master failed to start, check stderr log for details
Dec 09 18:10:03 Atlanta systemd[1]: gitlab.service: control process exited, code=exited status=1
Dec 09 18:10:03 Atlanta systemd[1]: Failed to start Gitlab Unicorn Rails server.
-- Subject: Unit gitlab.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit gitlab.service has failed.
--
-- The result is failed.
Dec 09 18:10:03 Atlanta systemd[1]: Unit gitlab.service entered failed state
log/unicorn.stderr.log
I, [2012-12-09T17:34:45.302519 #14642] INFO -- : Refreshing Gem list
F, [2012-12-09T17:35:22.796620 #14642] FATAL -- : error adding listener addr=0.0.0.0:90
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/socket_helper.rb:147:in `initialize': Permission denied - bind(2) (Errno::EACCES)
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/socket_helper.rb:147:in `new'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/socket_helper.rb:147:in `bind_listen'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/http_server.rb:228:in `listen'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/http_server.rb:751:in `block in bind_new_listeners!'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/http_server.rb:751:in `each'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/http_server.rb:751:in `bind_new_listeners!'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/http_server.rb:140:in `start'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/bin/unicorn_rails:209:in `<top (required)>'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/bin/unicorn_rails:23:in `load'
from /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/bin/unicorn_rails:23:in `<main>'