4 ms·
If you are using the Omnibus package on Ubuntu, don't upgrade! It just broke my instance. and can't find out what's wrong. Great features... It was a big mistak
by Walkman 8y ago
If you are using the Omnibus package on Ubuntu, don't upgrade! It just broke my instance. and can't find out what's wrong. Great features... It was a big mistake to trust GitLab, I already predicted they will have problems.
- some_account 8y agoI'm pretty sure this doesn't happen on all Ubuntu installs. Maybe you have some custom stuff?
- Walkman 8y agoI don't think so. The problem was that unicorn was not listening on IPv4 by default, but it was before 11.0. Weird.
- jobvandervoort 8y agoWhat is the output you get? Consider creating an issue here so we can help you debug: https://gitlab.com/gitlab-org/omnibus-gitlab/issues https://gitlab.com/gitlab-org/omnibus-gitlab/issues
- Walkman 8y agoHere we go: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/3615 https://gitlab.com/gitlab-org/omnibus-gitlab/issues/3615
- zingmars 8y agoTry rebooting the server. No, I'm not joking. I've had the omnibus package break my Gitlab as well and the bugs survived even full reconfigures and restarts. Rebooting the server fixed it even though it makes no sense.
- Walkman 8y agoThanks for the tip, but this was one of the first things I tried beside gitlab-ctl reconfigure && gitlab-ctl restart