After updating Ubuntu, Gitlab is not running and unicorn_stderr.log shows the following error:
F, [2018-10-12T21:47:15.632756 #3235] FATAL -- : error adding listener addr=127.0.0.1:8080
/opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/socket_helper.rb:185:in `bind': Cannot assign requested address - bind(2) for 127.0.0.1:8080 (Errno::EADDRNOTAVAIL)
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/socket_helper.rb:185:in `new_tcp_server'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/socket_helper.rb:165:in `bind_listen'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:242:in `listen'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:813:in `block in bind_new_listeners!'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:813:in `each'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:813:in `bind_new_listeners!'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:138:in `start'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.9.0/bin/unicorn:126:in `<top (required)>'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/bin/unicorn:23:in `load'
from /opt/gitlab/embedded/service/gem/ruby/2.1.0/bin/unicorn:23:in `<main>'
Hi, and welcome to the GitLab forum! 
Quickly looking at your output, this seems to be the error:
Cannot assign requested address - bind(2) for 127.0.0.1:8080 (Errno::EADDRNOTAVAIL)
Perhaps something else is using the 8080 port on your local machine? You can try to see if that’s the case with this command:
sudo lsof -i :8080
In any case, so that others can be able to help you, we’d need some more information:
Which version of Ubuntu did you upgrade to?
You can check this with the output of this command:
lsb_release -a
Which version of GitLab do you have installed?
You can check out the version of the GitLab package with the output of this command:
apt-cache policy gitlab-{e,c}e | grep Installed
What’s the status of the GitLab Runit supervision process?
You can check out the status with this command:
sudo service gitlab-runsvdir status
1 Like
This was an old Ubuntu 14.04 box. I did an apt-get upgrade and it installed the latest hotfixes for the current version. It tried to do the omnibus install but the pre-install checks failed and said I need to manually update to a in-between version before I can update to the latest version.
Hm, GitLab 8.10 is a rather old version I’m not familiar with. However, it would seem that port 8080 is taken by the gitlab-shell process.
Are you sure you don’t have a gitlab instance running while you are trying to start another one?
How do you usually start/stop GitLab on version 8.10?
Whatever your findings are, I’d recommend updating to a more recent version (11.3 is the latest), as you’ll get a better level of support and documentation.
I think what you’ll have to do is to:
- Check out the Mandatory upgrade paths for version upgrade
- First manually download the next packaged version you can upgrade to. As described here: https://docs.gitlab.com/omnibus/update/#updating-using-a-manually-downloaded-package
- Manually install the package with
dpkg -i <downloaded package>
- Repeat the two steps above until you get to at least 10.8.
- After 10.8, upgrades should work from the repository via
apt, if I understand the documentation correctly.
