double checking GitLab installation : gitlab-shell self-check failed

Question

I installed GitLab and everything seems fine. Until I double check application status by running: sudo -u git -H editor /home/git/gitlab-shell/config.yml. This item is in red and seems to have an error:

  gitlab-shell self-check failed
  Try fixing it:
  Make sure GitLab is running;
  Check the gitlab-shell configuration file:
  sudo -u git -H editor /home/git/gitlab-shell/config.yml
  Please fix the error above and rerun the checks.

I try opening config.yml but I don't seem to find any unusual there. You think what am I missing?

Also, I have a custom SSH connection. What I don't understand from this explanation:

Custom SSH Connection

If you are running SSH on a non-standard port, you must change the gitlab user's SSH config.

# Add to /home/git/.ssh/config
host localhost          # Give your setup a name (here: override localhost)
    user git            # Your remote git user
    port 2222           # Your port number
    hostname 127.0.0.1; # Your server name or IP
You also need to change the corresponding options (e.g. ssh_user, ssh_host, admin_uri) in the config\gitlab.yml file.

Out of lost, I don't have this /home/git/.ssh/config, should I create one or I am just missing something?

My call stack:

Checking Environment ...

Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.7.4 ? ... OK (1.7.6)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ... can't check, you have no projects
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: /usr/local/lib/ruby/2.0.0/net/http.rb:878:in `initialize': getaddrinfo: Name or service not known (SocketError)
        from /usr/local/lib/ruby/2.0.0/net/http.rb:878:in `open'
        from /usr/local/lib/ruby/2.0.0/net/http.rb:878:in `block in connect'
        from /usr/local/lib/ruby/2.0.0/timeout.rb:52:in `timeout'
        from /usr/local/lib/ruby/2.0.0/net/http.rb:877:in `connect'
        from /usr/local/lib/ruby/2.0.0/net/http.rb:862:in `do_start'
        from /usr/local/lib/ruby/2.0.0/net/http.rb:851:in `start'
        from /home/git/gitlab-shell/lib/gitlab_net.rb:62:in `get'
        from /home/git/gitlab-shell/lib/gitlab_net.rb:29:in `check'
        from /home/git/gitlab-shell/bin/check:11:in `<main>'
gitlab-shell self-check failed
  Try fixing it:
  Make sure GitLab is running;
  Check the gitlab-shell configuration file:
  sudo -u git -H editor /home/git/gitlab-shell/config.yml
  Please fix the error above and rerun the checks.

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ... can't check, you have no projects
Projects have satellites? ... can't check, you have no projects
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/local/bin/git"
Git version >= 1.7.10 ? ... yes (1.8.4)

Checking GitLab ... Finished

Answer 1

It could be similar to the Issue 5437:

I ran into the exact same problem doing a clean install on my debian wheezy 7.2 server.

I made two changes and rebooted the server (no problem since it is only a testserver):

• make sure that your domain points to 127.0.0.1 in /etc/hosts (on my server it pointed to 127.0.1.1)
• add /home/git/.ssh/config for the non-standard ssh port as mentioned in the installation procedure

In that case, setting the domain to 127.0.0.1 in the /etc/hosts was enough.

Other issue possible: issue 5426: wrong sidekick command

This way to start sidekiq does not work anymore. You have to use:

sudo -u git -H RAILS_ENV=production script/background_jobs start

---

An http.rb:xxx:ininitialize': getaddrinfo: Name or service not known (SocketError)` error message is seen in:

• Issue 5151 => solved by this comment:

  sudo -u git -H vim /home/git/gitlab-shell/config.yml
  # and change:
  gitlab_url: http://yourhost to gitlab_url: http://yourhost/
  # Slash at the end is important.
  

• Issue 42 of gitlab-shell: again, the /etc/hosts is important to get right.

---

The OP Leandro Garcia confirms in the comments:

I forgot to setup the domain I provided on gitlab_url.
Adding that and correcting the DNS on my domain provider solves the issue