Sometimes the OOPS page is not rendered correctly
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Steps to reproduce
1. https:/
2. Click the "Choose" link
3. Type aedilis in the popup thing
4. Hit enter
5. The popup search widget should return a link, click on it
6. Click Update
Wait for a while and the offline-
"Please try again
Sorry, there was a problem connecting to the Launchpad server.
Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode."
The apaches logs related to this issue: https:/
And no oops was recorded, which is quite strange.
Doing the same on staging, the OOPS page is rendered successfully and an oops is recorded: OOPS-779S920
| James Henstridge (jamesh) wrote | #1 |
| James Henstridge (jamesh) wrote | #2 |
| Christian Reis (kiko) wrote | #3 |
| Christian Reis (kiko) wrote | #4 |
| tags: |
added: build-infrastructure removed: infrastructure |
| tags: |
added: infrastructure removed: build-infrastructure |
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| visibility: | private → public |
| Gary Poster (gary) wrote | #5 |
| Changed in launchpad-foundations: | |
| status: | Triaged → Won't Fix |
Do we know if Apache even sent the request to any of the app servers before showing the 503 error page?
There have been occasional reports of people seeing the Apache 503 error page when Launchpad is up, so it is possible that this is a problem with the load balancer.