Closed
Bug 1154584
Opened 9 years ago
Closed 9 years ago
[basket] DOWNTIME. Error rate very high in New Relic.
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmac, Assigned: fox2mike)
References
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/952] )
Can't get MOC to do anything via IRC, so I'm coming here. New Relic for basket.mozilla.org is showing a lot of errors related to an inability to contact the DB starting at 6:30pm Pacific. I can contact that DB if I SSH in, so I'm guessing Apache just needs a kick. No idea what went wrong yet, but it looks like all DB related requests are 500ing. https://rpm.newrelic.com/accounts/263620/applications/2646232/traced_errors
Assignee | ||
Updated•9 years ago
|
Assignee: server-ops-webops → smani
Assignee | ||
Comment 1•9 years ago
|
||
atoll and pmac diagnosed this and I kicked httpd on the generic webheads. This seems to have fixed the issue.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•9 years ago
|
||
This appears to have happened again this morning between ~9:45AM and 10:30AM Eastern time. :cyliang believes it was resolved on its own this time by an apache segfault and restart. Let's see if we can track the root of this so we can avoid it in future.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/basket https://github.com/mozilla/basket/commit/b4c375cf1f1a62920f06dc6ce258e471d97f7974 Bug 1154584: Disable ratelimit for email subscribe. We think it might be causing problems. Disabling temporarily to see if our theory is correct.
Assignee | ||
Comment 4•9 years ago
|
||
This has been stable.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Updated•5 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
•