Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
In '/etc/cron.hourly/mcelog.cron', it looks like the intent is to first check if mcelog is supported and only proceed if so. However, I do not believe the check is being done correctly. The check is:
# is mcelog supported?
/usr/sbin/mcelog --supported >& /dev/null
if [ $? -eq 1 ]; then
exit 1;
fi
But according to mcelog(8), 'mcelog --supported' returns 1 if supported and 0 otherwise. So the script continues only if the system does not have processors which support MCE, which seems backwards.
Version-Release number of selected component (if applicable):
mcelog-1.0pre3_20110718-0.14.el6.x86_64
How reproducible:
On a system that does not support MCE, this issue should lead to hourly cron emails containing 'mcelog' errors.
Steps to Reproduce:
1. Verify that the system does not support MCE:
mcelog --supported ; echo "Supported: $?"
2. Run 'mcelog.cron':
/etc/cron.hourly/mcelog.cron
Actual results:
Supported: 0
mcelog: Cannot find SMBIOS DMI tables
Expected results:
Supported: 0
Description of problem: In '/etc/cron.hourly/mcelog.cron', it looks like the intent is to first check if mcelog is supported and only proceed if so. However, I do not believe the check is being done correctly. The check is: # is mcelog supported? /usr/sbin/mcelog --supported >& /dev/null if [ $? -eq 1 ]; then exit 1; fi But according to mcelog(8), 'mcelog --supported' returns 1 if supported and 0 otherwise. So the script continues only if the system does not have processors which support MCE, which seems backwards. Version-Release number of selected component (if applicable): mcelog-1.0pre3_20110718-0.14.el6.x86_64 How reproducible: On a system that does not support MCE, this issue should lead to hourly cron emails containing 'mcelog' errors. Steps to Reproduce: 1. Verify that the system does not support MCE: mcelog --supported ; echo "Supported: $?" 2. Run 'mcelog.cron': /etc/cron.hourly/mcelog.cron Actual results: Supported: 0 mcelog: Cannot find SMBIOS DMI tables Expected results: Supported: 0