Skip to content

GitLab Next

Closed
Opened by Yonghee Han@yongpwi

http, ssh git not accessible

Summary

I use gitlab omnibus ce version 8.5.1 I have updated to version 9.5 => 10.4.0

However, gitlab using an Internet browser works fine, but it does not do http, ssh git clone login using console.

Steps to reproduce

git clone http://gitlab.sphinfo.co.kr/yong/test2.git

When you call the parent instruction

"Cloning into 'test2' ... remote: Internal server error fatal: unable to access 'http://gitlab.sphinfo.co.kr/yong/test2.git/': The requested URL returned error: 500 "

Show results.

The gitlab log that received the command(error line)

==> /var/log/gitlab/gitlab-workhorse/current <== 2018-01-24_16:50:13.63026 2018/01/25 01:50:13 error: GET "/yong/atlas.git/info/refs?service=git-upload-pack": handleGetInfoRefs: GetInfoRefsHandler: rpc error: code = Unavailable desc = grpc: the connection is unavailable

==> /var/log/gitlab/postgresql/current <== 2018-01-24_16:50:19.67560 ERROR: relation "project_mirror_data" does not exist at character 42 2018-01-24_16:50:19.67562 STATEMENT: SELECT COUNT(*) FROM projects INNER JOIN project_mirror_data ON project_mirror_data.project_id = projects.id WHERE projects.mirror = 't' AND projects.import_status NOT IN ('scheduled', 'started') AND next_execution_timestamp <= NOW();

Show results

git clone git@gitlab.sphinfo.co.kr:yong/test2.git Cloning into 'test2'... 2018/01/25 02:02:48 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/opt/gitlab/gitaly/gitaly.socket: connect: connection refused"; Reconnecting to {/var/opt/gitlab/gitaly/gitaly.socket } gitaly-upload-pack: fatal: upload-pack failed fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)

What is the current bug behavior?

The requested URL returned error

What is the expected correct behavior?

http clone

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)
System information
System:		Ubuntu 14.04
Current User:	git
Using RVM:	no
Ruby Version:	2.3.6p384
Gem Version:	2.6.13
Bundler Version:1.13.7
Rake Version:	12.3.0
Redis Version:	3.2.11
Git Version:	2.14.3
Sidekiq Version:5.0.5
Go Version:	unknown


GitLab information
Version:	10.4.0
Revision:	128ef10
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		http://gitlab.sphinfo.co.kr
HTTP Clone URL:	http://gitlab.sphinfo.co.kr/some-group/some-project.git
SSH Clone URL:	git@gitlab.sphinfo.co.kr:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no


GitLab Shell
Version:	5.11.0
Repository storage paths:
  • default: /repository/data/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
root@ip-172-31-19-167:/etc/nginx/sites-available# sudo gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...


GitLab Shell version >= 5.11.0 ? ... OK (5.11.0)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
3/2 ... ok
3/3 ... ok
3/4 ... ok
5/5 ... ok
3/6 ... ok
5/7 ... repository is empty
3/8 ... ok
3/9 ... repository is empty
5/11 ... ok
7/14 ... ok
3/15 ... ok
5/16 ... ok
3/17 ... ok
8/18 ... ok
8/19 ... ok
5/20 ... ok
5/21 ... repository is empty
5/23 ... ok
5/25 ... repository is empty
7/26 ... ok
3/29 ... ok
3/30 ... ok
3/31 ... ok
8/33 ... ok
3/34 ... ok
5/35 ... ok
5/37 ... ok
3/38 ... repository is empty
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Sidekiq ...


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


Checking Sidekiq ... Finished


Reply by email is disabled in config/gitlab.yml
Checking LDAP ...


LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... skipped (no tmp uploads folder yet)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
3/2 ... yes
3/3 ... yes
3/4 ... yes
5/5 ... yes
3/6 ... yes
5/7 ... yes
3/8 ... yes
3/9 ... yes
5/11 ... yes
7/14 ... yes
3/15 ... yes
5/16 ... yes
3/17 ... yes
8/18 ... yes
8/19 ... yes
5/20 ... yes
5/21 ... yes
5/23 ... yes
5/25 ... yes
7/26 ... yes
3/29 ... yes
3/30 ... yes
3/31 ... yes
8/33 ... yes
3/34 ... yes
5/35 ... yes
5/37 ... yes
3/38 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.7.3 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 13


Checking GitLab ... Finished


(we will only investigate if the tests are passing)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited by Yonghee Han