Fedup'ing from F18 to F19 and then to F20, I've noticed that abrt doesn't like its very own older reports -- in my case because of missing time file while also no .lock locking mechanism is activated (likely to prevent race-conditions due to abrt's asynchronicity). IIRC I have already talked with Jakub about the intended workflow vs. user deliberate workflow (like preserving the incidents on purpose) in connection to [bug 1032636]. This is an extension of preserving the incidents across Fedora releases span. Either abrt should be prepared to live with older reports, or there should be one-off indication + blacklisting the now-unsupported incidents, i.e., it should be prevented that messages like this are generated over and over to the logs (under some circumstances, 10 times in row within the same moment): > abrtd[446]: Missing file: time > abrtd[446]: Unlocked '/var/tmp/abrt/ccpp-2013-10-08-18:37:40-10260/.lock' > (no or corrupted 'time' file) Happened to me in both F19 (abrt-2.1.10-1.fc19.x86_64) and F20 (abrt-2.1.10-1.fc20.x86_64).
Ah, so the reported dirs seem to be completely empty for some reason, not sure now. Anyway, having some kind of automatic blacklisting a/o conditionally trashing of apparently stale incident dirs would be a good improvement in such situation, rather than continually and verbosely jumping over it.
Thank you for the report. ABRT always required time file, so there is no compatibility issue. The problem here is that some tmp-files-cleaner has cleared contents of your dump directories and left the empty directories in the dump location. Removing of the empty directories from '/var/tmp/abrt' should help in this case. From ABRT's point of view, the best solution in this case is to prevent the tmp-files-cleaner from deleting files from the crash directories.
Similar happened to me, in my case I am trying to debug a locally built polipo package. This worked fine till a recent update - suddenly abrt changed behavior to immediately delete the crash report dir because GPG did not match. I have now added "OpenGPGCheck = no" to someplace /etc/abrt which seems to help. Other things go wrong though.. # ll /var/tmp/abrt total 3196 -rw-------. 1 root root 11952128 Mar 16 11:19 abrt-applet-coredump drwxrwx---. 2 rz abrt 4096 Mar 19 21:18 ccpp-2014-02-18-14:59:59-30525 drwxrwx---. 2 rz abrt 4096 Mar 19 21:18 ccpp-2014-03-19-17:41:10-28059 -rw-------. 1 root root 15 Mar 19 21:18 last-ccpp -rw-------. 1 root root 19 Dec 17 23:43 last-via-server BUT - I was expecting to find the crash from 21:18:35 somewhere. What happened?? In my case it does not appear there was no tmpcleaner at work, happened me earlier but this looked differently. ccpp-2014-02-18-14:59:59-30525 was empty but that should not break the later report? logile: Mar 19 21:18:34 localhost kernel: [98287.782404] polipo[29054]: segfault at bf6e6ffc ip 0804e3b3 sp bf6e7000 error 6 in polipo[8048000+2e000] Mar 19 21:18:35 localhost abrt-hook-ccpp[29791]: Saved core dump of pid 29054 (/usr/bin/polipo) to /var/tmp/abrt/ccpp-2014-03-19-21:18:35-29054 (9846784 bytes) Mar 19 21:18:36 localhost systemd[1]: polipo.service: main process exited, code=dumped, status=11/SEGV Mar 19 21:18:36 localhost systemd[1]: Unit polipo.service entered failed state. Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525' is not a problem directory Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:36 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:36 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525' is not a problem directory Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: Missing file: time Mar 19 21:18:37 localhost abrt-server[29793]: Unlocked '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525/.lock' (no or corrupted 'time' file) Mar 19 21:18:37 localhost abrt-server[29793]: '/var/tmp/abrt/ccpp-2014-02-18-14:59:59-30525' is not a problem directory Mar 19 21:18:37 localhost abrt-server[29793]: Generating core_backtrace Mar 19 21:18:37 localhost abrt-server[29793]: Generating backtrace Mar 19 21:18:39 localhost abrt-server[29793]: journalctl: unrecognized option '--system' Mar 19 21:18:39 localhost abrt-server[29793]: Duplicate: core backtrace Mar 19 21:18:39 localhost abrt-server[29793]: DUP_OF_DIR: /var/tmp/abrt/ccpp-2014-03-19-17:41:10-28059 Mar 19 21:18:39 localhost abrt-server[29793]: Deleting problem directory ccpp-2014-03-19-21:18:35-29054 (dup of ccpp-2014-03-19-17:41:10-28059) Mar 19 21:18:40 localhost dbus-daemon[915]: dbus[915]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Mar 19 21:18:40 localhost dbus[915]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Mar 19 21:18:40 localhost dbus-daemon[915]: dbus[915]: [system] Successfully activated service 'org.freedesktop.problems' Mar 19 21:18:40 localhost dbus[915]: [system] Successfully activated service 'org.freedesktop.problems'
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I still have the issue on fedora 26