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

Issue 641178 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 639822
Owner: ----
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Offline login blocked for 10 seconds on dmserver policy fetch

Project Member Reported by derat@chromium.org, Aug 25 2016

Issue description

Google Chrome	52.0.2743.116 (Official Build) (64-bit)
Platform	8350.68.0 (Official Build) stable-channel samus

I just saw a very slow (10+ seconds) offline login to my corp account on a corp-enrolled samus. It looks like we might block on a policy fetch before giving up. Maybe this is intentional, but it doesn't make sense to do it when the network interface isn't even configured (as was the case here).

----

[1812:1812:0825/165848:WARNING:device_management_service.cc(550)] Dmserver request failed, retrying in 10s.
[1812:1812:0825/165851:WARNING:device_management_service.cc(550)] Dmserver request failed, retrying in 20s.
[1812:1812:0825/165851:WARNING:device_management_service.cc(550)] Dmserver request failed, retrying in 20s.
[1812:1812:0825/165858:WARNING:user_cloud_policy_manager_chromeos.cc(409)] Timed out while waiting for the policy fetch. The session will start with the cached policy.
[1812:1812:0825/165858:VERBOSE1:input_events_blocker.cc(15)] InputEventsBlocker 0x2ce3192c8420 created.
[1812:1812:0825/165858:VERBOSE1:user_session_manager.cc(662)] RespectLocalePreference: app_locale='en-US', bkup_locale='en-US', account_locale - unused.  Selected 'en-US'
...
[1812:1812:0825/165859:VERBOSE1:user_session_manager.cc(1694)] Launching browser...
[1812:1812:0825/165859:WARNING:device_management_service.cc(550)] Dmserver request failed, retrying in 10s.
[1812:2260:0825/165859:ERROR:connection_factory_impl.cc(369)] Failed to connect to MCS endpoint with error -131
[1812:1812:0825/165859:VERBOSE1:input_events_blocker.cc(20)] InputEventsBlocker 0x2ce31fcb94e0 destroyed.
[1812:1812:0825/165908:VERBOSE1:oauth2_login_manager.cc(102)] OAuth2 refresh token is already loaded.
...
[1812:1812:0825/165910:VERBOSE1:user_image_manager_impl.cc(811)] Updating profile image for logged-in user.
[1812:1812:0825/165911:VERBOSE1:oauth2_login_verifier.cc(60)] MergeSession successful.
[1812:1812:0825/165911:VERBOSE1:oauth2_login_manager.cc(305)] OAuth2 refresh and/or GAIA token verification succeeded.
[1812:1812:0825/165912:VERBOSE1:oauth2_login_verifier.cc(74)] ListAccounts successful.
 
Cc: tnagel@chromium.org binzhao@chromium.org
Adding some more people.

Comment 2 by derat@chromium.org, Aug 28 2016

I just saw what looked like the same thing on the same device, but it was already connected to a network at the login screen this time. The user log is full of errors and warnings so it's a bit hard to tell what was to blame, but there are the same "Dmserver request failed, retrying in 10s." and "Timed out while waiting for the policy fetch. The session will start with the cached policy." warnings again.
chrome-slow-login.txt
14.1 KB View Download
Cc: atwilson@chromium.org
Can you try to ask someone else at google to log into this machine with his account (or use a test managed account with policy) to see if this issue is related to your account or any account on this machine.

Adding Drew as well he might have some clue about this.

This might be a dupe of  issue 639822  (which has recently been fixed AFAIU).
Yup, it's a dupe.
Mergedinto: 639822
Status: Duplicate (was: Untriaged)

Sign in to add a comment