TechnicalSquid
asked on
Gitlab not starting
I updated the patches on a Ubuntu box running gitlab-ce. Now it's refusing to start with the following error in unicorn_stderr.log
F, [2018-10-12T21:47:15.63275 6 #3235] FATAL -- : error adding listener addr=127.0.0.1:8080
/opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/lib /unicorn/s ocket_help er.rb:185: in `bind': Cannot assign requested address - bind(2) for 127.0.0.1:8080 (Errno::EADDRNOTAVAIL)
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/lib /unicorn/s ocket_help er.rb:185: in `new_tcp_server'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/lib /unicorn/s ocket_help er.rb:165: in `bind_listen'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/lib /unicorn/h ttp_server .rb:242:in `listen'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/lib /unicorn/h ttp_server .rb:813:in `block in bind_new_listeners!'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/lib /unicorn/h ttp_server .rb:813:in `each'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/lib /unicorn/h ttp_server .rb:813:in `bind_new_listeners!'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/lib /unicorn/h ttp_server .rb:138:in `start'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/ge ms/unicorn -4.9.0/bin /unicorn:1 26:in `<top (required)>'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/bi n/unicorn: 23:in `load'
from /opt/gitlab/embedded/servi ce/gem/rub y/2.1.0/bi n/unicorn: 23:in `<main>'
F, [2018-10-12T21:47:15.63275
/opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
from /opt/gitlab/embedded/servi
The error message suggests nothing is listening on 127.0.0.1:8080 so you'll have to arrange for something to listen on localhost:8080 before your code can connect.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.