Bug 1496303 - abrt should use journalctl mcelog.service instead of /var/log/mcelog
Summary: abrt should use journalctl mcelog.service instead of /var/log/mcelog
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Martin Kutlak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1170835 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-27 03:14 UTC by Anton Kochkov
Modified: 2019-01-18 12:15 UTC (History)
7 users (show)

Fixed In Version: abrt-2.11.1-2.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 04:34:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Anton Kochkov 2017-09-27 03:14:12 UTC
In case of MCE error abrt shows this:

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 on modern Fedora /var/log/mcelog doesn't exist, systemd/journalctl should be used to retrieve MCE log:

[root@localhost home]# journalctl -b -u mcelog.service
-- Logs begin at Sat 2017-07-29 23:59:17 CST, end at Wed 2017-09-27 11:09:18 CST. --
Sep 26 14:21:41 localhost.localdomain systemd[1]: Started Machine Check Exception Logging Daemon.
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: Hardware event. This is not a software error.
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: MCE 0
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: CPU 3 BANK 0 TSC e77a6aba9687
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: TIME 1506477739 Wed Sep 27 10:02:19 2017
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: MCG status:
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: MCi status:
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: Corrected error
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: Error enabled
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: MCA: Internal parity error
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: STATUS 90000040000f0005 MCGSTATUS 0
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: MCGCAP c09 APICID 6 SOCKETID 0
Sep 27 10:02:19 localhost.localdomain mcelog[1121]: CPUID Vendor Intel Family 6 Model 60
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: Hardware event. This is not a software error.
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: MCE 0
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: CPU 1 BANK 0 TSC f05bd52b9002
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: TIME 1506480458 Wed Sep 27 10:47:38 2017
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: MCG status:
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: MCi status:
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: Corrected error
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: Error enabled
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: MCA: Internal parity error
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: STATUS 90000040000f0005 MCGSTATUS 0
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: MCGCAP c09 APICID 2 SOCKETID 0
Sep 27 10:47:38 localhost.localdomain mcelog[1121]: CPUID Vendor Intel Family 6 Model 60
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: Hardware event. This is not a software error.
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: MCE 0
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: CPU 0 BANK 0 TSC f43863ad5608
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: TIME 1506481640 Wed Sep 27 11:07:20 2017
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: MCG status:
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: MCi status:
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: Corrected error
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: Error enabled
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: MCA: Internal parity error
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: STATUS 90000040000f0005 MCGSTATUS 0
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: MCGCAP c09 APICID 0 SOCKETID 0
Sep 27 11:07:20 localhost.localdomain mcelog[1121]: CPUID Vendor Intel Family 6 Model 60
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: Hardware event. This is not a software error.
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: MCE 0
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: CPU 0 BANK 0 TSC f439513b6c9f
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: TIME 1506481641 Wed Sep 27 11:07:21 2017
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: MCG status:
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: MCi status:
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: Corrected error
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: Error enabled
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: MCA: Internal parity error
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: STATUS 90000040000f0005 MCGSTATUS 0
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: MCGCAP c09 APICID 0 SOCKETID 0
Sep 27 11:07:21 localhost.localdomain mcelog[1121]: CPUID Vendor Intel Family 6 Model 60
[root@localhost home]#

Comment 1 Martin Kutlak 2018-10-25 12:58:57 UTC
Upstream PR: https://github.com/abrt/abrt/pull/1326

Comment 2 Ben Cotton 2018-11-27 13:56:57 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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.

Comment 3 Ben Cotton 2018-11-30 23:19:07 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.

Comment 4 Fedora Update System 2019-01-08 14:22:12 UTC
abrt-2.11.1-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b74a80dd86

Comment 5 Fedora Update System 2019-01-10 22:14:53 UTC
abrt-2.11.1-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b74a80dd86

Comment 6 Fedora Update System 2019-01-11 04:34:13 UTC
abrt-2.11.1-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Matej Marušák 2019-01-18 12:15:20 UTC
*** Bug 1170835 has been marked as a duplicate of this bug. ***


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