Closed
Bug 478565
Opened 15 years ago
Closed 15 years ago
Clients Engine Sync Error 0x80004005 (NS_ERROR_FAILURE)
Categories
(Cloud Services :: General, defect)
Cloud Services
General
Tracking
(Not tracked)
RESOLVED
FIXED
0.3
People
(Reporter: dw, Unassigned)
References
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.6) Gecko/2009020911 Ubuntu/8.10 (intrepid) Firefox/3.0.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.6) Gecko/2009020911 Ubuntu/8.10 (intrepid) Firefox/3.0.6 Client version: 0.2.100 Server version: 7c3a066d74d3 OS: Reproduced on Linux x86 and Vista 32bit After updating both my server and client, deleting all server side data, and initiating a first sync from a client, the process errors very early on throwing an error from the client engine, summarised here: 21:44 Engine.Clients INFO Applied 0 records, reconciled 0 records 2009-02-14 18:21:44 Engine.Clients DEBUG Preparing 2 outgoing records 2009-02-14 18:21:44 Engine.Clients WARN Sync failed 2009-02-14 18:21:44 Engine.Clients DEBUG Event: weave:clients-engine:sync:error 2009-02-14 18:21:44 Service.Main DEBUG Event: weave:service:sync:error 2009-02-14 18:21:44 Service.Main DEBUG Caught exception: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIJSON.decode] (JS frame :: file:///home/user/.mozilla/firefox/nsf1t1h9.default/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/modules/base_records/wbo.js :: WBORec_serialize :: line 123) Full log attached, and also the weave/meta/clients file as requested in this forum thread: https://labs.mozilla.com/forum/comments.php?DiscussionID=5074&page=1 Reproducible: Always Steps to Reproduce: 1. Update to latest server and client version 2. Clear all server data 3. Reset all lastsync values in order to initiate a first sync 4. Attempt sync
Reporter | ||
Comment 1•15 years ago
|
||
Reporter | ||
Comment 2•15 years ago
|
||
Comment 3•15 years ago
|
||
Thanks. That clients file is broken indeed!
Reporter | ||
Comment 4•15 years ago
|
||
Thanks Dan :) Out of curiosity, could you explain how it's broken? Should I delete the clients file(s) so I can get up and running again, or would you like me to leave it in place to test any fixes?
Updated•15 years ago
|
Attachment #362415 -
Attachment mime type: application/octet-stream → text/plain
Comment 5•15 years ago
|
||
Here's the clients file after running it through jsonlint.org (to format it): { "c3d88f13-337e-414b-a152-a5cb9cb60816": true, "1abfac95-96d1-40f4-8d54-8bcb2b835c2a": { "name": "Firefox", "type": "desktop" } } Each GUID corresponds to a client. Notice how one just says 'true'? That's wrong. You could try deleting the file and clearing the clients .lastSync pref
Updated•15 years ago
|
Reporter | ||
Comment 6•15 years ago
|
||
Thanks for the explanation :) Deleted the file on one machine, restarted Firefox and it's sync'ing again. Will get to my other clients over the next day or so and bring them all back online, will see if it trips up again. It must have happened at some point during the upgrade of the client and/or server, so the conditions have changed.
Comment 7•15 years ago
|
||
Let me know if you see it again. I think it's leftover from a previous version of the clients engine. I'm adding code that will clean it up on upgrade.
OS: Linux → All
Hardware: x86 → All
Comment 8•15 years ago
|
||
This is fixed now.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Component: Weave → General
Product: Mozilla Labs → Weave
Updated•15 years ago
|
QA Contact: weave → general
You need to log in
before you can comment on or make changes to this bug.
Description
•