| Summary: | abrt-oops.service: Fail ed with result 'exit-code'. (is too cryptic) after abrt -dump-journal-oops: Cannot read journal data. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Dodson <jwadodson> |
| Component: | abrt | Assignee: | abrt <abrt-devel-list> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | abrt-devel-list, iprikryl, jberan, mhabrnal, michal.toman, mmilata, phelia, rh001 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-08 19:01:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
John Dodson
2016-10-28 05:56:46 UTC
Like most other things I'm assuming this will wait till EoL so it can be ignored? 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. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. It is still failing in Fedora 27 and cannot be manually started. I think i resolved this issue. It looks like this turned out to be a corrupted journal file. Ran: "journalctl --verify" ... PASS: /var/log/journal/db5bf142ccd74b4bbf9ee92563daa927/system~ 480fd8: Invalid entry item (0/12 offset: 000000 480fd8: Invalid object contents: Bad message File corruption detected at /var/log/journal/db5bf142ccd74b4bbf9ee92563daa927/system~:480fd8 (of 8388608 bytes, 56%). FAIL: /var/log/journal/db5bf142ccd74b4bbf9ee92563daa927/system~ (Bad message) PASS: /var/log/journal/db5bf142ccd74b4bbf9ee92563daa927/system~ ... Removed file: /var/log/journal/db5bf142ccd74b4bbf9ee92563daa927/system~ Restarted services: "systemctl restart abrt-oops.service" It is now running. This appears to be related to Bug: 1433652 https://bugzilla.redhat.com/show_bug.cgi?id=1433652 |