Arch Linux

baronmog

Member

Registered: 2013-11-01

Posts: 60

logging/journalctl broken after systemd upgrade

Rebooted today, for the first time since systemd was upgraded (219-6 -> 221-1), and when I run journalctl, I now get

Error was encountered while opening journal files: No data available

Anyone else encountering this?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: logging/journalctl broken after systemd upgrade

Yes. There is at least one other thread and a bug report about it.

baronmog

Member

Registered: 2013-11-01

Posts: 60

Re: logging/journalctl broken after systemd upgrade

Yes. There is at least one other thread and a bug report about it.

Yeah, found the bug entry after posting this. I'd chime in on the bug report https://bugs.archlinux.org/task/45451 , but flyspray won't let me create an account.

zatricky

Member

From: Stockholm

Registered: 2008-09-03

Posts: 56

Website

Re: logging/journalctl broken after systemd upgrade

I'm getting the same error as you, baronmog.

The flyspray bug mentioned there has a different error. Here we're talking about "No data available". The existing flyspray bug mentions "Invalid argument".

Log output using the "SYSTEMD_LOG_LEVEL=debug" on my side shows that it is looking in the correct location. The files in that location have files with various timestamps, some recent enough to imply that data is still being written to them.

---

pacman russian roulette: yes | pacman -Rcs $(pacman -Q | LANG=C sort -R | head -n $((RANDOM % 10)))
(yes, I know its broken)

Franek

Member

Registered: 2010-05-16

Posts: 100

Re: logging/journalctl broken after systemd upgrade

I had the same error. It gave me idea to install syslog-ng again. Because I figured it wouldn't make sense for syslog-ng to try to pull logs from presumably corrupted journal files, I set these options in /etc/systemd/journald.conf:

Storage=none
ForwardToSyslog=yes

On the next reboot, I could watch journald flush months and months of old logs to syslog-ng (so apparently the logs where there, just not readable for journalctl?), which took several minutes. The very last entries in /var/log/messages said:

Aug 17 10:29:53 Brett systemd[1]: Starting Cleanup of Temporary Directories...
Aug 17 10:29:56 Brett systemd[1]: Started Cleanup of Temporary Directories.

Now everything (with syslog-ng) works nicely. (Tested by entering "logger -- test", which immediately appears as an entry in /var/log/messages.)