2014-10-03 273 views
3

当我收到以下错误,当我尝试使用SSH克隆库:SSH错误克隆Git仓库

$ git clone ssh://[email protected]:7999/eqt/myproject.git 
Cloning into 'myproject'... 
Read from socket failed: Connection reset by peer 
fatal: Could not read from remote repository. 

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

SSH密钥存储在共享驱动器,我也执行相同的没有问题从另一台也使用共享驱动器的机器克隆。我的问题是我的Windows 7笔记本电脑。

我试着调试ssh连接并运行以下命令:

$ ssh -Tvvv [email protected] -p 7999 
OpenSSH_6.6.1, OpenSSL 1.0.1i 6 Aug 2014 
debug2: ssh_connect: needpriv 0 
debug1: Connecting to stash.mydomain.com [10.105.255.156] port 7999. 
debug1: Connection established. 
debug3: Incorrect RSA1 identifier 
debug3: Could not load "/p/.ssh/id_rsa" as a RSA1 public key 
debug1: identity file /p/.ssh/id_rsa type 1 
debug1: identity file /p/.ssh/id_rsa-cert type -1 
debug1: identity file /p/.ssh/id_dsa type -1 
debug1: identity file /p/.ssh/id_dsa-cert type -1 
debug1: identity file /p/.ssh/id_ecdsa type -1 
debug1: identity file /p/.ssh/id_ecdsa-cert type -1 
debug1: identity file /p/.ssh/id_ed25519 type -1 
debug1: identity file /p/.ssh/id_ed25519-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_6.6.1 
debug1: Remote protocol version 2.0, remote software version SSHD-CORE-0.9.0-ATLASSIAN-1 
debug1: no match: SSHD-CORE-0.9.0-ATLASSIAN-1 
debug2: fd 3 setting O_NONBLOCK 
debug3: put_host_port: [stash.mydomain.com]:7999 
debug3: load_hostkeys: loading entries for host "[stash.mydomain.com]:7999" from file "/p/.ssh/known_hosts" 
debug3: load_hostkeys: found key type RSA in file /p/.ssh/known_hosts:2 
debug3: load_hostkeys: loaded 1 keys 
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],ssh-rsa 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug2: kex_parse_kexinit: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman- 
debug2: kex_parse_kexinit: [email protected],[email protected],ssh-rsa,[email protected],[email protected],ecdsa-sha2-nistp521-cert- 
stp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-dss 
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm[email protected],[email protected],[email protected],aes128-cbc,3des-cbc,blowfish-cbc,cast128-c 
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[email protected],[email protected],[email protected],aes128-cbc,3des-cbc,blowfish-cbc,cast128-c 
debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-ripemd16 
[email protected],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-ripemd16 
[email protected],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: none,[email protected],zlib 
debug2: kex_parse_kexinit: none,[email protected],zlib 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 
debug2: kex_parse_kexinit: ssh-rsa 
debug2: kex_parse_kexinit: aes128-ctr,aes128-cbc,3des-cbc,blowfish-cbc 
debug2: kex_parse_kexinit: aes128-ctr,aes128-cbc,3des-cbc,blowfish-cbc 
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-md5-96,hmac-sha1-96 
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-md5-96,hmac-sha1-96 
debug2: kex_parse_kexinit: none 
debug2: kex_parse_kexinit: none 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: mac_setup: setup hmac-md5 
debug1: kex: server->client aes128-ctr hmac-md5 none 
debug2: mac_setup: setup hmac-md5 
debug1: kex: client->server aes128-ctr hmac-md5 none 
debug2: bits set: 1008/2048 
debug1: sending SSH2_MSG_KEXDH_INIT 
debug1: expecting SSH2_MSG_KEXDH_REPLY 
Read from socket failed: Connection reset by peer 

可能是什么问题吗?我的SSH密钥似乎很好,但似乎这个连接被阻止在某个地方。我对SSH不太了解,不知道去哪里寻找。

+0

远程服务器在设置安全通道的同时断开连接。您需要排除服务器故障。 – Kenster 2014-10-03 19:45:16

+0

虽然服务器不能成为问题。正如我上面所说,完全相同的请求正在另一台机器上工作 – DJ180 2014-10-03 20:30:21

+2

“通过对等方重置连接”字面意思是连接的另一端关闭它。事实上,这意味着远端有一个“流产关闭”,而不是正常关闭。程序崩溃可能导致这种情况。 – Kenster 2014-10-03 20:42:39

回答

4

的服务器不能是虽然

我仍然会检查server sshd logs以确保(/var/log/auth.log)(increasing the LogLevel在sshd的配置也可以帮助你)的问题

你可以试试并通过MobaXterm(仅用于测试)测试ssh,因为它有Workaround for "connection reset by peer" issue

您可以检查它是否是Cipher issue (on the client side)

最后,you can try and regenerate a new pair of public/private keys,在服务器上发布公共服务器,并检查问题是否仍然存在。

+0

由于我们可以从URL中扣除@ DJ180正在使用存储,没有涉及ssh过程,只是java库。特别是[Apache SSH](http://mina.apache.org/sshd-project/) – 2014-10-10 18:04:41