Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

sync has not been able to complete during the last 7 days

  • 5 个回答
  • 35 人有此问题
  • 4 次查看
  • 最后回复者为 philipp

more options

On none of my 3 computers sync is working for more than a week now. Resetting sync (Replace all other devices with.... ) won't work either. Please advice me what to do.

On none of my 3 computers sync is working for more than a week now. Resetting sync (Replace all other devices with.... ) won't work either. Please advice me what to do.

所有回复 (5)

more options

Try to uninstall (unlink this device) and setup sync again.

Is there anything unusual reported in the Sync log (about:sync-log)?

Try to create a new profile as a test to check if your current profile is causing the problems.

See "Creating a profile":

If the new profile works then you can transfer some files from an existing profile to the new profile, but be careful not to copy corrupted files.

more options

Same here, I have got 4 devices have sync problem. I have tried to View Quota, Reset Sync, Change Recovery Key but all failed.

Here is the latest sync log...

1
367810164569	Sync.ErrorHandler	DEBUG	Flushing file log.
1367810164570	Sync.Status	DEBUG	Status.sync: error.sync.prolonged_failure => error.sync.prolonged_failure
1367810164570	Sync.Status	DEBUG	Status.service: error.login.failed => error.sync.failed
1367810164570	Sync.Service	DEBUG	Exception: Login failed: error.sync.reason.serverMaintenance No traceback available
1367810164570	Sync.Service	DEBUG	Not syncing: login returned false.
1367810164570	Sync.Notifications	ERROR	An exception occurred: Could not convert Native argument arg 3 [nsIDOMJSWindow.openDialog] Stack trace: openPreferences()@utilityOverlay.js:499 < SUI_openPrefs()@browser.js:7414 < browser.js:7318 < callbackWrapper()@resource://gre/modules/services-sync/notifications.js:116 < _doButtonCommand()@notification.xml:433 < oncommand()@browser.xul:1 < <file:unknown>
1367810164570	Sync.Notifications	INFO	Stack trace: openPreferences()@utilityOverlay.js:499 < SUI_openPrefs()@browser.js:7414 < browser.js:7318 < callbackWrapper()@resource://gre/modules/services-sync/notifications.js:116 < _doButtonCommand()@notification.xml:433 < oncommand()@browser.xul:1 < <file:unknown>
1367810164571	Sync.Status	DEBUG	Status.service: error.sync.failed => success.status_ok
1367810164574	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1367810164687	Sync.ErrorHandler	DEBUG	Log cleanup threshold time: 1366946164687
1367810164690	Sync.ErrorHandler	DEBUG	No logs to clean up.
1367810272259	Sync.StorageRequest	DEBUG	GET https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/info/quota 200
1367810327623	Sync.Resource	DEBUG	mesg: DELETE fail 503 https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/storage
1367810327623	Sync.Resource	DEBUG	DELETE fail 503 https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/storage
1367810347348	Sync.Service	DEBUG	Aborting wipeServer. Server responded with 503 response for https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/storage/
1367810347349	Sync.Service	DEBUG	Exception: "\"application error: crash id 69e2c8d22204d81267e79506c33fb615\"" No traceback available
1367810825775	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1367810827442	Sync.ErrorHandler	DEBUG	Beginning user-triggered sync.
1367810827443	Sync.Service	DEBUG	User-Agent: Firefox/20.0.1 FxSync/1.22.0.20130409194949.
1367810827443	Sync.Service	INFO	Starting sync at 2013-05-06 11:27:07
1367810827443	Sync.Service	DEBUG	In sync: should login.
1367810827443	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1367810827443	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1367810827443	Sync.Service	INFO	Logging in user [ACCOUNT]
1367810827443	Sync.Service	DEBUG	Caching URLs under storage user base: https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/
1367810828255	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1367810849322	Sync.Resource	DEBUG	mesg: GET success 200 https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/info/collections
1367810849322	Sync.Resource	DEBUG	GET success 200 https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/info/collections
1367810849322	Sync.Service	DEBUG	Fetching global metadata record
1367810849322	Sync.Service	DEBUG	Weave Version: 1.22.0 Local Storage: 5 Remote Storage: 5
1367810849322	Sync.Service	INFO	Sync key is up-to-date: no need to upgrade.
1367810849322	Sync.Service	DEBUG	Fetching and verifying -- or generating -- symmetric keys.
1367810849537	Sync.Resource	DEBUG	mesg: GET success 200 https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/info/collections
1367810849537	Sync.Resource	DEBUG	GET success 200 https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/info/collections
1367810849537	Sync.Service	INFO	Testing info/collections: {"forms":1367655088.58,"bookmarks":1366994242.87,"clients":1367722999.94,"history":1367566530.47}
1367810849537	Sync.CollectionKeyManager	INFO	Testing for updateNeeded. Last modified: 0
1367810849537	Sync.Service	INFO	collection keys reports that a key update is needed.
1367810849537	Sync.Service	INFO	... 'crypto' is not a reported collection. Generating new keys.
1367810849537	Sync.Service	INFO	No keys! Generating new ones.
1367810849537	Sync.Service	INFO	Fresh start. Resetting client and considering key upgrade.
1367810849537	Sync.Service	INFO	Service reset.
1367810849537	Sync.Engine.Clients	DEBUG	Resetting clients last sync time
1367810849537	Sync.Engine.Bookmarks	DEBUG	Resetting bookmarks last sync time
1367810849538	Sync.Engine.Forms	DEBUG	Resetting forms last sync time
1367810849538	Sync.Engine.History	DEBUG	Resetting history last sync time
1367810849538	Sync.Engine.Passwords	DEBUG	Resetting passwords last sync time
1367810849539	Sync.Engine.Prefs	DEBUG	Resetting prefs last sync time
1367810849539	Sync.Engine.Tabs	DEBUG	Resetting tabs last sync time
1367810849539	Sync.Engine.Addons	DEBUG	Resetting addons last sync time
1367810849539	Sync.CollectionKeyManager	INFO	Clearing collection keys...
1367810849539	Sync.Service	INFO	Sync key is up-to-date: no need to upgrade.
1367810857622	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1367810882494	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1367810901594	Sync.Resource	DEBUG	mesg: DELETE fail 503 https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/storage
1367810901594	Sync.Resource	DEBUG	DELETE fail 503 https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/storage
1367810901594	Sync.Service	DEBUG	Aborting wipeServer. Server responded with 503 response for https://phx-sync108.services.mozilla.com/1.1/[ACCOUNT]/storage/
1367810901594	Sync.Service	DEBUG	Failed to fetch and verify keys: "server error: converted 500" No traceback available
1367810901594	Sync.ErrorHandler	DEBUG	Got Retry-After: 600
1367810901594	Sync.Status	DEBUG	Status.login: error.sync.reason.serverMaintenance => error.sync.reason.serverMaintenance
1367810901594	Sync.Status	DEBUG	Status.service: success.status_ok => error.login.failed
1367810901595	Sync.SyncScheduler	DEBUG	Got backoff notification: 600000ms
1367810901595	Sync.SyncScheduler	DEBUG	Fuzzed minimum next sync: 1367811501595
1367810901595	Sync.Service	WARN	Failed to fetch symmetric keys. Failing remote setup.
1367810901595	Sync.Service	WARN	Remote setup failed.
1367810901595	Sync.SyncScheduler	DEBUG	Clearing sync triggers and the global score.
1367810901595	Sync.SyncScheduler	DEBUG	Next sync in 3600000 ms.

由cor-el于修改

more options

please also make sure that the system's date & time is set correctly on all devices...

more options

I've tried reset firefox, reset password, change key, unlink, relink, etc. NONE of these work, and always comes with weird script timeout...

Eventually, everything back to normal when I try again some other night. I strongly believe that the problem is not from my site.

more options

yes, you're right - i've learned that there where server issues which have been resolved now.