Remote End Hung Up Error

Stephen Scott· May 11, 2015, 18:14 UTC · lore

Greetings;

I am getting this error when trying to retrieve a repo from git. Has anyone seen this issue before, and if you have how did you resolve it.

Cloning into 'xxxxxxxxx'... remote: Counting objects: 187683, done remote: Finding sources: 100% (187683/187683) remote: Getting sizes: 100% (98684/98684) remote: Compressing objects: 89% (8667/9643) efrror: RPC failed; result=56, HTTP code = 200 MiB | 42.00 KiB/s fatal: The remote end hung up unexpectedly atal: early EOF fatal: index-pack failed

Cloning into 'xxxxxxxxx'... remote: Counting objects: 187683, done remote: Finding sources: 100% (187683/187683) efrror: RPC failed; result=56, HTTP code = 200 atal: The remote end hung up unexpectedly fatal: protocol error: bad pack header

Thank you in advance; Stephen Scott This e-mail message is confidential, may be privileged and is intended for the exclusive use of the addressee. Any other person is strictly prohibited from disclosing, distributing or reproducing it. If the addressee cannot be reached or is unknown to you, please inform us immediately and delete this e-mail message and destroy all copies. Thank you.

brian m. carlson· May 12, 2015, 23:24 UTC · re: Stephen Scott · lore

Re: Remote End Hung Up Error

On Mon, May 11, 2015 at 06:14:53PM +0000, Stephen Scott wrote:

Show 21 quoted lines

> Greetings;
> 
> I am getting this error when trying to retrieve a repo from git. Has
> anyone seen this issue before, and if you have how did you resolve it.
> 
> Cloning into 'xxxxxxxxx'...
> remote: Counting objects: 187683, done
> remote: Finding sources: 100% (187683/187683)
> remote: Getting sizes: 100% (98684/98684)
> remote: Compressing objects: 89% (8667/9643)
> efrror: RPC failed; result=56, HTTP code = 200 MiB | 42.00 KiB/s
> fatal: The remote end hung up unexpectedly
> atal: early EOF
> fatal: index-pack failed
> 
> Cloning into 'xxxxxxxxx'...
> remote: Counting objects: 187683, done
> remote: Finding sources: 100% (187683/187683)
> efrror: RPC failed; result=56, HTTP code = 200
> atal: The remote end hung up unexpectedly
> fatal: protocol error: bad pack header

CURL error code 56 is CURLE_RECV_ERROR, so the problem is a network connection. Commonly these types of errors occur over HTTP because of a broken proxy. Are you using such a proxy? If so, can you try over HTTPS (without MITM), the Git protocol, or SSH?

Also, what version of Git are you using, what version of libcurl is it linked against, and what type of HTTP authentication are you using, if any? I seem to remember that older versions of Git were broken with Kerberos in some cases, but that was quite some time ago.

Show 6 quoted lines

> This e-mail message is confidential, may be privileged and is intended
> for the exclusive use of the addressee. Any other person is strictly
> prohibited from disclosing, distributing or reproducing it. If the
> addressee cannot be reached or is unknown to you, please inform us
> immediately and delete this e-mail message and destroy all copies.
> Thank you.

Please don't send this material to the list. See http://www.goldmark.org/jeff/stupid-disclaimers/ for why it's a bad idea.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187