Bug 1281044
Summary: | Error was encountered while opening journal files: No data available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Steve <bugzilla> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | bugzilla, johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-17 15:41:32 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: |
Description
Steve
2015-11-12 03:54:11 UTC
With this amount of information, nobody can really do anything about your problem. What does "ls /var/log/journal/*" show? Is SELinux on? If yes, does the problem disappear after "setenforce 0"? $ ls /var/log/journal/* system~ system~ system~ system~ system~ system~ system~ system~ system~ system~ system~ system system.journal user-7777~ user-7777~ user-7777~ user-7777~ user-7777~ user-7777~ user-7777~ user-7777~ user-7777~ user-7777 user-7777.journal $ Yes SELinux is on. The problem does not disappear after "setenforce 0". Try running "journalctl --verify". $ journalctl --verify Error was encountered while opening journal files: No data available $ sudo journalctl --verify Error was encountered while opening journal files: No data available $ After some research, i found this: $ sudo rpm -Va systemd .M....... /var/log/journal (Code M means: File mode differs.) The actual file mode is: 8 drwxr-sr-x+ 3 root systemd-journal 4096 Oct 19 09:13 journal Is something wrong here? This seems to be a known bug: https://bbs.archlinux.org/viewtopic.php?id=199411 https://github.com/systemd/systemd/issues/487 ... However, i found a workaround: $ sudo rm -rf /var/log/journal/ $ reboot After reboot, systemd will automatically create new journal files. The right permissions are: 4 drwxr-sr-x. 2 root systemd-journal 4096 Nov 17 06:16 journal |