Closed
Bug 1273081
Opened 8 years ago
Closed 8 years ago
[mozillians.org][prod][celery] Database gave error: OperationalError(2006, 'MySQL server has gone away')
Categories
(Infrastructure & Operations Graveyard :: WebOps: Engagement, task)
Infrastructure & Operations Graveyard
WebOps: Engagement
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nemo-yiannis, Unassigned)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3127])
We are getting these errors triggered by celery: Database gave error: OperationalError(2006, 'MySQL server has gone away') Database error while sync: OperationalError(2006, 'MySQL server has gone away') It looks like this was triggered by some DB work during the weekend. Possible relevant bug from IRC discussion (which I don't have access) is 1264322. We fixed this issue on stage by forcing a chief push that restarts celery. Can you restart celery on prod too?
Reporter | ||
Comment 1•8 years ago
|
||
Here are the sentry errors: https://sentry.prod.mozaws.net/operations/mozilliansorg-prod/issues/332189/ https://sentry.prod.mozaws.net/operations/mozilliansorg-prod/issues/332194/
Reporter | ||
Updated•8 years ago
|
Severity: normal → blocker
Comment 2•8 years ago
|
||
Per request in #moc ran: /etc/init.d/celeryd-mozillians-prod restart /etc/init.d/celeryd-mozillians-prod-beat restart on python[1-4].webapp.phx1.mozilla.com Presumably this still needs to be looked into as to why it failed in the first place from a db failover, leaving bug open.
Severity: blocker → normal
Comment 3•8 years ago
|
||
Also ran by request: /etc/init.d/celeryd-mozillians-dev restart on python1.dev.webapp.phx1
Reporter | ||
Comment 4•8 years ago
|
||
Things look OK with mozillians.org celery services. Errors stopped triggering. Let's leave this one open to investigate what went wrong.
Comment 5•8 years ago
|
||
Sorry, we're pretty swamped at the moment...let's revisit this if it happens again.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•8 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 6•8 years ago
|
||
We are getting the same errors. Can you restart the celery services in all envs as described in comments #2 and #3.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2983] → [kanban:https://webops.kanbanize.com/ctrl_board/2/3127]
Reporter | ||
Updated•8 years ago
|
Severity: normal → critical
Comment 8•8 years ago
|
||
Per request in #moc ran: /etc/init.d/celeryd-mozillians-prod restart /etc/init.d/celeryd-mozillians-prod-beat restart on python[1-4].webapp.phx1.mozilla.com ran : /etc/init.d/celeryd-mozillians-stage restart /etc/init.d/celeryd-mozillians-stage-beat restart on python[12].stage.webapp.phx1.mozilla.com
Comment 9•8 years ago
|
||
Did dev also as per comment #3
Reporter | ||
Comment 10•8 years ago
|
||
Awesome! I'll keep an eye on it to check for any errors. If everything is OK i will close the bug. Thanks for the fast response!
Reporter | ||
Updated•8 years ago
|
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
Updated•8 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
•