Bug 952773

Summary:	abrt throttling not working
Product:	Red Hat Enterprise Linux 6	Reporter:	Harold Miller <hamiller>
Component:	abrt	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Zachar <lzachar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.3	CC:	dkutalek, dvlasenk, jfilak, jmoskovc, mmilata
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	abrt-2.0.8-18.el6	Doc Type:	Bug Fix
Doc Text:	Cause: abrt-watch-log and abrt-dump-oops are creating too many new problem directories when kernel error occurs periodically. Consequence: User is flooded with problem reports. Possibly overflowing /var partititon. Fix: abrt-dump-oops is changed to ignore all additional problems for a few minutes after it sees 5 or more of them. Result: User is not flooded with problem reports.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 09:31:05 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:

Description Harold Miller 2013-04-16 16:30:59 UTC

Description of problem:Customer ha d real error (soft-lockup) and abrt generated 8600 folders and 600+ emails to root@. There ought to be a time limit between creating crashes and a crash de-duplication mechanism - seems these are not working,

Version-Release number of selected component (if applicable):


How reproducible: 


Steps to Reproduce:
1.
2.
3.
  
Actual results: Many folders and emails created


Expected results: a more reasonable number of folders and emails, or a configuration option to allow us to select reports/10min


Additional info:

Comment 1 Martin Milata 2013-04-16 16:44:49 UTC

Based on an irc communication, it appears that this problem applies to kerneloops hook. Do our time-limiting & local deduplication mechanisms work with kerneloops problems?

Comment 3 Jakub Filak 2013-04-17 07:58:36 UTC

(In reply to comment #1)

Seems that ABRT tries to limit the number of reported kerneloops problems.

Upstream commit:

commit 6fc121f145354dd95bb588eb685f1593f5156ca0
Author: Denys Vlasenko <dvlasenk>
Date:   Tue Feb 5 17:32:43 2013 +0100

    abrt-dump-{oops,xorg}: limit amount of created dirs, add cooldown sleep if exceeded
    
    Signed-off-by: Denys Vlasenko <dvlasenk>

Comment 4 Denys Vlasenko 2013-06-14 10:44:01 UTC

abrt git, rhel6 branch commit:

commit 39b2415c9138664300232735b6ab83b99e39e341
Author: Denys Vlasenko <dvlasenk>
Date:   Wed Jun 12 14:33:21 2013 +0200

    abrt-dump-oops: limit amount of created dirs, add cooldown sleep if exceeded. rhbz#952773

    This is a partial backport of 6fc121f145354dd95bb588eb685f1593f5156ca0.

    Signed-off-by: Denys Vlasenko <dvlasenk>
    Signed-off-by: Jiri Moskovcak <jmoskovc>

Comment 7 errata-xmlrpc 2013-11-21 09:31:05 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.

http://rhn.redhat.com/errata/RHBA-2013-1586.html