Closed
Bug 684766
Opened 13 years ago
Closed 13 years ago
Normalize "server issue" 503 bodies
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Cloud Services
Operations: Miscellaneous
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rnewman, Unassigned)
References
Details
(Whiteboard: [qa+])
Per discussion in IRC re Bug 684751. [17:21] atoll: file a bug for us to change "255" [17:22] atoll: "255" means "all backend servers are overloaded" [17:22] atoll: which is early warning of that nagios alert there
note that changing this won't help much, since no firefox client currently logs the 503 error body, so this is basically only useful for the lucky few who notice
correction, in limited specific cases firefox writes the body into the log, for instance history engine (yay). therefore, improve this to be human-readable for end users, prefixed with "server issue: " so that they are hinted to report to us.
Reporter | ||
Comment 3•13 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=684788#c3. Morphing this.
Summary: Return more useful 503 body than "255" when backend servers are overloaded → Normalize "server issue" 503 bodies
replaced "255" with "server issue: pool exhausted", documented at intranet/Services/Ops/ZeusSetup, deployed dev/test/stage/scl2/phx. Need to update a table of error codes somewhere.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•13 years ago
|
||
(In reply to Richard Soderberg [:atoll] from comment #4) > Need to update a table of error codes somewhere. Done: https://hg.mozilla.org/services/docs/rev/a6bcd0593a69
Updated•13 years ago
|
Whiteboard: [qa+]
You need to log in
before you can comment on or make changes to this bug.
Description
•