Description of problem: My CPU is overheating, causing ABRT to display machine check events. When I click the Details button on the problem report, then expand the Backtrace entry, I see the following message: The kernel log indicates that hardware errors were detected. The data was saved by kernel for processing by the mcelog tool. However, neither /var/log/mcelog nor system log contain mcelog messages. Most likely reason is that mcelog is not installed or not configured to be started during boot. Without this tool running, the binary data saved by kernel is of limited usefulness. (You can save this data anyway by running 'cat </dev/mcelog >FILE'). The recommended course of action is to install mcelog. If another hardware error would occur, a user-readable description of it will be saved in system log or /var/log/mcelog. But this message is bogus. I have a fresh install of Fedora Workstation. mcelog is installed and enabled by default, and I can see what went wrong with 'systemctl status mcelog'. Note that /var/log/mcelog does not exist; it's probably been replaced with the system journal. Version-Release number of selected component (if applicable): abrt-2.3.0-3.fc21 Actual results: ABRT claims mcelog is uninstalled or disabled Expected results: ABRT realizes that mcelog is installed and enabled. Even better if it can display the error message from the log.
Thank you for the report! abrt-action-check-oops-for-hw-error needs to be made aware of systemd-journald.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I'm seeing the same problem with abrt-2.7.0-2.fc23.x86_64. journalctl excerpt: Nov 17 16:55:13 localhost.localdomain mcelog[804]: CPU 2 THERMAL EVENT TSC 4f28e65ebf6 Nov 17 16:55:13 localhost.localdomain mcelog[804]: TIME 1447797085 Tue Nov 17 16:51:25 2015 Nov 17 16:55:13 localhost.localdomain mcelog[804]: Processor 2 below trip temperature. Throttling disabled Nov 17 16:55:13 localhost.localdomain mcelog[804]: STATUS 88010282 MCGSTATUS 0 Nov 17 16:55:13 localhost.localdomain mcelog[804]: MCGCAP c07 APICID 1 SOCKETID 0 Nov 17 16:55:13 localhost.localdomain mcelog[804]: CPUID Vendor Intel Family 6 Model 58 Nov 17 16:55:14 localhost.localdomain abrt-dump-journal-oops[859]: abrt-dump-journal-oops: Found oopses: 1 Nov 17 16:55:14 localhost.localdomain abrt-dump-journal-oops[859]: abrt-dump-journal-oops: Creating problem directories
*** Bug 1278420 has been marked as a duplicate of this bug. ***
Upstream issue: https://github.com/abrt/abrt/issues/942
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Still valid. Reopening.
Already fixed in abrt-2.11.1-2.fc29 *** This bug has been marked as a duplicate of bug 1496303 ***