The remote end hung up unexpectedly while Git pushed large files

Question

When I try to switch to my replica bitpack, I get the following error. (This is actually the same on GitHub).

Counting objects: 48, done.
Delta compression using up to 2 threads.
Compression of objects: 100% (38/38), done.
Object spelling: 100% (48/48), 1.95 MiB | 38 KiB / s done.
Total 48 (delta 9), reused 0 (delta 0)
fatal: the far end unexpectedly hung up

error: RPC failed; result = 56, HTTP code = 0
fatal: recursion detected in gradient handler
All updated

Basically I get another error like

error: RPC error; result = 56, HTTP code = 0
fatal: the far end unexpectedly hung up

In any case, PUSH fails. I think this is only for large files. For small changes, it works great. I upgraded http.postBuffer to 2M and it still does not work.

Attention! I have a 3G connection and a CDMA-based EVDO internet connection. With a 3G connection, PUSH and everything else works FINE . But with EVDO I get the above errors. Therefore, I got the impression that due to a problem connecting to my EVDO or ISP.

How can i solve this?

Answer 1

Turns out it's a BSNL EVDO connection issue. Unfortunately, none of the technicians at BSNL could help me. So I refused the connection.

Back to the good old wired broadband: D.

Answer 2

usually deleted remote endings from unauthorized users. but if you can successfully link this, this is not a problem.

If you really think this is a file size issue, this is my best suggestion:

The default size at which the git client launches a "chunking" request is 1 MB. you can change this parameter using:

git config http.postBuffer 524288000

this example sets postBuffer to 500 MB. play around with this value and see if it helps.

Answer 3

I ran into the same problem, and because my push included some large files. Obviously, github has a limit of 100 MB for a single file size. I deleted the large files from my commit and tried git again and it worked. Here's more information about size restrictions:

https://help.github.com/articles/what-is-my-disk-quota

Answer 4

I ran into this problem with a bitbucket, an increase in postBuffer was most likely necessary, but did not solve the problem.

I was only able to resolve this using another internet connection.

These are the returned errors GIT_CURL_VERBOSE=1 :

 * SSLRead() return error -9820 * Connection died, retrying a fresh connect * Closing connection 0 

and then

 * SSLWrite() returned error -36 * Closing connection 1 error: RPC failed; result=55, HTTP code = 0 fatal: The remote end hung up unexpectedly 

Hope this helps someone, maybe someone with a great understanding understands these SSL errors?

Update:

The question I had was including inital git push in the repo, and since then I have tried the same click on the same reb-bitback with the original internet connection and it works.

Answer 5

If the reason is a huge file and http.postBuffer just doesn't work for you, try switching from http to ssh (i.e. ssh:// git@ <your git repository> ). This is likely to help you overcome the obstacle.