WebFaction
Community site: login faq

I know that this question is identical to another one in here, but my symptoms are different.

I followed the webfaction git tutorial, and have run this on my git instance:

$ git config http.postBuffer 524288000

Just to be clear, here's what's in the config of my repo:

$ cat config 
[core]
    repositoryformatversion = 0
    filemode = true
    bare = true
[http]
    receivepack = true
    postBuffer = 524288000

Regardless, this still happens:

$ git push
Counting objects: 74, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (62/62), done.
error: RPC failed; result=22, HTTP code = 411
fatal: The remote end hung up unexpectedly
Writing objects: 100% (73/73), 3.67 MiB | 962 KiB/s, done.
Total 73 (delta 3), reused 0 (delta 0)
fatal: The remote end hung up unexpectedly

The wacky thing is that I'm not even pushing up that much data: only about 120MB. Now I'm still quite new to git, so I thought I might post my local .git/config file too:

$ cat .git/config 
[core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
[remote "origin"]
    fetch = +refs/heads/*:refs/remotes/origin/*
    url = http://USERNAME:PASSWORD@MY.DOMAIN.TLD/REPONAME.git
[branch "master"]
    remote = origin
    merge = refs/heads/master

Honestly, I'm completely out of ideas. If someone can see what I've done wrong, I'd really appreciate it. Note that I know I can do this over SSH, but that's not ideal for my scenario.

asked 10 Feb '12, 18:06

danielquinn
1211310
accept rate: 14%


So after some blind tweaking (and some sleep) I realised that the problem was actually where I ran the postBuffer command. I ran it on the repo end, and not on the client side. Once I ran it client-side everything worked just fine.

Sorry to confuse everyone.

permanent link

answered 14 Feb '12, 03:57

danielquinn
1211310
accept rate: 14%

The HTTP error itself is odd, it is a 411 which would likely be from a client bug, what version of git is your client using? Many distributions come with an outdated version in their repo. Try matching versions with what is on the server.

permanent link

answered 10 Feb '12, 20:05

johns
5.4k312
accept rate: 23%

Danielquinn you are my hero! I has this issue for a couple of weeks now, I tried several setups and nginx configurations and stuff without a useful solution. I've never thought about the client-side ^^

Thanks a million!

permanent link

answered 06 Nov '14, 14:44

Mahdi Fleckner
82
accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×111
×28

question asked: 10 Feb '12, 18:06

question was seen: 13,413 times

last updated: 06 Nov '14, 14:44

WEBFACTION
REACH US
SUPPORT
AFFILIATE PROGRAM
LEGAL
© COPYRIGHT 2003-2019 SWARMA LIMITED - WEBFACTION IS A SERVICE OF SWARMA LIMITED
REGISTERED IN ENGLAND AND WALES 5729350 - VAT REGISTRATION NUMBER 877397162
5TH FLOOR, THE OLD VINYL FACTORY, HAYES, UB3 1HA, UNITED KINGDOM