Bug 1244958
| Summary: | Journal never moved to persistent storage with broken journal file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Göran Uddeborg <goeran> | ||||
| Component: | systemd | Assignee: | systemd-maint | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 22 | CC: | heri, johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, zbyszek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | systemd-219-21.fc22 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-10 09:52:58 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: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This should work fine with https://github.com/systemd/systemd/issues/695 applied. journalctl couldn't handle journal files with only a header and not a single object inside nicely. With that PR it can. systemd-219-21.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/systemd-219-21.fc22 Package systemd-219-21.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-219-21.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-12802/systemd-219-21.fc22 then log in and leave karma (feedback). systemd-219-21.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 1054038 [details] The suspicious system.journal file. Description of problem: Recently we had problems with a disk that started to behave badly. Finally it was kicked out of the raid by the OS, but on the way there we had a couple of crashes. Recently we discovered that there were no journal files persistently saved after that event. The journals were still saved in memory under /run/log, but nothing went into /var/log. Sending extra SIGUSR1 signals to the journald didn't have any apparent effect. To make a long story short, I finally tried to move away the system.journal file in /var/log. That seems to have helped. Sending a SIGUSR1 signal after that created a new large system.journal file, and also a user-1003.journal file. I believe I have read that when the journal daemon finds a corrupt journal file it is supposed to rotate it and move to the next. That does not seem to have happened in this case. Maybe my particular system.journal file was broken in some extra poisonous way? I attach it for your investigation. It's only 240 bytes long. Version-Release number of selected component (if applicable): systemd-219-15.fc22.x86_64 How reproducible: Has happened only once so far. Steps to Reproduce: 1. Maybe: crash the computer in a specially bad way? :-)