Closed
Bug 972589
Opened 12 years ago
Closed 12 years ago
One and Done prod paas 404ing after a bit of uptime
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: osmose, Assigned: cturra)
References
()
Details
After getting One and Done set up successfully on the prod paas, we started seeing constant 404s across the site after maybe an hour of uptime. The 404s seemingly started without any change by me.
Once again, my ops-idiodicy is blocking me. Any tips on how to proceed?
Assignee | ||
Comment 1•12 years ago
|
||
i restarted your app, which moved it to a new dea server in the paas cluster. right now, we're sorting out some name server stuff as tracked in bug 971983, which i suspect is related here.
additionally, we've seen another app lose connection in the past when the stackato core routing service marked the app as down due to connection attempts. that permanent solution to that is unrelated to the bug mentioned above, but is in the patches i will be applying to the prod cluster tomorrow evening.
https://mail.mozilla.org/pipermail/paas-users/2014-February/000194.html
Assignee: server-ops-webops → cturra
Assignee | ||
Comment 2•12 years ago
|
||
it looks like since the maintenance we did on monday evening, applications are no longer being marked as down by the stackato router (causing the 404's we were seeing here). i am going to mark this bug as r/fixed, but please re-open if this issue creeps back up on us again o/
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 3•12 years ago
|
||
Thx; this host is returning a 200 OK: https://oneanddone.mozilla.org/en-US/
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•