搜索 | 用户支持

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

详细了解

Syncing is not working and I tried about:sync-log, and found some errors but don't know how to fix them.

  • 2 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 guigs

more options

This is the log of error:

1524015364158 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015364158 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015364158 Sync.Service INFO Starting sync at 2018-04-18 03:36:04 in browser session YA5kZOsRpWpQ 1524015364160 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1524015364160 Sync.Status INFO Resetting Status. 1524015364160 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1524015364160 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1524015567114 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015567116 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=schedule) 1524015567120 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015567120 Sync.Service INFO Starting sync at 2018-04-18 03:39:27 in browser session YA5kZOsRpWpQ 1524015567122 Sync.Service DEBUG Exception calling anonymous function: LockException: Could not acquire lock. Label: "service.js: sync". (resource://services-sync/util.js:43:5) JS Stack trace: [email protected]:43:5 < [email protected]:119:11 < [email protected]:133:9 < [email protected]:1099:12 < sync/<@service.js:1091:13 < [email protected]:107:22 < [email protected]:1080:12 1524015567124 Sync.Service INFO Cannot start sync: already syncing? 1524015567158 Sync.SyncScheduler DEBUG Woke from sleep. 1524015567164 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015567172 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015567172 Sync.Service INFO Starting sync at 2018-04-18 03:39:27 in browser session YA5kZOsRpWpQ 1524015567172 Sync.Service DEBUG Exception calling anonymous function: LockException: Could not acquire lock. Label: "service.js: sync". (resource://services-sync/util.js:43:5) JS Stack trace: [email protected]:43:5 < [email protected]:119:11 < [email protected]:133:9 < [email protected]:1099:12 < sync/<@service.js:1091:13 < [email protected]:107:22 < [email protected]:1080:12 1524015567174 Sync.Service INFO Cannot start sync: already syncing? 1524015570280 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015570282 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015570282 Sync.Service INFO Starting sync at 2018-04-18 03:39:30 in browser session YA5kZOsRpWpQ 1524015570282 Sync.Service DEBUG Exception calling anonymous function: LockException: Could not acquire lock. Label: "service.js: sync". (resource://services-sync/util.js:43:5) JS Stack trace: [email protected]:43:5 < [email protected]:119:11 < [email protected]:133:9 < [email protected]:1099:12 < sync/<@service.js:1091:13 < [email protected]:107:22 < [email protected]:1080:12 1524015570284 Sync.Service INFO Cannot start sync: already syncing? 1524015571288 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015571290 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015571290 Sync.Service INFO Starting sync at 2018-04-18 03:39:31 in browser session YA5kZOsRpWpQ 1524015571290 Sync.Service DEBUG Exception calling anonymous function: LockException: Could not acquire lock. Label: "service.js: sync". (resource://services-sync/util.js:43:5) JS Stack trace: [email protected]:43:5 < [email protected]:119:11 < [email protected]:133:9 < [email protected]:1099:12 < sync/<@service.js:1091:13 < [email protected]:107:22 < [email protected]:1080:12 1524015571290 Sync.Service INFO Cannot start sync: already syncing? 1524015576296 Sync.Resource WARN GET request to https://sync-540-us-west-2.sync.services.mozilla.com/1.5/100607571/info/collections failed: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1524015576296 Sync.ErrorHandler ERROR Sync encountered an error: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1524015576298 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=reschedule) 1524015576300 Sync.Service DEBUG Exception calling anonymous function: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1524015576300 Sync.ErrorHandler DEBUG Addons installed: 0

This is the log of error: 1524015364158 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015364158 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015364158 Sync.Service INFO Starting sync at 2018-04-18 03:36:04 in browser session YA5kZOsRpWpQ 1524015364160 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1524015364160 Sync.Status INFO Resetting Status. 1524015364160 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1524015364160 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1524015567114 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015567116 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=schedule) 1524015567120 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015567120 Sync.Service INFO Starting sync at 2018-04-18 03:39:27 in browser session YA5kZOsRpWpQ 1524015567122 Sync.Service DEBUG Exception calling anonymous function: LockException: Could not acquire lock. Label: "service.js: sync". (resource://services-sync/util.js:43:5) JS Stack trace: [email protected]:43:5 < [email protected]:119:11 < [email protected]:133:9 < [email protected]:1099:12 < sync/<@service.js:1091:13 < [email protected]:107:22 < [email protected]:1080:12 1524015567124 Sync.Service INFO Cannot start sync: already syncing? 1524015567158 Sync.SyncScheduler DEBUG Woke from sleep. 1524015567164 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015567172 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015567172 Sync.Service INFO Starting sync at 2018-04-18 03:39:27 in browser session YA5kZOsRpWpQ 1524015567172 Sync.Service DEBUG Exception calling anonymous function: LockException: Could not acquire lock. Label: "service.js: sync". (resource://services-sync/util.js:43:5) JS Stack trace: [email protected]:43:5 < [email protected]:119:11 < [email protected]:133:9 < [email protected]:1099:12 < sync/<@service.js:1091:13 < [email protected]:107:22 < [email protected]:1080:12 1524015567174 Sync.Service INFO Cannot start sync: already syncing? 1524015570280 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015570282 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015570282 Sync.Service INFO Starting sync at 2018-04-18 03:39:30 in browser session YA5kZOsRpWpQ 1524015570282 Sync.Service DEBUG Exception calling anonymous function: LockException: Could not acquire lock. Label: "service.js: sync". (resource://services-sync/util.js:43:5) JS Stack trace: [email protected]:43:5 < [email protected]:119:11 < [email protected]:133:9 < [email protected]:1099:12 < sync/<@service.js:1091:13 < [email protected]:107:22 < [email protected]:1080:12 1524015570284 Sync.Service INFO Cannot start sync: already syncing? 1524015571288 Sync.SyncScheduler DEBUG Network link looks up. Syncing. 1524015571290 Sync.Service DEBUG User-Agent: Firefox/59.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.61.0.20180323154952.desktop 1524015571290 Sync.Service INFO Starting sync at 2018-04-18 03:39:31 in browser session YA5kZOsRpWpQ 1524015571290 Sync.Service DEBUG Exception calling anonymous function: LockException: Could not acquire lock. Label: "service.js: sync". (resource://services-sync/util.js:43:5) JS Stack trace: [email protected]:43:5 < [email protected]:119:11 < [email protected]:133:9 < [email protected]:1099:12 < sync/<@service.js:1091:13 < [email protected]:107:22 < [email protected]:1080:12 1524015571290 Sync.Service INFO Cannot start sync: already syncing? 1524015576296 Sync.Resource WARN GET request to https://sync-540-us-west-2.sync.services.mozilla.com/1.5/100607571/info/collections failed: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1524015576296 Sync.ErrorHandler ERROR Sync encountered an error: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1524015576298 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=reschedule) 1524015576300 Sync.Service DEBUG Exception calling anonymous function: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1524015576300 Sync.ErrorHandler DEBUG Addons installed: 0

所有回复 (2)

more options

Hi, this has been referred to a Supervisor. Expect contact within a couple of days.

more options

Hi there,

So thank you for you patience. I have shared the logs you mention in your question with the experts, and I have been advised to share the following for your benefit.

This is the most current guide for how to consult the Firefox Sync team in bugzilla about errors in your Firefox Sync account: https://wiki.mozilla.org/CloudService.../File_a_desktop_bug

Please feel free to use this link in other sync-log error scenarios for those lurking in this post.

The advise for your specific error are that a new attempt was made to sync when a previous attempt was not finished. That is the 'locked' error.

However, it was also advised that you share the last 5 log errors to get more information on this. Please be sure to add [SUMO Issue] to the title of your new bug in bugzilla.mozilla.org as well as a link to this thread for a smooth handoff between support and the Firefox Sync experts.

Let me know if there are any hickups in this handoff. You are in good hands.