Closed
Bug 1067638
Opened 10 years ago
Closed 10 years ago
Consistent sync falures for ~24h
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: kael, Unassigned)
Details
(Whiteboard: [qa+])
Attachments
(1 file)
|
3.25 KB,
text/plain
|
Details |
Sync has been consistently failing for over a day on all my machines. The logs show a mix of stuff like this: 1410790026386 Sync.Resource DEBUG mesg: GET fail 503 https://sync-77-us-west-2.sync.services.mozilla.com/1.5/4662609/info/collections 1410790026386 Sync.Resource DEBUG GET fail 503 https://sync-77-us-west-2.sync.services.mozilla.com/1.5/4662609/info/collections 1410818525234 Sync.Resource DEBUG mesg: GET fail 401 https://sync-77-us-west-2.sync.services.mozilla.com/1.5/4662609/info/collections 1410818525234 Sync.Resource DEBUG GET fail 401 https://sync-77-us-west-2.sync.services.mozilla.com/1.5/4662609/info/collections 1410818546414 Sync.Service DEBUG verifyLogin failed: Error: NS_ERROR_CONNECTION_REFUSED (resource://services-sync/resource.js:394:18) JS Stack trace: Res_get@resource.js:414:12 < verifyLogin@service.js:715:18 < onNotify@service.js:992:12 < WrappedNotify@util.js:148:21 < WrappedLock@util.js:103:16 < WrappedCatch@util.js:77:16 < login@service.js:1003:12 < sync/<@service.js:1249:14 < WrappedCatch@util.js:77:16 < sync@service.js:1245:5 Recent sync log attached.
|
||
Comment 1•10 years ago
|
||
Odd. This should be fixed as of this morning. Adding a couple people to look at this...
Whiteboard: [qa+]
|
||
Comment 2•10 years ago
|
||
It looks like you've been moved to a new node, which is a good start - previously sync-77, now sync-117. The time between NS_ERROR_CONNECTION_REFUSED and the preceding statement is only 20s, which seems far too short to be a timeout on the connection. :kael does it consistency produce a similer NS_ERROR_CONNECTION_REFUSED error if you force a sync using "Tools > Sync Now"?
Flags: needinfo?(kg)
|
Reporter | |
Comment 3•10 years ago
|
||
It looks like the sync failures stopped sometime this afternoon; maybe the most recent one I saw on my laptop was due to a wifi drop while it was syncing. Syncs seem to work on my desktop now. (I only filed the bug because I saw the error message about sync again.) Thanks!
Flags: needinfo?(kg)
|
|
||
Comment 4•10 years ago
|
||
OK, good to hear - hopefully this was resolved with our recent server maintenance and node migration, and the errors on the new node were just a network glitch. Thanks for reporting.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•