404 on code.google.com

[andrey mirtchovski]

anybody else having this issue? hg tries to access code.google.com/p/go and fails:

$ hg sync
abort: HTTP Error 404: Not Found
$

$ for i in `host code.google.com | awk '{print $4}' | grep -v alias`; do echo -n $i: ; curl $i/p/go 2>/dev/null | grep 'was not found' ;  done
74.125.228.1:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.4:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.2:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.7:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.6:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.14:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.0:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.9:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.5:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.8:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>
74.125.228.3:  <p>The requested URL <code>/p/go</code> was not found on this server.  <ins>That’s all we know.</ins>

[Tw]

于2013年8月16日 23:23:45,andrey mirtchovski写到:

> anybody else having this issue? hg tries to access

> code.google.com/p/go <http://code.google.com/p/go> and fails:

>
> $ hg sync
> abort: HTTP Error 404: Not Found
> $
>

> $ for i in `host code.google.com <http://code.google.com> | awk

> '{print $4}' | grep -v alias`; do echo -n $i: ; curl $i/p/go
> 2>/dev/null | grep 'was not found' ; done

> 74.125.228.1 <http://74.125.228.1>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.4 <http://74.125.228.4>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.2 <http://74.125.228.2>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.7 <http://74.125.228.7>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.6 <http://74.125.228.6>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.14 <http://74.125.228.14>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.0 <http://74.125.228.0>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.9 <http://74.125.228.9>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.5 <http://74.125.228.5>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.8 <http://74.125.228.8>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>

> 74.125.228.3 <http://74.125.228.3>: <p>The requested URL

> <code>/p/go</code> was not found on this server. <ins>That’s all we
> know.</ins>
>

> --
> You received this message because you are subscribed to the Google
> Groups "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to golang-nuts...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

I got this error too...

[chris dollin]

Well, that's a kind of relief, because I have this message (or a near

equivalent) too when I attempt to push my nothing-to-do-with-Go

project, so it's not something I've broken in my local configurations
and I can hope that it's a problem that somebody else can fix!

Chris

--
Chris "waiting is" Dollin

[Lubos Pintes]

Just encountered it.

D�a 16. 8. 2013 17:23 andrey mirtchovski wrote / nap�sal(a):
> anybody else having this issue? hg tries to access code.google.com/p/go

> <http://code.google.com/p/go> and fails:

>
> $ hg sync
> abort: HTTP Error 404: Not Found
> $
>

> $ for i in `host code.google.com <http://code.google.com> | awk '{print

> $4}' | grep -v alias`; do echo -n $i: ; curl $i/p/go 2>/dev/null | grep
> 'was not found' ; done

> 74.125.228.1 <http://74.125.228.1>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.4 <http://74.125.228.4>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.2 <http://74.125.228.2>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.7 <http://74.125.228.7>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.6 <http://74.125.228.6>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.14 <http://74.125.228.14>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.0 <http://74.125.228.0>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.9 <http://74.125.228.9>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.5 <http://74.125.228.5>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.8 <http://74.125.228.8>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
> 74.125.228.3 <http://74.125.228.3>: <p>The requested URL
> <code>/p/go</code> was not found on this server. <ins>That�s all we
> know.</ins>
>

[Ives van der Flaas]

With some luck Brad Fitzpatrick will also rewrite that server in go.... (see http://talks.golang.org/2013/oscon-dl.slide#1 in case anyone missed it). 

--

You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Ives van der Flaas
☎ 0499/31.54.37

[andrey mirtchovski]

now it's "abort: HTTP Error 502: Bad Gateway"​

it'll probably be back online soon.

[Andy Balholm]

It appears to be back up for me now.

[andrey mirtchovski]

started working for me too, shortly after atkaaz's message.

On Fri, Aug 16, 2013 at 6:19 PM, Andy Balholm <andyb...@gmail.com> wrote:
> It appears to be back up for me now.
>

[roger peppe]

I had this too (trying to update the vet command). The weird thing is that when I mentioned it in #go-nuts, other people could access the repo just fine while I was getting 404s. I wonder what the issue was.

[Skip Tavakkolian]

Probably related:

http://www.theregister.co.uk/2013/08/17/google_outage/

On Aug 17, 2013 12:19 AM, "roger peppe" <rogp...@gmail.com> wrote:

I had this too (trying to update the vet command). The weird thing is that when I mentioned it in #go-nuts, other people could access the repo just fine while I was getting 404s. I wonder what the issue was.

--

[andrey mirtchovski]

I noted that I could access the repo with a browser, but not with the
hg client or with curl. that's from both linux and osx.

[Kyle Lemons]

On Sat, Aug 17, 2013 at 3:25 AM, Skip Tavakkolian <skip.tav...@gmail.com> wrote:

Probably related:

http://www.theregister.co.uk/2013/08/17/google_outage/

Why would they be related?  They weren't even happening at the same time.

[Skip Tavakkolian]

just a conjecture; i don't know, but the fact that the -- very stable --  Google infrastructure was having problems on the same day as the site -- which I assume is on the same infrastructure -- didn't seem coincidental.