Bug 692474 - ABRT2: Exceeded quota is not reported
Summary: ABRT2: Exceeded quota is not reported
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Denys Vlasenko
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 12:29 UTC by Vít Ondruch
Modified: 2011-09-29 23:26 UTC (History)
7 users (show)

Fixed In Version: abrt-2.0.3-4.fc15
Clone Of:
Environment:
Last Closed: 2011-09-29 23:26:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2011-03-31 12:29:06 UTC
Description of problem:
Exceeded quota is not reported

Steps to Reproduce:
1. MaxCrashReportsSize = 1 set in /etc/abrt/abrt.conf
2. Executed libreoffice writer
3. pkill -SIGSEGV swriter
  
Actual results:
Old bugs are removed, but exceeded quota is not reported

Expected results:
Exceeded quota will be reported.

Comment 1 Denys Vlasenko 2011-04-04 19:40:18 UTC
I tend to leave current behavior as-is.

The code which is responsible for trimming old dump directories runs in hooks, in particular, in coredump hook. Coredump hook is spawned by kernel. Any problem in coredump hook has a potential of creating a crash loop.

I hesitate to add dbus libraries and code to emit dbus signals to coredump hook.

If you feel strongly about it, please describe your rationale why trimming of old dumps *has to be* reported to the user.

Comment 2 Vít Ondruch 2011-04-05 08:04:44 UTC
The main reason is that it was part of the test case https://fedoraproject.org/wiki/QA:Testcase_ABRT_quota and therefore I expected to be by your specifications.

And of course it would be nice to be at least notified that something is going to be deleted. That is probably problem mainly because there is not clear ABRT workflow, i.e. the bug report lifetime. But that is probably different topic.

Comment 3 Denys Vlasenko 2011-07-17 09:52:03 UTC
This is caused by "silent" pruning of spool directory in ccpp hook. It prunes directory with treshold set to MaxCrashReportsSize * 1.25 to avoid stepping on abrtd's pruning (that one is done with unmodified MaxCrashReportsSize).

But if MaxCrashReportsSize is 1, then MaxCrashReportsSize * 1.25 is also 1.

The fix I committed uses (MaxCrashReportsSize * 1.25 | 63). That is, the limit is always at least 63 megabytes.

Fixed in git:

commit c20d967744f1dbbc7d747d8f5d50886f3aefe2bd
Author: Denys Vlasenko <dvlasenk>
Date:   Sun Jul 17 11:46:45 2011 +0200

    abrt-server/ccpp_hook: enlarge spool dir pruning threshold.

Comment 4 Fedora Update System 2011-09-05 15:01:01 UTC
abrt-2.0.3-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/abrt-2.0.3-2.fc15

Comment 5 Fedora Update System 2011-09-07 00:13:13 UTC
Package abrt-2.0.3-2.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.3-2.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/abrt-2.0.3-2.fc15
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2011-09-09 13:24:13 UTC
abrt-2.0.3-3.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/abrt-2.0.3-3.fc15

Comment 7 Fedora Update System 2011-09-13 16:01:54 UTC
abrt-2.0.3-4.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/abrt-2.0.3-4.fc15

Comment 8 Fedora Update System 2011-09-29 23:25:30 UTC
abrt-2.0.3-4.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.