New issue
Advanced search Search tips

Issue 706921 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Error: 500: cache entry has expired

Project Member Reported by vapier@chromium.org, Mar 30 2017

Issue description

i have no idea what to do about this error page
https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/22822

Error: 500

cache entry has expired
Request ID: 58dd4f6000ff07bdfd23bfa3b80001737e6c7563692d6d696c6f0001313632322d6336353265653400010105

i wasn't logged in and i got the error.  i logged in and still get the error.  can't view current logs here.
 

Comment 1 by no...@chromium.org, Mar 30 2017

Components: -Infra>Platform>Milo Infra>Platform>Milo>Buildbot
Labels: -Pri-2 Pri-0
Status: Available (was: Untriaged)

Comment 2 by hinoka@chromium.org, Mar 30 2017

Might be a bad config.  Opportunistically changing cache settings to "enabled" instead of strict.

Comment 3 by no...@chromium.org, Mar 30 2017

Labels: -Pri-0 Pri-1
mitigated by flushing memcache. Try to relogin

this still requires investigation

Comment 4 by vapier@chromium.org, Mar 30 2017

thanks, i can view the logs now

Comment 5 by no...@chromium.org, Mar 30 2017

Status: Fixed (was: Available)
the invalid config was reverted

we will improve the reliability so that we don't return http 500 even if the config is temporary invalid

Comment 6 by no...@chromium.org, Apr 3 2017

Issue 706915 has been merged into this issue.

Sign in to add a comment