Created attachment 1474271 [details] journalctl content Description of problem: After a dnf update, rebooting the machine, I get: systemctl status abrt-oops.service ● abrt-oops.service - ABRT kernel log watcher Loaded: loaded (/usr/lib/systemd/system/abrt-oops.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-08-08 13:07:58 CEST; 54s ago Process: 1119 ExecStart=/usr/bin/abrt-dump-journal-oops -fxtD (code=exited, status=1/FAILURE) Main PID: 1119 (code=exited, status=1/FAILURE) Aug 08 13:07:57 mypc systemd[1]: Started ABRT kernel log watcher. Aug 08 13:07:58 mypc abrt-dump-journal-oops[1119]: abrt-dump-journal-oops: Cannot read journal data. Aug 08 13:07:58 mypc systemd[1]: abrt-oops.service: Main process exited, code=exited, status=1/FAILURE Aug 08 13:07:58 mypc systemd[1]: abrt-oops.service: Failed with result 'exit-code'. Version-Release number of selected component (if applicable): 4.18.0-0.rc7.git1.1.fc29.x86_64 #1 SMP Wed Aug 1 16:46:20 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux abrt-2.10.10-4.fc29.x86_64 abrt-addon-kerneloops-2.10.10-4.fc29.x86_64 In addition, during the boot process I see a lot of lines remembering me a core dump. See the attached file.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
The same problem on Fedora 28.
I have upgraded my workstation to Fedora 29. The problem persists.
The problem seems to be solved now. | systemctl status abrt-oops.service | ● abrt-oops.service - ABRT kernel log watcher | Loaded: loaded (/usr/lib/systemd/system/abrt-oops.service; enabled; vendor preset: enabled) | Active: active (running) since Thu 2019-05-16 10:25:02 CEST; 11min ago | Main PID: 1034 (abrt-dump-journ) | Tasks: 1 (limit: 4915) | Memory: 42.8M | CGroup: /system.slice/abrt-oops.service | └─1034 /usr/bin/abrt-dump-journal-oops -fxtD | rpm -q abrt | abrt-2.12.0-2.fc29.x86_64 | rpm -q abrt-addon-kerneloops | abrt-addon-kerneloops-2.12.0-2.fc29.x86_64
I my case it was an corrupt journal. After remove the corrupt journal files, the service will start.
(In reply to Frank Büttner from comment #6) > I my case it was an corrupt journal. > After remove the corrupt journal files, the service will start. Hello Frank, how did you remove the corrupt journal? The service fails on my machine even after rebooting, with the same error "Cannot read journal data".
Simple delete all files show as damaged by: journalctl --verify
(In reply to Frank Büttner from comment #8) > Simple delete all files show as damaged by: > journalctl --verify Thanks! That fixed the issue for me as well. There were a bunch of corrupt files.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.