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

Issue 763516 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

crash_reporter should include failure reasons in its log messages

Project Member Reported by teravest@chromium.org, Sep 8 2017

Issue description

From crbug.com/760337:

017-09-07T14:28:54.770878+08:00 ERR crash_reporter[1812]: Could not get active user sessions, using default.
2017-09-07T14:28:54.794204+08:00 ERR crash_reporter[1812]: Failed to gzip /home/chronos/crash/chrome.20170907.142854.1721.chrome.txt
2017-09-07T14:28:54.807593+08:00 ERR crash_reporter[1812]: Unable to write /home/chronos/crash/chrome.20170907.142854.1721.meta

We lose the crash data in this case :( We should write the reason for the failed writes to help with debugging these.

 
just to be clear, you mean "we should include the failure reason in the log message" :) ?  i think we lost the data there because the user's home dir has failed/gone away, so if that's the case, there's no safe location for us to write out the crash report.  the system spool dir is only for system crashes and we don't want to place any user crashes there.
Summary: crash_reporter should include failure reasons in its log messages (was: crash_reporter should log error code on I/O failures.)
> just to be clear, you mean "we should include the failure reason in the log message" :) ? 

Yes, that would have been a better title :)

Peeking at the crash_reporter source, it looks like /home/chronos/crash is used as a fallback when there's no active user, and I thought that /home/chronos should exist regardless.

It looks like you wrote that fallback logic, though, so I trust your analysis ;)
Status: Assigned (was: Available)

Comment 4 Deleted

Sign in to add a comment