If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Status

Cloud Services
General
5 years ago
5 years ago

People

(Reporter: andym, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
I can't pair a device. Log:

1348966753889	Sync.Service	DEBUG	Exception: Can't sync: Weave is disabled No traceback available
1348966753919	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1348966753929	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1348966754144	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1348966783334	Sync.JPAKEClient	ERROR	Keys don't match!
1348966783334	Sync.JPAKEClient	DEBUG	Aborting...
1348966783334	Sync.JPAKEClient	DEBUG	Reporting failure to server.
1348966802184	Sync.JPAKEClient	ERROR	Keys don't match!
1348966802184	Sync.JPAKEClient	DEBUG	Aborting...
1348966802184	Sync.JPAKEClient	DEBUG	Reporting failure to server.
1348966820306	Sync.JPAKEClient	ERROR	Keys don't match!
1348966820306	Sync.JPAKEClient	DEBUG	Aborting...
1348966820306	Sync.JPAKEClient	DEBUG	Reporting failure to server.
1348966848383	Sync.JPAKEClient	ERROR	Keys don't match!
1348966848383	Sync.JPAKEClient	DEBUG	Aborting...
1348966848383	Sync.JPAKEClient	DEBUG	Reporting failure to server.
1348966946755	Sync.Service	DEBUG	User-Agent: Firefox/18.0a1 FxSync/1.20.0.20120928030544.
1348966946755	Sync.Service	INFO	Starting sync at 2012-09-29 18:02:26
1348966946756	Sync.SyncScheduler	DEBUG	Clearing sync triggers and the global score.
1348966946756	Sync.Service	INFO	In sync().
1348966946756	Sync.Status	INFO	Resetting Status.
1348966946756	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1348966946757	Sync.SyncScheduler	DEBUG	Next sync in 86400000 ms.

This is on two updated Firefox nightlies. I've typed this in a few of times I'm sure I got it right at least once. Retried with a new account and no luck there either.
Bumping out of "Server" component since it's not clear which side the error is on, adding client devs for advice on this log.
Component: Server: Sync → General
Andy: this on Mac? Reminds me of a crypto problem. A full log from startup would help:

https://philikon.wordpress.com/2011/06/13/how-to-file-a-good-sync-bug/
You need to log in before you can comment on or make changes to this bug.