git push fails, postBuffer set

Question

I'm attempting to push a large set of changes via http, something around 60mb to a git repository. I've configured the post buffer as instructed in the docs but its still fails. I get this error:

fatal: The remote end hung up unexpectedly fatal: expected ok/error, helper said '4004???A???+q??&D??5??,M?c }g???<?&??56uQv??T??Pp?S???z??????????{y?L??{??,?<?_??`?U R??e?8?'????M|^Q??:K?????X???pm??oWcV???-?x??U8??:?rn?E????JL???X'

in addition to the 411 errors that are documented. I've got three other git repos set up that I've been working with just fine, although I've not attempted to push that much in the way of changes before

Any insights would be welcome. Thanks

Accepted Answer

In theory the postbuffer setting should allow very large commits to be pushed without a problem, but it seems that the front-end server stack is getting in the way of this large changeset, and causing the commit to fail (it needs to be a single data stream; any interruption in that could cause a remote server hung up unexpectedly error).

In this case, I would suggest simply pushing this one changeset over SSH instead of HTTP. You don't need to do a git remote add and add a permanent remote, but should be able to just do something like this:

git push username@username.webfactional.com:webapps/git/repos/therepo.git

This will push the changeset over SSH, which is the most stable protocol available. You should still be able to push future changes over the normal HTTP, and also others should be able to download the changes over HTTP without a problem. In other words, you should be able to fall back on a single SSH push whenever you need it.

git push fails, postBuffer set

Follow this question

Related questions