Closed Bug 1100162 Opened 9 years ago Closed 9 years ago

High rate of 503s on sync-129

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

Product:
Cloud Services Graveyard
Component:
Server: Sync
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rfkelly, Assigned: jlaz)

Details

Attachments

(1 file)

error-1416205445542.txt
11.96 KB, text/plain
Details 
Several users in #sync and sumo are reporting 503s from sync-129.  Examples:

   https://support.mozilla.org/en-US/questions/1031263
   https://support.mozilla.org/en-US/questions/1031161
   https://pastebin.mozilla.org/7332411

Interestingly the errors are on requests like GET meta/global and GET crypto/keys, rather than the more usual "large POST request times out" error.  I wonder if it's related to a memcache issue, particularly because of meta/global getting involved.

Bob, any insight?
Flags: needinfo?(bobm)
Although, crypto/keys shouldn't be touching memcache AFAIK, so maybe it's not that...
I've been hitting this consistently on every single sync attempt on all of my systems for the last 3 days, it's kinda annoying ;)
Sync-node-129 is now being migrated as we speak.  You should have node-reassignment very soon.  Sorry about the issues Alex!
Node fully migrated.  According to bobm, looks like MySQL had died on this host.  Please reopen if you continue to experience any issues
Assignee: nobody → jlaz
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Flags: needinfo?(bobm)
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.