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:
This appears to be the same problem as described in
https://bugzilla.redhat.com/show_bug.cgi?id=1416310
Version-Release number of selected component (if applicable):
abrt-2.1.11-52.el7.x86_64
How reproducible:
Hard to say. On Fedora
"
I still haven't found out how to reproduce the problem, but here are at least the symptoms:
- one single cpu core is suddenly consuming 100% of power, i notice because of the alarming fan swoosh
- check in the process list for the cause:
"/usr/sbin/abrtd -d -s" is the culprit
- do a
systemctl restart abrtd.service
and the thing is fixed
When an application related process aborts the abrtd process consumes 100% of a CPU core and remains at that utilization level until the daemon is restarted
This occurs after the app process receives a SIGABRT and has occurred 10 times since September 18 with no set pattern of occurrence.
# abrt-cli list|grep time
time: Sun 11 Nov 2018 09:52:09 PM CST
time: Wed 19 Sep 2018 01:31:33 PM CDT
time: Tue 06 Nov 2018 07:52:11 AM CST
time: Tue 06 Nov 2018 07:52:11 AM CST
time: Tue 06 Nov 2018 07:40:57 AM CST
time: Fri 21 Sep 2018 05:15:19 PM CDT
time: Thu 20 Sep 2018 08:41:25 PM CDT
time: Thu 20 Sep 2018 08:39:42 PM CDT
time: Thu 20 Sep 2018 08:30:51 PM CDT
time: Tue 18 Sep 2018 08:13:06 AM CDT
What information can you provide around timeframes and the business impact?
Last time of occurance: Wed 19 Sep 2018 01:31:33 PM CDT
This system is sized to meet the application requirements and with abrtd consuming 100% of a single CPU core it is impacting the applications ability to run reports in a timely manner.
Steps to Reproduce:
1. unknown
2.
3.
Actual results:
abrtd runs at 100% cpu
Expected results:
abrtd should not run at 100%
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2027