Closed Bug 1595311 Opened 5 years ago Closed 5 years ago

Firefox sync stopped syncing on multiple devices simultaneously

Categories

(Firefox :: Sync, defect)

70 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1595298

People

(Reporter: maxim.feinleb, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

  1. Sending Tabs across devices does not work any longer (Windows + Android)
  2. Sync now on Android will be executed but "Last synced" timestamp does not change
  3. After disconnect and reconnect to Sync with Windows and Android: on Windows: Synced Tabs is empty; on Android: Synced devices: 0 devices

Actual results:

Starting yesterday (2019-11-09) Firefox Sync stopped working. I first noticed the problem with my Firefox on Android (v68.2.0), but the same problem persists with Firefox v70.0.1 on Windows 10 and also Firefox v71.0b8 on Windows 10.
Tabs cannot be sent any longer across my devices (Sub-menu "Send Tab to device" is grayed-out and disabled on Windows; on Android sending Tabs had no effect i.e. didn't appear on other device)
All my devices are listed correctly under: Firefox Accounts > Devices & apps
Disconnecting from Sync and connecting again helper neither on Windows nor on Android
about:sync-log returns:
1573305059673 Sync.LogManager DEBUG Flushing file log
1573305059674 FirefoxAccounts TRACE not checking freshness of profile as it remains recent
1573305059687 Sync.LogManager DEBUG Log cleanup threshold time: 1572441059687
1573305059708 Sync.LogManager DEBUG Done deleting files.
1573305192169 FirefoxAccounts INFO Polling device commands.
1573305192169 Sync.Service DEBUG User-Agent: Firefox/70.0.1 (Windows NT 10.0; Win64; x64) FxSync/1.72.0.20191030021342.desktop
1573305192170 Sync.Service INFO Starting sync at 2019-11-09 14:13:12 in browser session e...j
1573305192170 Sync.Service DEBUG In sync: should login.
1573305192170 Sync.Service INFO User logged in successfully - verifying login.
1573305192172 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys
1573305192172 Sync.Status DEBUG Status.login: error.sync.reason.serverMaintenance => success.status_ok
1573305192172 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed
1573305192172 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok
1573305192177 Services.Common.RESTRequest DEBUG GET request to https://api.accounts.firefox.com/v1/account/device/commands?index=0
1573305193183 Sync.Resource DEBUG GET fail 503 https://sync-598-us-west-2.sync.services.mozilla.com/1.5/9...8/info/collections
1573305193183 Sync.Resource WARN GET request to https://sync-598-us-west-2.sync.services.mozilla.com/1.5/9...8/info/collections failed with status 503
1573305193183 Sync.Status DEBUG Status.login: success.status_ok => error.login.reason.server
1573305193184 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed
1573305193184 Sync.ErrorHandler DEBUG Got Retry-After: 3600
1573305193184 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance
1573305193184 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed
1573305193184 Sync.SyncScheduler DEBUG Got backoff notification: 3600000ms
1573305193184 Sync.SyncScheduler DEBUG Fuzzed minimum next sync: 1573308793184
1573305193185 Sync.ErrorHandler ERROR Sync encountered a login error
1573305193185 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score.
1573305193187 Sync.SyncScheduler DEBUG Next sync in 4037145.391576633 ms. (why=schedule)
1573305193190 Sync.Service DEBUG Exception calling WrappedLock: Error: Login failed: error.sync.reason.serverMaintenance(resource://services-sync/service.js:984:15) JS Stack trace: onNotify@service.js:984:15
1573305193190 Sync.Service DEBUG Not syncing: login returned false.

Expected results:

I would expect Sync to function as expected.
In case of server maintenance I would expect an official statement informing about the downtime.

Component: Untriaged → Sync

Can confirm this has been happening to me for the last 48 hours as well. Have the same 503 error messages for my account's designated sync server.

Same here. Looks like it's the same sync server you mentioned.

573351673341 Sync.Resource DEBUG GET fail 503 https://sync-598-us-west-2.sync.services.mozilla.com/1.5/92804540/storage/meta/global
1573351673341 Sync.Resource WARN GET request to https://sync-598-us-west-2.sync.services.mozilla.com/1.5/92804540/storage/meta/global failed with status 503
1573351673341 Sync.Service WARN Unable to get meta/global. Failing remote setup.
1573351673342 Sync.ErrorHandler DEBUG Got Retry-After: 3600
1573351673342 Sync.Status DEBUG Status.login: success.status_ok => error.sync.reason.serverMaintenance

I confirm I have the same issue with the server https://sync-598-us-west-2.sync.services.mozilla.com/ both on my Firefox Desktop 70.0.1 on macOS 10.14.6, my Firefox for Android 68.2.0 on Android 10, and Lockwise for Android 3.10 on Android 10 (right when I changed my phone haha).

Also this is happening on my Firefox Nightly (72) Firefox Beta (71) and Firefox 70 install on Windows 10 and Mac OS X Catalina and on my Android device.

Count me in:
1573410119722 Sync.Resource DEBUG GET fail 503 https://sync-598-us-west-2.sync.services.mozilla.com/[...]
1573410119723 Sync.Service WARN Unable to get meta/global. Failing remote setup.
1573410119723 Sync.ErrorHandler DEBUG Got Retry-After: 3600
1573410119723 Sync.Status DEBUG Status.login: success.login => error.sync.reason.serverMaintenance
1573410119723 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed

FF 70.0.1 64bit on Win7 and Win10 64bit

Propose to merge with https://bugzilla.mozilla.org/show_bug.cgi?id=1595298

Indeed, these all appear to be the same sync node, I'm going to go ahead and merge the two bugs. Thanks!

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.