git clone Stalling when Checking Out New Projects
I have recently migrated some projects from a locally hosted SVN server to BitBucket.
The push seemed to happen successfully.
When checking them out on other people's dev machines, they consistently stall at 65% and 10% respectively.
For example (usernames and repository names changes)
xyz@localhost projects]$ git clone email@example.com:deliverycube/repo.git repo Initialized empty Git repository in /home/xyz/development/projects/repo/.git/ remote: Counting objects: 11758, done. remote: Compressing objects: 100% (3177/3177), done. Receiving objects: 10% (1240/11758), 5.06 MiB | 38 KiB/s Write failed: Broken pipe1240/11758), 5.40 MiB | 1 KiB/s fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed
Another one fails consistently at 65%.
I don't think it is an ssh problem.
The repositories are not particularly big.
They stall at the same point on different machines.
I have run an ssh debug and get the following output (usernames changed).
XXX-Mac-mini:~ xxx$ ssh -Tv firstname.lastname@example.org OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 debug1: Reading configuration data /etc/ssh_config debug1: /etc/ssh_config line 20: Applying options for * debug1: Connecting to bitbucket.org [220.127.116.11] port 22. debug1: Connection established. debug1: identity file /Users/xxx/.ssh/id_rsa type 1 debug1: identity file /Users/xxx/.ssh/id_rsa-cert type -1 debug1: identity file /Users/xxx/.ssh/id_dsa type -1 debug1: identity file /Users/xxx/.ssh/id_dsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH_5* debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40 debug1: Host 'bitbucket.org' is known and matches the RSA host key. debug1: Found key in /Users/xxx/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/xxx/.ssh/id_rsa debug1: Remote: Forced command: conq username:xyz debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Server accepts key: pkalg ssh-rsa blen 279 debug1: Remote: Forced command: conq username:vmarathe debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Authentication succeeded (publickey). Authenticated to bitbucket.org ([18.104.22.168]:22). debug1: channel 0: new [client-session] debug1: Requesting email@example.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LC_CTYPE = UTF-8 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype firstname.lastname@example.org reply 0 logged in as xyz. You can use git or hg to connect to Bitbucket. Shell access is disabled. debug1: channel 0: free: client-session, nchannels 1 Transferred: sent 3072, received 2888 bytes, in 0.7 seconds Bytes per second: sent 4141.8, received 3893.7 debug1: Exit status 0