957415 - Nightly: Not able to consistently use FxA + Sync to sync various collections without sync errors.

Status: RESOLVED WORKSFORME

(Firefox :: Sync, defect)

Description

[James Bonacci [:jbonacci]]

I have installed the latest Nightly on Mac (and Win/Linux).
I have set identity.fxaccounts.enabled=true and restarted Nightly.
I have set the sync logs (Error/Success) so I can see the fruits of my labor.

Clicking "Sync Now" appears to do nothing. That is there is no apparent sync activity and nothing appears in the sync logs.
After waiting for 20 minutes or so, I click it again.
Eventually I see an error bar that sync failed. There is a button to sync again.
I was not able to capture the error bar before it went away.

At this point, I do get a sync. I can see success logs, but I also see an error log before the success logs. The error log contains most of the sync activity before the failures:
1389141381407	Sync.Service	DEBUG	User-Agent: Firefox/29.0a1 FxSync/1.31.0.20140107030202.
1389141381407	Sync.Service	INFO	Starting sync at 2014-01-07 16:36:21
1389141381407	Sync.Service	DEBUG	Exception: Could not acquire lock. Label: "service.js: sync". No traceback available

and then

1389141386421	Sync.Service	INFO	Starting sync at 2014-01-07 16:36:26
1389141386421	Sync.Service	DEBUG	Exception: Could not acquire lock. Label: "service.js: sync". No traceback available
1389141386421	Sync.Service	INFO	Cannot start sync: already syncing?

...etc...


It looks like sync is taking so long that a follow-up user-triggered sync (or a sync if changes are made to various collections) is causing errors.

Warrants more investigation.

Adding rfkelly in case this is related to our use of a single sync db awsbox in AWS (access/slowness/etc)...

Comment 1

[:Gavin Sharp [email: [e-mail]]]

Is this bug useful now? Lots has changed since this was filed.

Comment 2

[Tracy Walker [:tracy]]

this is WFM. Much has improved since this was reported, please reopen if able to repro with current sync client/server state.