Kept getting sync error message for the past few days
I haven't been able to sync my accounts for the past few days. Below is the error message: "Sync encountered an error while syncing: Firefox Sync server maintenance is underway, syncing will resume automatically. Sync will automatically retry this action."
My latest error log is below:
1416113749815 Sync.ErrorHandler DEBUG Flushing file log. 1416113749817 Sync.Service DEBUG Exception: Login failed: error.sync.reason.serverMaintenance No traceback available 1416113749817 Sync.Service DEBUG Not syncing: login returned false. 1416113749817 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok 1416113749821 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1416113749821 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1416113749840 Sync.ErrorHandler DEBUG Log cleanup threshold time: 1415249749840 1416113749844 Sync.ErrorHandler DEBUG No logs to clean up. 1416114123789 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1416114123791 Sync.ErrorHandler DEBUG Beginning user-triggered sync. 1416114123791 Sync.Service DEBUG User-Agent: Firefox/33.1.1 FxSync/1.35.0.20141113143407. 1416114123791 Sync.Service INFO Starting sync at 2014-11-15 21:02:03 1416114123792 Sync.Service DEBUG In sync: should login. 1416114123792 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1416114123792 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1416114123793 Sync.Service INFO Logging in the user. 1416114123793 Sync.Service DEBUG Caching URLs under storage user base: https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/ 1416114123795 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1416114124226 Sync.Resource DEBUG mesg: GET success 200 https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/info/collections 1416114124227 Sync.Resource DEBUG GET success 200 https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/info/collections 1416114124227 Sync.Service DEBUG Fetching global metadata record 1416114124227 Sync.Service DEBUG Weave Version: 1.35.0 Local Storage: 5 Remote Storage: 5 1416114124227 Sync.Service INFO Sync key is up-to-date: no need to upgrade. 1416114124227 Sync.Service DEBUG Fetching and verifying -- or generating -- symmetric keys. 1416114124227 Sync.Service INFO Testing info/collections: {"prefs":1415684960.1,"tabs":1416002806.09,"clients":1415999571.59,"crypto":1411776108.31,"meta":1413417019.06,"bookmarks":1415995802.11,"addons":1415981896.19} 1416114124227 Sync.CollectionKeyManager INFO Testing for updateNeeded. Last modified: 0 1416114124227 Sync.Service INFO collection keys reports that a key update is needed. 1416114124228 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1416114124424 Sync.Resource DEBUG mesg: GET fail 503 https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/storage/crypto/keys 1416114124424 Sync.Resource DEBUG GET fail 503 https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/storage/crypto/keys 1416114124425 Sync.Status DEBUG Status.login: error.sync.reason.serverMaintenance => error.login.reason.server 1416114124425 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1416114124425 Sync.ErrorHandler DEBUG Got Retry-After: 3600 1416114124425 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance 1416114124425 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1416114124425 Sync.SyncScheduler DEBUG Got backoff notification: 3600000ms 1416114124425 Sync.SyncScheduler DEBUG Fuzzed minimum next sync: 1416117724425 1416114124425 Sync.Service WARN Got status 503 fetching crypto keys. 1416114124425 Sync.Service WARN Failed to fetch symmetric keys. Failing remote setup. 1416114124425 Sync.Service WARN Remote setup failed. 1416114124425 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1416114124426 Sync.SyncScheduler DEBUG Next sync in 4079084.8112176084 ms.
I haven't been able to sync my accounts for the past few days.
Below is the error message:
"Sync encountered an error while syncing: Firefox Sync server maintenance is underway, syncing will resume automatically. Sync will automatically retry this action."
My latest error log is below:
<pre><nowiki>1416113749815 Sync.ErrorHandler DEBUG Flushing file log.
1416113749817 Sync.Service DEBUG Exception: Login failed: error.sync.reason.serverMaintenance No traceback available
1416113749817 Sync.Service DEBUG Not syncing: login returned false.
1416113749817 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok
1416113749821 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok
1416113749821 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok
1416113749840 Sync.ErrorHandler DEBUG Log cleanup threshold time: 1415249749840
1416113749844 Sync.ErrorHandler DEBUG No logs to clean up.
1416114123789 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok
1416114123791 Sync.ErrorHandler DEBUG Beginning user-triggered sync.
1416114123791 Sync.Service DEBUG User-Agent: Firefox/33.1.1 FxSync/1.35.0.20141113143407.
1416114123791 Sync.Service INFO Starting sync at 2014-11-15 21:02:03
1416114123792 Sync.Service DEBUG In sync: should login.
1416114123792 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok
1416114123792 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok
1416114123793 Sync.Service INFO Logging in the user.
1416114123793 Sync.Service DEBUG Caching URLs under storage user base: https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/
1416114123795 Sync.BrowserIDManager DEBUG _ensureValidToken already has one
1416114124226 Sync.Resource DEBUG mesg: GET success 200 https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/info/collections
1416114124227 Sync.Resource DEBUG GET success 200 https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/info/collections
1416114124227 Sync.Service DEBUG Fetching global metadata record
1416114124227 Sync.Service DEBUG Weave Version: 1.35.0 Local Storage: 5 Remote Storage: 5
1416114124227 Sync.Service INFO Sync key is up-to-date: no need to upgrade.
1416114124227 Sync.Service DEBUG Fetching and verifying -- or generating -- symmetric keys.
1416114124227 Sync.Service INFO Testing info/collections: {"prefs":1415684960.1,"tabs":1416002806.09,"clients":1415999571.59,"crypto":1411776108.31,"meta":1413417019.06,"bookmarks":1415995802.11,"addons":1415981896.19}
1416114124227 Sync.CollectionKeyManager INFO Testing for updateNeeded. Last modified: 0
1416114124227 Sync.Service INFO collection keys reports that a key update is needed.
1416114124228 Sync.BrowserIDManager DEBUG _ensureValidToken already has one
1416114124424 Sync.Resource DEBUG mesg: GET fail 503 https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/storage/crypto/keys
1416114124424 Sync.Resource DEBUG GET fail 503 https://sync-129-us-west-2.sync.services.mozilla.com/1.5/9195458/storage/crypto/keys
1416114124425 Sync.Status DEBUG Status.login: error.sync.reason.serverMaintenance => error.login.reason.server
1416114124425 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed
1416114124425 Sync.ErrorHandler DEBUG Got Retry-After: 3600
1416114124425 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance
1416114124425 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed
1416114124425 Sync.SyncScheduler DEBUG Got backoff notification: 3600000ms
1416114124425 Sync.SyncScheduler DEBUG Fuzzed minimum next sync: 1416117724425
1416114124425 Sync.Service WARN Got status 503 fetching crypto keys.
1416114124425 Sync.Service WARN Failed to fetch symmetric keys. Failing remote setup.
1416114124425 Sync.Service WARN Remote setup failed.
1416114124425 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score.
1416114124426 Sync.SyncScheduler DEBUG Next sync in 4079084.8112176084 ms.</nowiki></pre>
Modified by cor-el
Chosen solution
it might still take a bit, since it's currently weekend and most sync engineers are stationed in the us west-coast timezone...
edit: you can follow along progress for this this issue at bug #1100162
Read this answer in context 👍 1All Replies (3)
hello v4ever, this is most likely an issue on the server side at the moment & nothing wrong on your particular installation/account. it's probably best to just sit this one out - sorry for the inconvenience...
Thanks for your quick reply, philipp. Do you know how long it will take for the server problem to get resolved? Are a lot of other people having similar problems?
Seçilmiş Həll
it might still take a bit, since it's currently weekend and most sync engineers are stationed in the us west-coast timezone...
edit: you can follow along progress for this this issue at bug #1100162
Modified by philipp