Description of problem:the computer iz freezing without any error reports services are crashing all over and ABRT dosent work Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: abrt-ccpp.service loaded active exited Install ABRT coredump hook ● abrt-oops.service loaded failed failed ABRT kernel log watcher abrt-xorg.service loaded active running ABRT Xorg log watcher abrtd.service loaded active running ABRT Automated Bug Reporting Tool [root@robert-localdomain rfairborther]# systemctl status abrt-oops ● 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 Sat 2017-03-18 19:08:54 CDT; 54min ago Process: 2627 ExecStart=/usr/bin/abrt-dump-journal-oops -fxtD (code=exited, status=1/FAILURE) Main PID: 2627 (code=exited, status=1/FAILURE) Mar 18 19:08:39 robert-localdomain systemd[1]: Started ABRT kernel log watcher. Mar 18 19:08:54 robert-localdomain abrt-dump-journal-oops[2627]: abrt-dump-journal-oops: Cannot read journal data. Mar 18 19:08:54 robert-localdomain systemd[1]: abrt-oops.service: Main process exited, code=exited, status=1/FAILURE Mar 18 19:08:54 robert-localdomain systemd[1]: abrt-oops.service: Unit entered failed state. Mar 18 19:08:54 robert-localdomain systemd[1]: abrt-oops.service: Failed with result 'exit-code'. Expected results: Additional info:
Created attachment 1264492 [details] problem report directory
Created attachment 1264493 [details] problem report directory
Created attachment 1264522 [details] problem report directory
Created attachment 1264523 [details] problem report directory f last-via-server
Created attachment 1264524 [details] problem report directory
Created attachment 1264525 [details] problem report directory
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
I see this on upgraded fedora 26, any workarounds?
I'm seeing this on my F26 too
I have this on F26 too. Is it a left-over from upgrades?
I have this problem on F27 after migrating from F26. Maybe it appeared earlier on F26 (after upgrading from F25), but I discovered it just now.
A fresh install of Fedora 27 shows the same issue: January 27, 2018 00:32 abrt-oops.service: Failed with result 'exit-code'. systemd 00:32 abrt-oops.service: Unit entered failed state. systemd 00:32 abrt-oops.service: Main process exited, code=exited, status=1/FAILURE systemd 00:32 abrt-dump-journal-oops: Cannot read journal data. abrt-dump-journal-oops 00:32 Started ABRT kernel log watcher. systemd January 26, 2018 Reboot 20:10 abrt-oops.service: Failed with result 'exit-code'. systemd 20:10 abrt-oops.service: Unit entered failed state. systemd 20:10 abrt-oops.service: Main process exited, code=exited, status=1/FAILURE systemd 20:10 abrt-dump-journal-oops: Cannot read journal data. abrt-dump-journal-oops 20:10 Started ABRT kernel log watcher. systemd (overview generated via the cockpit tool) did a restart of the abrt-oops service: Jan 27 09:28:58 thebeast systemd[1]: Started ABRT kernel log watcher. Jan 27 09:28:58 thebeast audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=abrt-oops comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 27 09:28:59 thebeast abrt-dump-journal-oops[6806]: abrt-dump-journal-oops: Cannot read journal data. Jan 27 09:28:59 thebeast systemd[1]: abrt-oops.service: Main process exited, code=exited, status=1/FAILURE Jan 27 09:28:59 thebeast systemd[1]: abrt-oops.service: Unit entered failed state. Jan 27 09:28:59 thebeast audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=abrt-oops comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Jan 27 09:28:59 thebeast systemd[1]: abrt-oops.service: Failed with result 'exit-code'. FYI I am running Fedora 27 (Linux 4.14.14-300.fc27.x86_64 #1 SMP Fri Jan 19 13:19:54 UTC 2018 x86_64 )
% sudo abrt-dump-journal-oops -v abrt-dump-journal-oops: Failed to read 'MESSAGE' field: Bad message abrt-dump-journal-oops: Cannot read journal data. This is due to a corrupted journal file, check with journalctl --verify: 586fe0: Invalid entry item (0/9 offset: 000000 586fe0: Invalid object contents: Bad message File corruption detected at /var/log/journal/24f49f7834f743dcbe3220166edd047/system~:586fe0 (of 8388608 bytes, 69%). FAIL: /var/log/journal/24f49f7834f743dcbe3220166edd047/system~ (Bad message) After deleting the corrupted journal file: % sudo abrt-dump-journal-oops -v abrt-dump-journal-oops: Found oopses: 10
ive noticed on one of my upgraded machines that watchdog isint stopping and when systemd or journald is killed with ABRT watchdog gives a connection refused error and the computer crashes and then i dont find any kerneloops bugs in gnome-abrt
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.
(In reply to Mike Gerber from comment #13) > % sudo abrt-dump-journal-oops -v > abrt-dump-journal-oops: Failed to read 'MESSAGE' field: Bad message > abrt-dump-journal-oops: Cannot read journal data. > > This is due to a corrupted journal file, check with journalctl --verify: > > > 586fe0: Invalid entry item (0/9 offset: 000000 > > 586fe0: Invalid object contents: Bad message > > File corruption detected at > /var/log/journal/24f49f7834f743dcbe3220166edd047/system@000564bb930a2cf3- > 80658c37fb73a5a0.journal~:586fe0 (of 8388608 bytes, 69%). > FAIL: > /var/log/journal/24f49f7834f743dcbe3220166edd047/system@000564bb930a2cf3- > 80658c37fb73a5a0.journal~ (Bad message) > > After deleting the corrupted journal file: > > % sudo abrt-dump-journal-oops -v > abrt-dump-journal-oops: Found oopses: 10 and to finish systemctl start abrt-oops.service Thank you for this comment , I had exactly same problem on F31 , the problem is the .journal~ file , which is a temporary file that wasn't delete on my computer crash on experiment wireless driver . So I think abrt-dump-journal-oops should not try read .journal~ files and that is the bug
It also affect Fedora 33. abrt-xorg.service - ABRT Xorg log watcher Loaded: loaded (/usr/lib/systemd/system/abrt-xorg.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2020-10-15 07:17:58 CEST; 3h 44min ago Main PID: 1446 (code=exited, status=1/FAILURE) CPU: 47ms Oct 15 07:17:57 knut systemd[1]: Started ABRT Xorg log watcher. Oct 15 07:17:58 knut abrt-dump-journal-xorg[1446]: abrt-dump-journal-xorg: Cannot read journal data. Oct 15 07:17:58 knut systemd[1]: abrt-xorg.service: Main process exited, code=exited, status=1/FAILURE Oct 15 07:17:58 knut systemd[1]: abrt-xorg.service: Failed with result 'exit-code'.
I can verify that removing the *.journal~ temporary files will make it possible to start abrt-oops.service again. This on a Fedora 33 installation, abrt-addon-kerneloops-2.14.5-1.fc33.x86_64
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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've just had the same problem on Fedora 34. Temporary (I assume) journal files that end in ~ are corrupt, causing abrt to fail. I assume that a hard system crash can corrupt the temporary files. They should either get removed by journald when it starts, or abrt-journald should ignore corrupt files if they're temporary. If neither of those are possible, abrt should show a "corrupt journal" gui popup like it does for other system failures, so that it can be fixed and statistics are known. 525008: Invalid object File corruption detected at /var/log/journal/6845e32ae4824400b195d57df1f1e652/system~:525008 (of 8388608 bytes, 64%). FAIL: /var/log/journal/6845e32ae4824400b195d57df1f1e652/system~ (Bad message) 305e98: ZSTD decompression failed: Bad message 305e98: Invalid object contents: Bad message File corruption detected at /var/log/journal/6845e32ae4824400b195d57df1f1e652/user-1000~:305e98 (of 8388608 bytes, 37%). FAIL: /var/log/journal/6845e32ae4824400b195d57df1f1e652/user-1000~ (Bad message)
RFE? .journal~ files should be ignored by abrt-dump-journal-oops? from man systemd-journald: "If the daemon is stopped uncleanly, or if the files are found to be corrupted, they are renamed using the ".journal~" suffix, and systemd-journald starts writing to a new file."
Same problem, fedora 35, upgrade from 33, however I got non-backup files: 1a3b5a8: Data object's entry array not sorted File corruption detected at /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system:1a3cf00 (of 33554432 bytes, 81%). FAIL: /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system (Bad message) 645998: Data object's entry array not sorted File corruption detected at /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system:afb0a8 (of 16777216 bytes, 68%). FAIL: /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system (Bad message) 39fbc8: Data object's entry array not sorted File corruption detected at /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system:846a20 (of 16777216 bytes, 51%). FAIL: /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system (Bad message) 2903430: Data object's entry array not sorted File corruption detected at /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system:605ba50 (of 109051904 bytes, 92%). FAIL: /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system (Bad message) 3aea480: Data object's entry array not sorted File corruption detected at /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system:45241c0 (of 75497472 bytes, 96%). FAIL: /var/log/journal/9bce2f058e9a4a4daf8856e045cffa73/system (Bad message) ... "Solved" with "journalctl --vacuum-time=7d" and "systemctl restart abrt-oops.service"
(In reply to Carl G. from comment #25) > RFE? .journal~ files should be ignored by abrt-dump-journal-oops? > > from man systemd-journald: > > "If the daemon is stopped uncleanly, or if the files are found to be > corrupted, they are renamed using the ".journal~" suffix, and > systemd-journald starts writing to a new file." Yes, I would suggest going with an RFE, or simply treat the issue like a bug-fix. Seems the underlying assumption was violated, that renaming journal files would cause them to be ignored. And... they are currently NOT ignored. So that suggests we could make `abrt-dump-journal-oops` ignore corrupted journal files, or perhaps `systemd-journald` deletes corrupted files instead of renaming, or do better at renaming, or moves the corrupt files out of the pathway, etc... Anything like that would work. A bonus stretch goal might be to have `journalctl` gain a feature enhancement to vacuum corrupted journal files.
Guys, does anyone still have one of the offending .journal~ files? Also see https://github.com/systemd/systemd/pull/22340
(In reply to Michal Fabik from comment #28) > Guys, does anyone still have one of the offending .journal~ files? > > Also see https://github.com/systemd/systemd/pull/22340 I do not
(In reply to Michal Fabik from comment #28) > Guys, does anyone still have one of the offending .journal~ files? I removed them, asking my colleagues if they have any... should know by tomorrow.
nope, sorry. Will preserve some logs if it happens again...
Just started happening on one of my Fedora 33 boxes
This started happening to me on Fedora 36 with abrt 2.15.1-1. It looks like the upstream bug https://github.com/abrt/abrt/issues/1604. A fix has been merged (https://github.com/abrt/abrt/pull/1605) but isn't included in the latest release.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.