can't sync anything on my Chrome book |
||||||
Issue descriptionChrome Version: 66.0.3359.137 (0) stable OS: ChromeOS What steps will reproduce the problem? (1) I powerwashed a corporate chromebook. (2) Reenroll it to the domain, sign in to the corporate account. (3) Sign out and create a second account (personal) What is the expected result? Everything is synced. What happens instead? Sync doesn't start whatever I try. At the same time I'm signed in to Google and Chrome. I attached chrome://sync-internals/ screenshot but I don't see more info than SYNC_AUTH_ERROR. Another interesting behavior is that when I go to the settings, Sync doesn't show any error. When I click on it the window with Sync details shows up for 0.5 sec and disappears immediately. chrome://settings/syncSetup redirects me to chrome://settings/people. I just took my another device and also see an error on chrome://sync-internals/. Seems to be a server problem.
,
Apr 30 2018
No, sync is broken on absolutely every instance of Chrome I have for this account. In events I see a lot of
{
"details": "Received error: SYNC_SERVER_ERROR",
"proto": {},
"time": 1525078684884.735,
"type": "GetUpdates Response"
}
The protocol log doesn't output anything useful with the checkbox on:
4/30/2018, 11:28:04 AM Normal GetUpdate request
Nudged types: Bookmarks, Typed URLs, Sessions, Favicon Images, Favicon Tracking, Device Info, User Events
<big json here>
4/30/2018, 11:28:05 AM GetUpdates Response
Received error: SYNC_SERVER_ERROR
{}
,
Apr 30 2018
+sfiera for server knowledge: Any ideas what might cause the server to consistently return errors for a given account? Or how to further debug this?
,
Apr 30 2018
It’s the second report I’ve seen. I filed an internal bug with one theory. In the previous report, a sync reset didn’t help immediately, but the account eventually unwedged itself the next day. If it wouldn’t be too much trouble, it would be good if you can hold of on resetting for a couple days, to confirm that the issue really is transient.
,
Apr 30 2018
I can wait. I noticed this error on Friday though. Maybe it had existed for a long time as there is no UI indication of the problem.
,
May 2 2018
The Sync went live yesterday magically.
,
May 2 2018
Bug 838323 looks similar
,
May 4 2018
Closing because not reproducible anymore.
,
May 4 2018
Not so fast. It's yellow again on my Linux Chrome beta 67.0.3396.30, server error since Friday, May 4, 2018 at 1:10:57 PM. But green on my Android (stable channel).
,
May 4 2018
Yellow and "backed off"? If so, I'd consider this a dupe of bug 838323.
,
May 4 2018
Yes, "Backed off"
,
May 4 2018
Alright, then let's continue the investigation on bug 838323. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by treib@chromium.org
, Apr 30 2018Owner: treib@chromium.org
Status: Assigned (was: Untriaged)