Re: Git fetch/pull stopped working

From: Carlos Martín Nieto <cmn@elego.de>
Date: May 8, 2012, 00:10 UTC
Message-ID: <20120508001018.GB5067@centaur.lab.cmartin.tk>
In-Reply-To: <7vehqv36aw.fsf@alter.siamese.dyndns.org>

On Mon, May 07, 2012 at 04:44:23PM -0700, Junio C Hamano wrote:

Show 26 quoted lines

> Egor Ryabkov <egor.ryabkov@gmail.com> writes:
> 
> > git fetch and pull stopped working a few days ago on my server with
> > the following message:
> >
> > $ git fetch
> > ERROR: Repository not found.
> > fatal: The remote end hung up unexpectedly
> 
> Are you sure it is an error on the remote side (presumably on GitHub)?
> 
> More interestingly, neither "Repository not found" nor "ERROR:" hits
> anything relevant to "git fetch" codepath.  The closest I can find is in
> http-backend.c that says "Repository not exported", which is on the server
> side, but you were talking about ssh connection, so it probably is not
> what you are seeing.
> 
> Oh, wait.
> 
> > "$ GIT_TRACE=1 git fetch" gives somewhat different output on local PC
> > and server:
> > http://pastecode.com/bd3fc1a79f8e9d1eaf30911d9895938051c472f4
> 
> So you are going over http:// after all.  But it does not look like github
> to me, so you may be comparing apples and oranges, which would not help in
> diagnosing the issue very much.

I can reproduce this issue. It happens somewhere between my phone jack and rackspace.

I can perform 'git fetch' on other hosts and ssh -T git@github.com works fine. However, trying to fetch from github gives me an error.

Not only this, but trying to browse to github.com or rubygems.org, both of which seem to be hosted on the same datacentre gives me timeouts or takes really long to answer. Routing traffic through my server in the next country over makes it work, as does fetching from that host.

The only difference I've been able to find is that the traffic looks like it goes through different hosts when it goes through the UK on its way to the US.

> 
> Puzzled...

Yeah... It looks like the Internet is being silly. So much for routing around damage. What I'm not sure is how this would also affect AWS; maybe the Irish one?

cmn