As Quarry app itself is behind a nginx reverse proxy and sometimes fails, 502 error is not uncommon. Having a user-friendly error message would be great.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| quarry: nginx conf for custom 50x error pages | operations/puppet | production | +4 -0 | |
| Create custom 50x error pages | analytics/quarry/web | master | +146 -0 |
Related Objects
Related Objects
- Mentioned Here
- rANQW3776b5f906c0: Create custom 50x error pages
Event Timeline
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2019-05-11T22:00:52Z] <framawiki> disabling puppet temporary on -web-01 to test nginx conf T223018
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2019-05-11T22:10:16Z] <framawiki> re-enable puppet T223018
Comment Actions
Change 509606 had a related patch set uploaded (by Framawiki; owner: Framawiki):
[analytics/quarry/web@master] Create custom 50x error pages
Comment Actions
Change 509608 had a related patch set uploaded (by Framawiki; owner: Framawiki):
[operations/puppet@production] quarry: nginx conf for custom 50x error pages
Comment Actions
Change 509606 merged by jenkins-bot:
[analytics/quarry/web@master] Create custom 50x error pages
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2019-05-12T17:57:07Z] <wm-bot> framawiki: Deployed 3776b5f on -web-01 T223018
Comment Actions
Change 509608 merged by Andrew Bogott:
[operations/puppet@production] quarry: nginx conf for custom 50x error pages
Comment Actions
Works as excepted, yeah! Now if the standard nginx bad gateway error page is shown, that originate from WMCS shared web proxy hosts and that says that quarry host is not responding at all.