Upgrade from 4.2, SSH fatal: The remote end hung up unexpectedly
Created by: Leegorous
I just followed the Update guides to update Gitlab from 4.2 to 5.0.
Everything is good, all green, but when i do git pull or clone on the former project, it ends with
> git clone [email protected]:leegorous/one-project.git
Cloning into 'one-project'...
fatal: The remote end hung up unexpectedlyAnd than, i test SSH
> ssh -T [email protected]
Welcome to GitLab, Anonymous!That's weird.
I can't git over SSH, but the HTTP runs well
> git clone http://mygitlab.com/leegorous/one-project.git
...
Receiving objects: 100% (10616/10616), 12.81 MiB | 552 KiB/s, done.
Resolving deltas: 100% (7783/7783), done.I can't see any related error log under /home/git/gitlab/log/
Do anyone have some idea?
The env:info
> sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
System information
System: Ubuntu 12.10
Current User: git
Using RVM: no
Ruby Version: 1.9.3p327
Gem Version: 1.8.23
Bundler Version:1.3.1
Rake Version: 10.0.3
GitLab information
Version: 5.0.1
Revision: 951273f
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: http://mygitlab.com
HTTP Clone URL: http://mygitlab.com/some-project.git
SSH Clone URL: [email protected]:some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 1.2.0
Repositories: /home/git/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/bin/git