git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jeff King <peff@peff.net>
Date
Sep 18, 2013, 18:14 UTC
Message-ID
<20130918181443.GA18821@sigill.intra.peff.net>
In-Reply-To
<201309181444.19070.marex@denx.de>
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
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “[BUG] git clone -q ends with early EOF”
  1. Marek VasutSep 18, 2013
  2. Junio C HamanoSep 18, 2013
  3. Jeff KingSep 18, 2013
  4. Junio C HamanoSep 18, 2013
  5. Marek VasutSep 18, 2013
  6. Marek VasutSep 20, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.