Bug 1476518 - abrt (or journald/coredumpctl) does not deal well with journal disk corruption
abrt (or journald/coredumpctl) does not deal well with journal disk corruption
Status: NEW
Product: Fedora
Classification: Fedora
Component: abrt (Show other bugs)
Unspecified Linux
unspecified Severity high
: ---
: ---
Assigned To: abrt
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-07-29 15:11 EDT by Robin Burchell
Modified: 2017-07-29 15:14 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
log extract of abrt looping around (4.40 KB, text/plain)
2017-07-29 15:11 EDT, Robin Burchell
no flags Details

  None (edit)
Description Robin Burchell 2017-07-29 15:11:53 EDT
Created attachment 1306364 [details]
log extract of abrt looping around

I recently had some laptop trouble which I had to hard-reboot from. This caused some disk corruption. When I got back after a restart, abrt started going crazy (see attachment).

I ended up having to wipe my journal (rm -rf /var/log/journal), restart systemd-journald, and abrt-everything to get things quiet again. Unfortunately, I don't have a copy for post-mortem purposes; I didn't think of that until *after* I was trying to stop it from reporting a few hundred crashes a minute.

My guess is that something did actually crash (which subsequently caused me to have to hard-reboot); this was logged in the journal in a corrupted form, and abrt (or some other piece of the puzzle) didn't manage to cope with that situation. Note that the line:

    Jul 29 21:00:28 adele abrt-dump-journal-oops[930]: abrt-dump-journal-oops: Found oopses: 6

... was repeated, always with the same 6 oopses count, further leading me to believe that something got "stuck".

Setting severity to high, because although I doubt this sort of situation occurs often, it's very difficult to recover from when it does happen.
Comment 1 Robin Burchell 2017-07-29 15:14:10 EDT
Note that I do still a bunch (422 to be exact) of repeated crash reports in the UI. If those would be of use somehow, I can provide them.

Note You need to log in before you can comment on or make changes to this bug.