Bug 1281044 - Error was encountered while opening journal files: No data available
Summary: Error was encountered while opening journal files: No data available
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-12 03:54 UTC by Steve
Modified: 2015-11-17 15:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-17 15:41:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steve 2015-11-12 03:54:11 UTC
Description of problem:
Error was encountered while opening journal files: No data available

Version-Release number of selected component (if applicable):
systemd-222-8.fc23.x86_64

How reproducible:
always

Steps to Reproduce:
1. Open Terminal
2. Type "journalctl"
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jan Synacek 2015-11-12 13:38:46 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"?

Comment 2 Steve 2015-11-12 15:04:42 UTC
$ 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".

Comment 3 Jan Synacek 2015-11-13 08:10:44 UTC
Try running "journalctl --verify".

Comment 4 Steve 2015-11-13 08:21:46 UTC
$ 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
$

Comment 5 Steve 2015-11-14 16:57:36 UTC
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?

Comment 6 Steve 2015-11-16 15:10:04 UTC
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.

Comment 7 Steve 2015-11-17 05:22:00 UTC
The right permissions are:

4 drwxr-sr-x.  2 root   systemd-journal     4096 Nov 17 06:16 journal


Note You need to log in before you can comment on or make changes to this bug.