threads / bug / 34957

[BUG] git clone -q ends with early EOF

Subject: [BUG] git clone -q ends with early EOF

## tl;dr

6 messages between Sep 18, 2013 and Sep 20, 2013.

replies: 5people: 3as markdown or json

Marek Vasut· Sep 18, 2013, 12:44 UTC · lore
Hello,
I am trying to clone a repository and I am getting the following output:

$ git clone -q git://kernel.ubuntu.com/ubuntu/linux.git fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed

The "fatal:" lines usually appear a few minutes after running the clone. Of course, the clone does not finish successfully. Interestingly, when I drop the '-q' option from the git clone commandline, the clone finishes correctly.

My git version is:

$ git --version git version 1.8.4.rc3

Is this a known issue?
Thank you!

Best regards, Marek Vasut

Junio C Hamano· Sep 18, 2013, 16:03 UTC · re: Marek Vasut · lore

Re: [BUG] git clone -q ends with early EOF

This sounds suspiciously like 05e95155 (upload-pack: send keepalive packets during pack computation, 2013-09-08) that is cooking in 'next'.

If you are talking with other people's server side, you are SOL until the server end gets the patch.

Jeff King· Sep 18, 2013, 18:14 UTC · re: Marek Vasut · lore

Re: [BUG] git clone -q ends with early EOF

On Wed, Sep 18, 2013 at 02:44:18PM +0200, Marek Vasut wrote:
Show 10 quoted lines
> I am trying to clone a repository and I am getting the following output:
> 
> $ git clone -q git://kernel.ubuntu.com/ubuntu/linux.git
> fatal: The remote end hung up unexpectedly
> fatal: early EOF
> fatal: index-pack failed
> 
> The "fatal:" lines usually appear a few minutes after running the clone. Of 
> course, the clone does not finish successfully. Interestingly, when I drop the 
> '-q' option from the git clone commandline, the clone finishes correctly.

As Junio mentioned, this does seem like the issue that 05e9515 (upload-pack: send keepalive packets during pack computation, 2013-09-08) tries to fix. The server is quiet for a long period while preparing the pack, and something in the network stack thinks the connection has timed out and kills it.

One way you can check this is by running:
  time git clone -q git://kernel.ubuntu.com/ubuntu/linux.git

If it's a network timeout, it will die consistently at some nice round number. In this case, I just ran that command twice, and it died both times at just a hair over 2 minutes. So that is probably what is going on. There's no proxy on my end, so presumably there is some front-end reverse proxying happening on the server end, and it has a 2-minute timeout.

The keepalive patch is not in any released version yet, but we have been running it in production at GitHub for a few weeks. You may want to file a support request with the Ubuntu folks asking to pick up the patch, or to increase the timeouts on their proxies.

-Peff
Junio C Hamano· Sep 18, 2013, 19:50 UTC · re: Jeff King · lore

Re: [BUG] git clone -q ends with early EOF

Jeff King <peff@peff.net> writes:
> The keepalive patch is not in any released version yet, but we have been
> running it in production at GitHub for a few weeks.

That is good to hear; I'd feel safer to bump the scheduled graduation date to 'master' for the topic in that case.

Like tomorrow ;-)
Marek Vasut· Sep 18, 2013, 20:55 UTC · re: Junio C Hamano · lore

Re: [BUG] git clone -q ends with early EOF

Hi,
Show 8 quoted lines
> Jeff King <peff@peff.net> writes:
> > The keepalive patch is not in any released version yet, but we have been
> > running it in production at GitHub for a few weeks.
> 
> That is good to hear; I'd feel safer to bump the scheduled
> graduation date to 'master' for the topic in that case.
> 
> Like tomorrow ;-)

Thanks for explaining guys, I will try to poke the canonical guys with reference to this thread.

Best regards, Marek Vasut

Marek Vasut· Sep 20, 2013, 13:58 UTC · re: Junio C Hamano · lore

Re: [BUG] git clone -q ends with early EOF

Hi,
Show 8 quoted lines
> Jeff King <peff@peff.net> writes:
> > The keepalive patch is not in any released version yet, but we have been
> > running it in production at GitHub for a few weeks.
> 
> That is good to hear; I'd feel safer to bump the scheduled
> graduation date to 'master' for the topic in that case.
> 
> Like tomorrow ;-)

I reported the issue on Ubuntu Lunchpad here [1], so I hope they will eventually fix it.

[1] https://bugs.launchpad.net/ubuntu/+source/git/+bug/1228148

Best regards, Marek Vasut

← back to recent threads