Page MenuHomePhabricator

Jenkins: Consistently getting 503 Varnish in response to succesful login
Closed, ResolvedPublic

Description

As of late, when logging in to Jenkins I get a 503 error from Varnish in return (the green wmerror page, much like our php/wmerror one).

https://integration.wikimedia.org/ci/login?from=%2Fci%2F

It only does that for a successful login though, with a wrong password it just shows the login form again with the relevant error message.


Version: wmf-deployment
Severity: normal

Details

Reference
bz61710

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:57 AM
bzimport set Reference to bz61710.
bzimport added a subscriber: Unknown Object (MLST).

When I manually go back with cache disabled it shows me being logged in though, so it did somehow get through.

Might be related to bug 58279, aka http redirects to https being cached in varnish and cache not varying by protocol.

Patch is https://gerrit.wikimedia.org/r/#/c/114464/ , will be deployed on monday.

The patch got deployed and the misc varnish cache is now instructed to vary by protocol (Vary: X-Forwarded-Proto). I guess that would solve this bug as well.

Krinkle reopened this task as Open.EditedJun 7 2015, 5:14 PM

Still happening.

https://integration.wikimedia.org/ci/loginError

If you report this error to the Wikimedia System Administrators, please include the details below.

Request: GET http://integration.wikimedia.org/ci/loginError, from 10.64.0.172 via cp1044 cp1044 ([10.64.0.172]:80), Varnish XID 265195218
Forwarded for: 90.220.24.136, 10.64.0.172
Error: 503, Service Unavailable at Sun, 07 Jun 2015 17:14:09 GMT
hashar triaged this task as Low priority.Jun 9 2015, 2:23 PM
hashar moved this task from Untriaged to Backlog on the Continuous-Integration-Infrastructure board.

Still happening. Makes logging into Jenkins unnecessarily difficult.

At the time I think I encountered the issue a couple time at most. Since 2015 lot of things have changed (Jenkins upgrades, Varnish/vcl changed ..), I don't think this task applies anymore.

@Krinkle do you still encounter those 503 when login to Jenkins?