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

Re: unexpected EOF?

From
Linus Torvalds <torvalds@osdl.org>
Date
Dec 1, 2005, 18:40 UTC
Message-ID
<Pine.LNX.4.64.0512011036120.3099@g5.osdl.org>
In-Reply-To
<E1EhohG-0001iZ-IB@jdl.com>
On Thu, 1 Dec 2005, Jon Loeliger wrote:
Show 12 quoted lines
> 
> I thought I had imagined this last time, but now 
> that it has happened twice, I'm not so sure what
> is going on.  First pull attempt garners an
> unexpected EOF message; immediately pull again
> seems to work.
> 
> jdl@ubuntu:/usr/src/git-core$ git pull origin
> fatal: unexpected EOF
> Fetch failure: git://git.kernel.org/pub/scm/git/git.git/
> jdl@ubuntu:/usr/src/git-core$ git pull origin
> Unpacking 17 objects

The public kernel.org machines are actually _two_ different machines, and have two different addresses:

	Non-authoritative answer:
	git.kernel.org  canonical name = zeus-pub.kernel.org.
	Name:   zeus-pub.kernel.org
	Address: 204.152.191.5
	Name:   zeus-pub.kernel.org
	Address: 204.152.191.37

so with a round-robin kind of DNS resolution, you'd get alternate machines. Maybe one of them isn't up-to-date due to mirroring problems?

You can test by using the IP addresses explicitly, of course.

In particular, if the directory doesn't exist at all, or if the directory doesn't have the "git-daemon-export-ok" flag, the git daemon on the other end will just close the connection and refuse to talk to you (I thought that was preferable to give any indication of why it fails: from a security standpoint, you do _not_ want to be able to test if a random directory exists by looking at the return value of git-daemon).

			Linus
Previous: Tim O'Callaghan
Message 3 of 3 in “unexpected EOF?”
  1. Jon LoeligerDec 1, 2005
  2. Tim O'CallaghanDec 1, 2005
  3. Linus TorvaldsDec 1, 2005

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.