Weave does not synchronize

RESOLVED FIXED

Status

Cloud Services
General
--
major
RESOLVED FIXED
11 years ago
7 years ago

People

(Reporter: dominique.gonzalez, Assigned: thunder)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9b2) Gecko/2007121016 Firefox/3.0b2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9b2) Gecko/2007121016 Firefox/3.0b2

I tried it with two computers.
No synchrozination seems to be done.

Reproducible: Always

Steps to Reproduce:
Connect or click on "sync now" button in the preference window.
Actual Results:  
Here is the log:

2007-12-27 04:46:53	Service.SnapStore	INFO	Read saved snapshot from disk
2007-12-27 04:46:53	Service.HistEngine	INFO	Beginning sync
2007-12-27 04:46:53	Service.DAV	INFO	Acquiring lock
2007-12-27 04:46:54	Service.DAV	INFO	Lock acquired
2007-12-27 04:46:54	Service.HistEngine	INFO	Lock acquired
2007-12-27 04:46:56	Service.HistEngine	INFO	Got status file from server
2007-12-27 04:46:56	Service.HistEngine	INFO	Downloading server deltas
2007-12-27 04:46:56	Service.HistEngine	ERROR	Exception caught: illegal character
2007-12-27 04:46:56	Service.HistEngine	INFO	Local snapshot version: 0
2007-12-27 04:46:56	Service.HistEngine	INFO	Server status: -1
2007-12-27 04:46:56	Service.HistEngine	INFO	Server maxVersion: null
2007-12-27 04:46:56	Service.HistEngine	INFO	Server snapVersion: null
2007-12-27 04:46:56	Service.HistEngine	FATAL	Sync error: could not get server status, or initial upload failed.  Aborting sync.
2007-12-27 04:46:56	Service.DAV	INFO	Releasing lock
2007-12-27 04:46:57	Service.DAV	INFO	Lock released (or we didn't have one)
(Assignee)

Comment 1

11 years ago
Do you have anything more in the verbose log around this line?

2007-12-27 04:46:56     Service.HistEngine      ERROR   Exception caught:
illegal character
(Reporter)

Comment 2

11 years ago
Here is all which happened at 04:46:56 (verbose log)

2007-12-27 04:46:56	Service.EventHandler	DEBUG	Handling event load
2007-12-27 04:46:56	Service.HistEngine	INFO	Got status file from server
2007-12-27 04:46:56	Service.HistEngine	INFO	Downloading server deltas
2007-12-27 04:46:56	Service.DAV	DEBUG	Creating GET request for https://services.mozilla.com/user/eb30daddba55f9f1d15be8a057427601d547c738/user-data/history/deltas.json
2007-12-27 04:46:56	Service.DAV	DEBUG	HTTP Header Authorization: ***** (suppressed)
2007-12-27 04:46:56	Service.DAV	DEBUG	HTTP Header Content-type: text/plain
2007-12-27 04:46:56	Service.DAV	DEBUG	HTTP Header If: <https://services.mozilla.com/user/eb30daddba55f9f1d15be8a057427601d547c738/> (<opaquelocktoken:2fcb802b-61a7-4d60-aec2-bbcf0d9fba76>)
2007-12-27 04:46:56	Service.EventHandler	DEBUG	Handling event load
2007-12-27 04:46:56	Service.Crypto	DEBUG	Decrypting data
2007-12-27 04:46:56	Service.Crypto	DEBUG	Done decrypting data
2007-12-27 04:46:56	Service.HistEngine	ERROR	Exception caught: illegal character
2007-12-27 04:46:56	Service.HistEngine	INFO	Local snapshot version: 0
2007-12-27 04:46:56	Service.HistEngine	INFO	Server status: -1
2007-12-27 04:46:56	Service.HistEngine	INFO	Server maxVersion: null
2007-12-27 04:46:56	Service.HistEngine	INFO	Server snapVersion: null
2007-12-27 04:46:56	Service.HistEngine	FATAL	Sync error: could not get server status, or initial upload failed.  Aborting sync.
2007-12-27 04:46:56	Service.DAV	INFO	Releasing lock
2007-12-27 04:46:56	Service.DAV	DEBUG	Creating UNLOCK request for https://services.mozilla.com/user/eb30daddba55f9f1d15be8a057427601d547c738/
2007-12-27 04:46:56	Service.DAV	DEBUG	HTTP Header Lock-Token: <opaquelocktoken:2fcb802b-61a7-4d60-aec2-bbcf0d9fba76>
2007-12-27 04:46:56	Service.DAV	DEBUG	HTTP Header Authorization: ***** (suppressed)
2007-12-27 04:46:56	Service.DAV	DEBUG	HTTP Header Content-type: text/plain
2007-12-27 04:46:56	Service.DAV	DEBUG	HTTP Header If: <https://services.mozilla.com/user/eb30daddba55f9f1d15be8a057427601d547c738/> (<opaquelocktoken:2fcb802b-61a7-4d60-aec2-bbcf0d9fba76>)
2007-12-27 04:46:57	Service.EventHandler	DEBUG	Handling event load
(Assignee)

Comment 3

11 years ago
Thanks.  My guess: you synced data up with one passphrase, but are trying to decrypt it now with a different one.

If you aren't sure what passphrase you used, try this on *both* computers:

1) Go to the weave prefs and then the advanced pane.
2) Delete the login information and the server data (but be careful not to delete the local data).
3) Restart Firefox.
4) Try to log in, that should take you through the setup wizard.  Make 100% sure you are using the same encryption passphrase on both computers.

If I'm right, the above should work.  In that case the real bug is that Weave has no safeguards against typing in an incorrect passphrase (!).
Assignee: nobody → thunder
(Assignee)

Updated

11 years ago
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
(Reporter)

Comment 4

11 years ago
Funny! But it is not an incorrect passphrase "bug".
I was sure that I did no mistake, but I made the test with a simpler passphrase.

With the same result.

Comment 5

11 years ago
I have the same problem. The passphrase is 100% correct, I tried multiple times.

Initial data transfer works fine, but each successive sync fails with above error.

My log looks pretty much the same, the "invalid character" error appears right after "done decrypting data".

This happens on a Vista machine as well as on an Ubuntu 7.10 machine.
(Reporter)

Comment 6

11 years ago
It should not be possible that it could have relation with it (but when all the possible solutions have been investigated without result the answer must lie with the impossible --Sherlock Holmes--) : I am one of those who were not able to get a verification email (I got it after 3 days).

maybe it can help? maybe not?

Comment 7

11 years ago
I got my verification email the very instant I registered. I doubt any connection to this bug...
(Assignee)

Comment 8

11 years ago
Created attachment 294794 [details] [diff] [review]
Don't decrypt cleartext

Bug found.  Attached one-liner patch should fix the problem.
I'll make another release soon.
(Assignee)

Comment 9

11 years ago
I just released 0.1.13 with this fix.  Go to Tools -> Add-ons -> Right-click on Weave -> Find update, and restart Firefox.  It should sync correctly now.

Reopen the bug if not.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED

Comment 10

11 years ago
Works flawlessly for me now. Thanks Dan!
(Assignee)

Comment 11

11 years ago
You're welcome! :-)
(Reporter)

Comment 12

11 years ago
It seems to work fine for me.
THANKS !!!

Updated

9 years ago
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
QA Contact: weave → general

Comment 13

7 years ago
What is weave?
Weave was the old codename for what is now called "Firefox Sync".

(This bug is long-closed; please don't post questions (or followup issues) here.  If you're experiencing issues with Weave aka Sync, file a new bug for them.)
You need to log in before you can comment on or make changes to this bug.