Closed Bug 662627 Opened 15 years ago Closed 14 years ago

sync has stopped working on this computer

Categories

(Firefox :: Sync, defect)

Product:
Firefox
Component:
Sync
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: k0scist, Unassigned)

References

Details

Sync has stopped working on this computer, perhaps last week. It is a Firefox 4 release. The other two computers I use are on nightly and I also have an android Fennec which may or may not work (unsure). The other computers seem unaffected. Only this one is broken. Sync has an unknown error. Pasting the end of log - the whole log is too long for bugzilla (I recommend having automatic filing of these errors a la crashreporter since the logs are too long and the filing bug process is time-consuming and error prone, even assuming the user is generous enough to file) 1307478574903 Collection DEBUG JSON.parse JS Stack trace: deserialize("<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">")@record.js:94 < ()@record.js:812 < Channel_onDataAvail([object XPCWrappedNative_NoHelper],null,[object XPCWrappedNative_NoHelper],0,347)@resource.js:530 1307478574909 Service.Main DEBUG history failed: NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS JS Stack trace: Res_get()@resource.js:439 < SyncEngine__processIncoming()@engines.js:730 < SyncEngine__sync()@engines.js:966 < wrappedSync(null)@util.js:193 < batchedSync()@util.js:199 < WrappedNotify()@util.js:172 < Engine_sync()@engines.js:377 < WeaveSvc__syncEngine([object Object])@service.js:1913 < ()@service.js:1793 < WrappedNotify()@util.js:172 < WrappedLock()@util.js:140 < _lockedSync()@service.js:1695 < ()@service.js:1686 < WrappedCatch()@util.js:114 < sync()@service.js:1667 < (2)@browser.js:5320 1307478574912 Engine.Passwords INFO 0 outgoing items pre-reconciliation 1307478574913 Engine.Passwords INFO Records: 0 applied, 0 failed to apply, 0 reconciled. 1307478574917 Engine.Prefs INFO 0 outgoing items pre-reconciliation 1307478574959 Engine.Prefs WARN Error decrypting record: Record SHA256 HMAC mismatch: should be f9fa21260efd6c48f39aac590d0faa92088131f49e1e269bae28b7ef3ae48f7f, is 1ed89b5b728da3e22a0d79821d76eee320363dabede639674b6b09fcb919b2e6 No traceback available 1307478574961 Collection DEBUG GET success 200 https://phx-sync167.services.mozilla.com/1.0/jhammel/storage/prefs?full=1&ids=e2EyMzk4M2MwLWZkMGUtMTFkYy05NWZmLTA4MDAyMDBjOWE2Nn0= 1307478574962 Engine.Prefs DEBUG Records that failed to apply: e2EyMzk4M2MwLWZkMGUtMTFkYy05NWZmLTA4MDAyMDBjOWE2Nn0= 1307478574963 Service.Main DEBUG prefs failed to apply some records. 1307478574964 Engine.Prefs INFO Records: 0 applied, 1 failed to apply, 0 reconciled. 1307478575002 Service.Main DEBUG Exception: Some engines did not sync correctly No traceback available
(In reply to comment #0) > Only this one is broken. There are two problems here. Firstly, at some point during history sync, something went wrong -- either a crypto problem, or even something as trivial as a network issue at just the right moment. That has led to Bug 638301, which will be fixed in Firefox 5. Secondly, you've hit an HMAC error in the prefs engine. That means that somehow a record ended up on the server which either got corrupted, or was encrypted with the incorrect key. Neither of those things are supposed to happen. The most foolproof way to fix both of these issues is to change your Sync Key on one of your devices. (Prefs > Sync > My Sync Key > Generate.) You'll need to re-enter the key on your other devices. One way to do that is to deactivate the device's Sync account and go through the Easy Setup process again. If you're not keen on doing this, I can suggest individual steps in a terminal or Web Console to get things going again. > Pasting the end of log - the whole log is too long for bugzilla The best thing to do (which also avoids Bugzilla's wrapping nonsense) is to save the log to a file and use the "Add an attachment" link. > recommend having automatic filing of these errors a la crashreporter since > the logs are too long and the filing bug process is time-consuming and error > prone, even assuming the user is generous enough to file) It's on our (very long) list of things to do!
Blocks: 646269
FWIW, sync *seems* to be working again for me. It would be nice if there was some easy way to test this, but bookmarks, etc, seem to be going through to my several devices now.
Glad to hear it! Marking as FIXED.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
NOT fixed! Tried a new sync key and got the same original message.
(In reply to Robert from comment #4) > NOT fixed! Tried a new sync key and got the same original message. Robert: please file a new bug with logs for your issue. You're probably encountering a different problem. https://philikon.wordpress.com/2011/06/13/how-to-file-a-good-sync-bug/
Resolution: FIXED → WORKSFORME
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.