Created attachment 8489702 [details] error-1410818546416.txt 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 < email@example.com:1003:12 < sync/<@service.js:1249:14 < WrappedCatch@util.js:77:16 < firstname.lastname@example.org:1245:5 Recent sync log attached.
Odd. This should be fixed as of this morning. Adding a couple people to look at this...
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"?
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!
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
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.