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.
Bug 1132510 - Need more correct cleanup behaviour when /var/spool/abrt is full
Summary: Need more correct cleanup behaviour when /var/spool/abrt is full
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: abrt
Version: 6.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: abrt
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 1132459
Blocks: 1075802 1172231 1269194
TreeView+ depends on / blocked
 
Reported: 2014-08-21 13:26 UTC by Konstantin Lepikhov
Modified: 2020-02-14 17:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1132459
Environment:
Last Closed: 2017-05-18 18:59:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Konstantin Lepikhov 2014-08-21 13:26:27 UTC 
+++ This bug was initially created as a clone of Bug #1132459 +++

Description of problem:
The original description taken from #sfdc case 01176977

----
Aug 19 11:25:22 el1191 abrtd: Directory 'ccpp-2014-08-19-11:25:19-2206' creation detected
Aug 19 11:25:22 el1191 abrtd: Size of '/var/spool/abrt' >= 1000 MB, deleting 'ccpp-2014-08-19-11:24:35-56940'
Aug 19 11:25:22 el1191 abrt[4235]: /var/spool/abrt is 1348804852 bytes (more than 1279MiB), deleting 'ccpp-2014-08-19-11:24:35-56940'
----

I can imagine that when abrtd is removing directories because the size goes over a specific treshold, but at the same time abrt processes are working with files/directories, the abrt scripts fail at different locations depending on specific timing issues.

So I do understand that there is a mechanism to prevent the filesystem to get full, but I think the abrt python scripts should not generated unhandled exceptions causing new crashes. It might be as simple as catching these specific exceptions, and logging the event to syslog before exiting with an error and error message.

All in all that wouldn't be a dramatic change to what is happening on right now, with the added value that these events are being logged and no new crashes are being initiated.

Version-Release number of selected component (if applicable):
abrt-2.0.8-21.el6.x86_64
abrt-addon-ccpp-2.0.8-21.el6.x86_64
abrt-addon-kerneloops-2.0.8-21.el6.x86_64
abrt-addon-python-2.0.8-21.el6.x86_64
abrt-cli-2.0.8-21.el6.x86_64
abrt-libs-2.0.8-21.el6.x86_64
abrt-tui-2.0.8-21.el6.x86_64

How reproducible:
Always, when size of /var/spool/abrt directory is bigger than predefined threshold.

Steps to Reproduce:
1. Create so many crashes that dir size will be bigger than predefined threshold.
2. Try to crash app again.

Actual results:
The abrt process will try to delete actual crashdump directory and run sosreport at the same time.

Expected results:
If we need a cleanup for that directory just delete oldest crasdump, not the latest one.
Comment 4 Chris Williams 2017-05-18 18:59:10 UTC 
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not appear to meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com
Note You need to log in before you can comment on or make changes to this bug.