Hello,
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.
If MaxCrashReportsSize is not reached and crashes are still deleted
it is probably a bug. What OS (distro and version) are you using?
Two probably unrelated questions:
1. I know that the "firefox" package is signed with a proper key, but I
installed it from command line after manually downloading it from koji. Abrt
throws away this crash and logs:
Dez 13 21:13:14 hostname abrt-hook-ccpp[3199]: Process 30672 (firefox) of
user 1000 killed by SIGSEGV - dumping core
Dez 13 21:13:15 hostname abrt-hook-ccpp[3199]: Failed to create
core_backtrace: PTRACE_SEIZE (tid 30766) failed: Operation not permitted
Dez 13 21:13:15 hostname abrt-server[3202]: Package 'firefox' isn't signed
with proper key
Dez 13 21:13:15 hostname abrt-server[3202]: 'post-create' on
'/var/spool/abrt/ccpp-2016-12-13-21:13:14-30672' exited with 1
Dez 13 21:13:15 hostname abrt-server[3202]: Deleting problem directory
'/var/spool/abrt/ccpp-2016-12-13-21:13:14-30672'
What am I doing wrong?
If you install packages manually from koji, package are not signed and you have to
set 'OpenGPGCheck' option to 'yes' in
/etc/abrt/abrt-action-save-package-data.conf
to catch such a crashes.
Because of abrt deleting my crashes, I get these a lot:
"ignoring (repeated
crash)". How can I reset abrt's behavior about crashes it has seen before?
Removing /var/spool/abrt/last-ccpp file should help.
Matej