Lately, I'm seeing a weird behavior of abrt happening over and over again:
Although I have just a few (say, 4) smaller crashes (not WebKit or Firefox), which take up little space on my disk, when a new crash happens, some or even all crashes are deleted. abrtd then reports to syslog: abrtd[896]: Size of '/var/spool/abrt' >= 25000 MB (MaxCrashReportsSize), deleting old directory 'ccpp-2016-12-…
This way, I never get more than 6 crashes listed by gnome-abrt or abrt-cli. Sometimes, abrt even deletes all my crash directories, including small python backtraces with just a few megabytes.
I don't understand why this happens. Can you please tell me? Is this a bug?
See /etc/abrt/abrt.conf: # Max size for crash storage [MiB] or 0 for unlimited # MaxCrashReportsSize = 1000
I don't understand.
In my /etc/abrt/abrt.conf, I've set
MaxCrashReportsSize = 25000
So no, the limit is not reached for sure if I get just 1…5 simple crashes. ABRT is just taking some hundred MiB on my disk, not 25 GiB.
Am Dienstag, den 20.12.2016, 11:07 +0100 schrieb Miroslav Suchý:
Lately, I'm seeing a weird behavior of abrt happening over and over again:
Although I have just a few (say, 4) smaller crashes (not WebKit or Firefox), which take up little space on my disk, when a new crash happens, some or even all crashes are deleted. abrtd then reports to syslog: abrtd[896]: Size of '/var/spool/abrt' >= 25000 MB (MaxCrashReportsSize), deleting old directory 'ccpp-2016-12-…
This way, I never get more than 6 crashes listed by gnome-abrt or abrt-cli. Sometimes, abrt even deletes all my crash directories, including small python backtraces with just a few megabytes.
I don't understand why this happens. Can you please tell me? Is this a bug?
See /etc/abrt/abrt.conf: # Max size for crash storage [MiB] or 0 for unlimited # MaxCrashReportsSize = 1000
crash-catcher@lists.fedorahosted.org