You are not logged in.
Hello
Since I upgraded to systemd 221, journalctl is broken:
$ journalctl -f
Error was encountered while opening journal files: Invalid argument
$ sudo journalctl -f
Error was encountered while opening journal files: Invalid argument
I also tried to re-install systemd in the current version, but this didn't help.
I ran out of space in the /var filesystem AFTER upgrading to the latest systemd version. I also rebooted several times to ensure the filesystem is ok, since Arch checks the filesystem on every boot.
The only search result in the internet is this one https://www.mail-archive.com/systemd-de … 32757.html which sounds similar, also with
If I use journalctl of systed 219 from the Arch Rollback Machine, it works like expected:
$ curl -s http://seblu.net/a/arm/2015/06/15/core/os/x86_64/systemd-219-6-x86_64.pkg.tar.xz | xz -d | tar -xf - usr/bin/journalctl 2>/dev/null
$ usr/bin/journalctl -f
-- Logs begin at Thu 2014-10-23 00:49:11 CEST. --
[...]
So this is why I think it's not a filesystem error because this binary works fine.
Has any one else the same problem with journalctl?
thx
mindfuckup
Last edited by mindfuckup (2015-06-24 21:24:08)
Offline
Online
Could it be related to this https://bbs.archlinux.org/viewtopic.php?id=198683?
Is there by any chance a corrupted file? What is the output of the following commands (assuming your user has id 1000)?
journalctl --verify
journalctl --verify --file /var/log/journal/$logdir/system.journal
journalctl --verify --file /var/log/journal/$logdir/user-1000.journall
Where $logdir is the name of the directory containing the journal files.
Offline
Yes with `SYSTEMD_LOG_LEVEL=debug journalctl`, i got this error:
Failed to add file /var/log/journal/45a16f5406e346168a94791581a8b952/user-1000.journal: Invalid argument
The user log file is not valid:
$ journalctl --verify --file /var/log/journal/*/system.journal
PASS: /var/log/journal/45a16f5406e346168a94791581a8b952/system.journal
$ journalctl --verify --file /var/log/journal/*/user-1000.journal
Failed to open /var/log/journal/45a16f5406e346168a94791581a8b952/user-1000.journal: Invalid argument
Failed to open files: Invalid argument
If i remove the invalid file, journalctl works again. But strange the older version 219 of journalctl works with the invalid file.
Offline
Exact same "Invalid argument" issue after an upgrade from 30 days old.
I keep my journals between boots.
I suspect that an upgrade isn't backwards compatibile with the old file format.
I wiped out my logs and everything is fine now.
# cd /var/log/journal
# ls -l
# rm -rf {ids}/
Offline