GitLab

Created by: mhoskiso

I've been setting up a fresh install of Gitlab 5.4 on Ubuntu 13.04 server and can't use SSH to push, pull, or clone but the http links work perfectly. When I try to use ssh, I get the following message:

fatal: Could not read from remote repository.

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

I can ssh into the server just fine so there's no firewall issues here. I thought this might be related to issue 3424(https://github.com/gitlabhq/gitlabhq/issues/3424) and I needed to add repositories to the ssh path, but I tried adding /repositories & /home/git/repositories but still get the error message. I've included my gitlab-shell config file down below, as well as the diagnostic checks but I can't see anything wrong.

ssh [email protected]

Welcome to GitLab, Anonymous! Connection to source.etnainteractive.com closed

git@source:~/gitlab-shell$ ./bin/check

Check GitLab API access: OK Check directories and files: /home/git/repositories: OK /home/git/.ssh/authorized_keys: OK

bundle exec rake gitlab:env:info RAILS_ENV=production

System information System: Ubuntu 13.04 Current User: git Using RVM: no Ruby Version: 1.9.3p392 Gem Version: 1.8.23 Bundler Version:1.3.5 Rake Version: 10.0.4

GitLab information Version: 5.4.0 Revision: 94a814d3 Directory: /home/git/gitlab DB Adapter: mysql2 URL: http://source.etnainteractive.com HTTP Clone URL: http://source.etnainteractive.com/some-project.git SSH Clone URL: [email protected]:some-project.git Using LDAP: no Using Omniauth: no

GitLab Shell Version: 1.4.0 Repositories: /home/git/repositories/ Hooks: /home/git/gitlab-shell/hooks/ Git: /usr/bin/git

git@source:~/gitlab$ bundle exec rake gitlab:check RAILS_ENV=production

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.4.0 ? ... OK (1.4.0) 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 post-receive hook up-to-date? ... yes post-receive hooks in repos are links: ... Internal Projects / Gitlab ... ok Client Sites / Gittest ... ok Client Sites / DevDeployTest ... ok Development Server / devdeploy ... repository is empty Doom ... ok

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes

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 satellites? ... Internal Projects / Gitlab ... yes Client Sites / Gittest ... yes Client Sites / DevDeployTest ... yes Development Server / devdeploy ... can't create, repository is empty Doom ... yes Redis version >= 2.0.0? ... yes Your git bin path is "/usr/bin/git" Git version >= 1.7.10 ? ... yes (1.8.1)

Checking GitLab ... Finished

git@source:~/gitlab-shell$ cat config.yml

GitLab user. git by default user: git

Url to gitlab instance. Used for api calls. Should be ends with slash. source: "http://source.etnainteractive.com/"

http_settings: user: someone password: somepass self_signed_cert: false

Repositories path repos_path: "/home/git/repositories"

File used as authorized_keys for gitlab user auth_file: "/home/git/.ssh/authorized_keys"

Redis settings used for pushing commit notices to gitlab redis: bin: /usr/bin/redis-cli host: 127.0.0.1 port: 6379 socket: /tmp/redis.socket # Only define this if you want to use sockets namespace: resque:gitlab