Bug 1655241

Summary:	abrtd process consumes 100% of one core
Product:	Red Hat Enterprise Linux 7	Reporter:	Alan Matsuoka <alanm>
Component:	abrt	Assignee:	Martin Kutlak <mkutlak>
Status:	CLOSED ERRATA	QA Contact:	Martin Kyral <mkyral>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.6	CC:	amike, jaeshin, mkutlak, mkyral, msuchy, xingli
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	abrt-2.1.11-54.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-06 12:03:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1650622
Bug Blocks:

Description Alan Matsuoka 2018-12-01 19:52:46 UTC

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:

Comment 2 Miroslav Suchý 2018-12-03 12:56:28 UTC

This has already been resolved in upstream and has been resolved in RHEL8. See bug 1650622.
We can backport it to RHEL 7.

Comment 7 errata-xmlrpc 2019-08-06 12:03:28 UTC

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