Skip to content

x/website: elevated rate of 502s #30619

@dmitshur

Description

@dmitshur

I am seeing a relatively high frequently of 502s on the golang.org website:

$ time curl 'https://golang.org/_ah/health'
ok
real	0m0.209s
user	0m0.025s
sys	0m0.010s
$ time curl 'https://golang.org/_ah/health'
ok
real	0m0.142s
user	0m0.025s
sys	0m0.007s
$ time curl 'https://golang.org/_ah/health'
ok
real	0m0.141s
user	0m0.025s
sys	0m0.007s
$ time curl 'https://golang.org/_ah/health'

<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>502 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>

real	0m9.192s
user	0m0.017s
sys	0m0.006s
$ time curl 'https://golang.org/_ah/health'
ok
real	0m0.438s
user	0m0.022s
sys	0m0.007s
$ time curl 'https://golang.org/_ah/health'
ok
real	0m0.142s
user	0m0.024s
sys	0m0.007s

I suspect it's what's causing golang/lint#440. /cc @agnivade

It seems to be happening on previously deployed versions of golang.org, not just the current one.

The last error that https://tip.golang.org/_tipstatus ran into is also 502 related, but when cloning from go.googlesource.com/go:

error=builder.Init: checkout of go: fetch: fatal: unable to access 'https://go.googlesource.com/go/': The requested URL returned error: 502

Maybe it's related to some higher-level component and not the website specifically? I don't have enough information to tell yet. /cc @bradfitz @andybons

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrozenDueToAgeNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions