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

Re: fatal: unexpected EOF

From
BGBrian Gerst <bgerst@didntduck.org>
Date
Feb 28, 2006, 15:43 UTC
Message-ID
<44046F94.3070806@didntduck.org>
In-Reply-To
<Pine.LNX.4.64.0602280731210.22647@g5.osdl.org>
Linus Torvalds wrote:
Show 28 quoted lines
> 
> On Tue, 28 Feb 2006, Brian Gerst wrote:
> 
>>Lately I've been receiving this error frequently from git.kernel.org:
>>
>>Fetching pack (head and objects)...
>>fatal: unexpected EOF
>>cg-fetch: fetching pack failed
>>
>>What is causing this?
> 
> 
> Almost any error will cause the pack sending to abort, and the git:// 
> protocol only opens a single socket for data, so there is no way for the 
> other end to say _what_ failed.
> 
> With git.kernel.org, I suspect the reason for the failure is almost always 
> the same, though: the mirroring is not complete, so it doesn't have all 
> object files. The mirroring from master.kernel.org to the actual public 
> machines is just a rsync script, so there's no atomicity guarantees.
> 
> That said, it might be a load issue too - I don't know what limits 
> Peter & co put on the git daemons, and it might also be that it's set up 
> to accept at most <n> connections and will close anything else.
> 
> 		Linus
> 
> 

I doubt it is a problem with mirroring, since it affects all repos (kernel, git, cogito, etc.) at the same time.

--
				Brian Gerst
Previous: Linus TorvaldsNext: Tony Luck
Message 3 of 5 in “fatal: unexpected EOF”
  1. Brian GerstFeb 28, 2006
  2. Linus TorvaldsFeb 28, 2006
  3. Brian GerstFeb 28, 2006
  4. Tony LuckFeb 28, 2006
  5. Alex RiesenMar 2, 2006

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.