Sync failing with server maintenance stated as the reason
I'm trying to bring a new laptop up to speed and in sync with my other machines. The sync failed yesterday evening and now again this morning (a 17 hour span). "Sync encountered an error while syncing; Firefox Sync server maintenance is underway, syncing will resume automatically. Sync will automatically retry this action."
http://support.mozilla.org/questions/935263?s=sync+%22maintenance+is+underway%22&r=0&as=s
Another user reported something similar but seemed to have solved his issue with a reset. That did not work for me. Windows Firewall is off for me. http://status.mozilla.com/11627/149178/Sync-%5BBasic%5D says everything's green.
Any other thoughts?
From my original machine, I see similar connection issues. I cannot create a new recovery key. "There was an error changing your recovery key!" I also cannot see how much space my sync is taking up on the servers: "Could not retrieve quota information."
Any other thoughts?
被采纳的解决方案
I've got success now--did nothing different so perhaps a sync server was down.
定位到答案原位置 👍 0所有回复 (2)
1345739776463 Sync.Service DEBUG Exception: Login failed: error.sync.reason.serverMaintenance No traceback available 1345739776463 Sync.Service DEBUG Not syncing: login returned false. 1345739776464 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok 1345739776467 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1345740005793 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1345740274684 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1345740275753 Sync.ErrorHandler DEBUG Beginning user-triggered sync. 1345740275754 Sync.Service DEBUG User-Agent: Firefox/14.0.1 FxSync/1.16.0.20120713134347. 1345740275754 Sync.Service INFO Starting sync at 2012-08-23 10:44:35 1345740275754 Sync.Service DEBUG In sync: should login. 1345740275754 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1345740275754 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1345740275754 Sync.Service INFO Logging in user px7xtianc3zx6vyngrjdnxy6ukej7jfi 1345740275754 Sync.Service DEBUG Caching URLs under storage user base: https://scl2-sync725.services.mozilla.com/1.1/px7xtianc3zx6vyngrjdnxy6ukej7jfi/ 1345740276057 Sync.Resource DEBUG mesg: GET fail 503 https://scl2-sync725.services.mozilla.com/1.1/px7xtianc3zx6vyngrjdnxy6ukej7jfi/info/collections 1345740276057 Sync.Resource DEBUG GET fail 503 https://scl2-sync725.services.mozilla.com/1.1/px7xtianc3zx6vyngrjdnxy6ukej7jfi/info/collections 1345740276057 Sync.Status DEBUG Status.login: error.sync.reason.serverMaintenance => error.login.reason.server 1345740276057 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1345740276057 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance 1345740276057 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1345740276058 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1345740276059 Sync.SyncScheduler DEBUG Next sync in 86400000 ms.
选择的解决方案
I've got success now--did nothing different so perhaps a sync server was down.