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:
Limit the corefiles dumped in /var/spool/abrt to strictly 1GiB if we have "MaxCrashReportsSize = 1000" in `/etc/abrt/abrt.conf`.
Now, if we have a highly memory consuming application; it is likely to dump core to sometimes >10GiB which can fill up the /var filesystem.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6
abrt-2.0.8-34.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Kill a high memory consuming application, and capture coredump in /var/spool/abrt
2.
3.
Actual results:
Feb 8 17:26:52 scrbmrsdk000952 abrt[41162]: Saved core dump of pid 38022 (/home/test2/testapp) to /var/spool/abrt/ccpp-2016-02-08-17:26:45-38022 (4220542976 bytes)
Feb 8 17:26:52 scrbmrsdk000952 abrtd: Directory 'ccpp-2016-02-08-17:26:45-38022' creation detected
Feb 8 17:26:54 scrbmrsdk000952 abrt[41162]: /var/spool/abrt is 8445954791 bytes (more than 1279MiB), deleting 'ccpp-2016-02-08-17:11:14-36941'
Feb 8 17:26:56 scrbmrsdk000952 abrtd: '/var/spool/abrt/ccpp-2015-10-15-07:02:21-23191' is not a problem directory
Feb 8 17:26:56 scrbmrsdk000952 abrtd: '/var/spool/abrt/ccpp-2015-10-15-07:42:45-29774' is not a problem directory
Feb 8 17:26:57 scrbmrsdk000952 abrtd: '/var/spool/abrt/ccpp-2015-10-15-08:41:54-34553' is not a problem directory
Feb 8 17:26:57 scrbmrsdk000952 abrtd: '/var/spool/abrt/ccpp-2015-10-15-12:53:18-33797' is not a problem directory
Feb 8 19:06:52 scrbmrsdk000952 abrtd: Sending an email...
Feb 8 19:06:52 scrbmrsdk000952 abrtd: Email was sent to: root@localhost
Feb 9 06:32:57 scrbmrsdk000952 abrt[21717]: Not saving repeating crash in '/home/test2/testapp1'
Feb 9 06:32:58 scrbmrsdk000952 abrt[21718]: Saved core dump of pid 60878 (/home/test2/testapp1) to /var/spool/abrt/ccpp-2016-02-09-06:32:57-60878 (161607680 bytes)
Feb 9 06:32:58 scrbmrsdk000952 abrt[21718]: /var/spool/abrt is 4386930785 bytes (more than 1279MiB), deleting 'ccpp-2016-02-08-19:03:12-50067'
Feb 9 06:32:58 scrbmrsdk000952 abrtd: Directory 'ccpp-2016-02-09-06:32:57-60878' creation detected
Expected results:
Limit corefile sizes captured to MaxCrashReportsSize value. The problem directory need not be deleted.
Log in /var/log/mesaages that corefile is truncated. User can then blacklist if needed as in Bug #1208713
Additional info:
Please update abrt man pages for plugin configuration files such as 'CCpp.conf'.
It would be helpful if we can add a manpage for abrt-hook-ccpp and its functions.
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://rhn.redhat.com/errata/RHBA-2017-0768.html