Closed
Bug 785021
Opened 13 years ago
Closed 13 years ago
Sync fails with error.sync.reason.serverMaintenance (GET 503 "server issue: database is not healthy")
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Cloud Services
Operations: Miscellaneous
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: fowl2, Unassigned)
Details
Attachments
(1 file)
1.82 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20120821135628
Steps to reproduce:
A few days ago I install Nightly on a new computer and used my phone to add it to Sync. It accepted the code and proceeded to the "initial sync" tab. A short time later a yellow warning bar appeared indicating that "Firefox Sync server maintenance is underway". This has started showing up on my laptop too.
Both devices have log entries like this:
1345712992815 Sync.Resource DEBUG GET fail 503 https://scl2-sync730.services.mozilla.com/1.1/fowl/info/collections
Pasting that URL in my browser returns: "server issue: database is not healthy"
https://services.mozilla.com/status/ reports "No known issues at this time. "
My phone (Android, also Nightly) doesn't report any issues.
Apologies if this is in an incorrect component - I can't tell if this a client or a server issue, but it looks like a server one (503).
Thanks
Comment 1•13 years ago
|
||
a 503 will almost certainly be a server problem. Thanks for bringing it to our attention.
Throwing it over to ops to see what's in the logs.
Component: Server: Sync → Operations
Has the error bar remained present without fail since "a few days ago"? Has sync worked at all since then, or been broken continuously?
Comment 3•13 years ago
|
||
It looks like one of our scl2 dbs servers has had issues. I've migrated users from that node (filed bug 785132)
James, can you try to resync once again?
Comment 4•13 years ago
|
||
Feel free to reopen if you continue to have issues :)
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•13 years ago
|
||
Thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•