unexpected EOF?

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.

Some state:

jdl@ubuntu:/usr/src/git-core$ git --version
git version 0.99.9j

jdl@ubuntu:/usr/src/git-core$ cat .git/remotes/origin
URL: git://git.kernel.org/pub/scm/git/git.git/
Pull: master:origin
Pull: todo:todo
Pull: maint:maint
Pull: pu:pu

And the error capture:

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
 100% (17/17) done
* committish: d175455acaaba6bd39dd2d5ec71961bf238f06d4
  branch 'todo' of git://git.kernel.org/pub/scm/git/git
* refs/heads/todo: same as branch 'todo' of git://git.kernel.org/pub/scm/git/git* committish: 93dcab2937624ebb97f91807576cddb242a55a46
  branch 'maint' of git://git.kernel.org/pub/scm/git/git
* refs/heads/maint: same as branch 'maint' of git://git.kernel.org/pub/scm/git/git
* committish: b34403aa97047f90c0cdd5177e63a8e7530e3388
  branch 'master' of git://git.kernel.org/pub/scm/git/git
* refs/heads/origin: same as branch 'master' of git://git.kernel.org/pub/scm/git/git
* committish: 6e35634a4d595d554423b04438bfa8b523414c54
  branch 'pu' of git://git.kernel.org/pub/scm/git/git
* refs/heads/pu: does not fast forward to branch 'pu' of git://git.kernel.org/pub/scm/git/git;
  not updating.
Already up-to-date.

I noticed this myself this morning. It happened twice, then after leaving it for a minute or two, it worked. Possibly traffic problems to kernel.org?

I should also report that if a spurious lockfile exists (under cygwin at least), git just dies with the cryptic "unable to create new cachefile".

Tim.
"I've worked myself up from nothing to a state of supreme poverty." -- Groucho Marx

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