Bug #518
Updated by Daniel Curtis almost 10 years ago
I encountered a problem while pushing new commits to my GitLab server. I was able to access the web front end, so the problem was specifically happening with the gitlab-shell. * When I ran the following: <pre> git push origin master </pre> #* I got the following error: <pre> /usr/local/lib/ruby/2.0/net/http.rb:878:in `initialize': getaddrinfo: hostname nor servname provided, or not known (SocketError) from /usr/local/lib/ruby/2.0/net/http.rb:878:in `open' from /usr/local/lib/ruby/2.0/net/http.rb:878:in `block in connect' from /usr/local/lib/ruby/2.0/timeout.rb:52:in `timeout' from /usr/local/lib/ruby/2.0/net/http.rb:877:in `connect' from /usr/local/lib/ruby/2.0/net/http.rb:862:in `do_start' from /usr/local/lib/ruby/2.0/net/http.rb:851:in `start' from /usr/home/git/gitlab-shell/lib/gitlab_net.rb:103:in `post' from /usr/home/git/gitlab-shell/lib/gitlab_net.rb:28:in `check_access' from /usr/home/git/gitlab-shell/lib/gitlab_shell.rb:63:in `validate_access' from /usr/home/git/gitlab-shell/lib/gitlab_shell.rb:24:in `exec' from /usr/home/git/gitlab-shell/bin/gitlab-shell:16:in `<main>' fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. </pre> * It turns out that I had recently migrated my name server and forgot to add a proper DNS record for the GitLab servers hostname. Once I added the DNS record I was able to push commits again. h2. Resources https://stackoverflow.com/questions/4132525/getaddrinfo-nodename-nor-servname-provided-or-not-known