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

Issue 888116 link

Starred by 1 user
Status: Duplicate
Merged: issue 884249
Owner:
vapier@chromium.org
Closed: Sep 21
Cc:
derat@chromium.org
█ jlklein@chromium.org
snanda@chromium.org
vapier@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

feedback report does not contain the client ID because Consent To Send Stats is missing

Project Member Reported by semenzato@chromium.org, Sep 21 
As shown in b/116256960, there may be a problem the interaction of feedback reports and /home/chronos/Consent To Send Stats.

The reporter of that bug was trying to access the client ID in a feedback report that was just sent, but the field contained "error: consent not given".  However, the "Automatically send diagnostics" switch was locked in the ON position by corp policy.

The error is consistent with a missing /home/chronos/Consent To Send Stats.  The message is produced by metrics_client, which is invoked by debugd when it collects feedback logs in log_tool.cc:

  { "CLIENT_ID", "/usr/bin/nsenter -t1 -m /usr/bin/metrics_client -i",
    kRoot,
    kDebugfsGroup,
  },

The question then is why was that file missing.

Comment 1 by semenzato@chromium.org, Sep 21 

Jeremy, can you take a look at chrome://crashes on that device?  Thanks!

Comment 2 by jlklein@chromium.org, Sep 21 

Sure, what am I looking for in the crashes page?

Comment 3 by semenzato@chromium.org, Sep 21 

#2: I think I am confused---it's probably not useful.  You wanted to find MORE crash reports with that client ID.  You probably already found the crash reports listed in chrome://crashes.  Sorry.

Comment 4 by semenzato@chromium.org, Sep 21 

Here's a theory (credits to Sameer).  There may be a race condition when Consent To Send Stats is first created.  In fact, almost certainly there is at least one race condition since creating the file and writing to it are separate operations.  So the file may not exist (even though the "send stats" policy is forced ON), or may exist and be empty.  The same error message is produced if the file is empty or has unexpected content.

Vovo has collected a number of feedback reports to extract OOM kill information.  I will ask him if he can check the client ID in all of them, to see if this is more common than we thought.

Comment 5 by vapier@chromium.org, Sep 21

Components: -OS>Systems>CrashReporting OS>Systems
what OS version are you looking at ?  is this just a dupe of  issue 884249  ?

Comment 6 Deleted

Comment 7 by jlklein@chromium.org, Sep 21 

Chrome version 70.0.3538.22 (Most recent dev channel)
CrOS Version 11021.19.0

Sounds like maybe it could be a dupe if that fix isn't in 70 yet.

Comment 8 by vapier@chromium.org, Sep 21

Mergedinto: 884249
Owner: vapier@chromium.org
Status: Duplicate (was: Untriaged)
the fix isn't in R70.  i'm waiting for a TPM to approve the merge still.

Comment 9 by semenzato@chromium.org, Sep 21 

Thanks.  My bad, I forgot to search crbug.
►

Sign in to add a comment