New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 604434 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Unrelated network issues manifest as several strange problems related to Sync

Project Member Reported by agoode@chromium.org, Apr 18 2016

Issue description

Version 50.0.2661.79 beta (64-bit)
Platform 7978.57.0 (Official Build) beta-channel samus
Firmware Google_Samus.6300.174.0

What steps will reproduce the problem?
(1) Be on a router with flaky connections to clients4.google.com
(2) Try to sync (especially first time sync)

What is the expected output?
The errors should surface as meaningful, transient errors. The system should retry automatically. Sync should not be disconnected.

What do you see instead?
Several problems:
- The user is given no notice that sync is having problems. This was especially devastating since I just did a powerwash.
- Sync is disabled and must be manually restarted. 
- Various wrong explanations of the behavior: "stopped by Google Dashboard" on the settings screen, "AUTH ERROR" on sync-internals, "Failed to start up the sync backend" on the settings screen. Messages seemed to suggest authentication problems, which was not true.

 
Cc: jnaveen@chromium.org plaree@chromium.org
Can you clarify the scenario a bit? My understanding is that you just did a full wipe of a Chromebook, signed in, and are having problems syncing.

You mentioned two different messages on the settings screen; can you clarify where those were? The AUTH_ERROR on sync-internals may be unrelated, but there might have been a real problem getting auth tokens for your account. Why do you think that could not have been the case?

Comment 2 by agoode@chromium.org, Apr 20 2016

I am pretty sure there were no auth issues on the account. It all came down to DNS failing to resolve clients4.google.com. Once I solved my DNS problems, everything started working perfectly.

If you purposely break DNS in the same way, causing clients4.google.com to not resolve, you might see similar problems.
I could not reproduce the issue either.
I have tried signing in to sync after a powerwash and I could be able to successfully sign in without any errors and the sync internals page too does not have any errors.
I have also tried reimaging the device with the latest chromeos and then sign in to sync build. Still haven't seen any errors and sync internals looks healthy.
Could this be some intermittent issue?

Comment 4 by agoode@chromium.org, Apr 25 2016

Correct, it is an intermittent issue. The problem is that when this issue occurs, the system provides misleading diagnostics.

You should be able reproduce this network issue by changing your DNS or firewall configuration to block traffic to clients4.google.com. Once you do this, you'll see the problems as described above.

Comment 5 by gangwu@chromium.org, Apr 27 2016

Owner: maxbogue@chromium.org

Comment 6 by s...@chromium.org, May 4 2016

Status: Assigned (was: Untriaged)
Labels: Hotlist-Polish
Owner: ----
Status: Available (was: Assigned)

Comment 9 by s...@chromium.org, Jan 17 2018

Status: Archived (was: Available)

Sign in to add a comment