Description of problem: journalctl cannot read system journal. Version-Release number of selected component (if applicable): 243.4-1.fc31 How reproducible: Easily, just run journalctl. Steps to Reproduce: 1. run journalctl Actual results: Error message: $ journalctl Journal file /var/log/journal/ca0002d173ab497aba312acd6693956c/system uses an unsupported feature, ignoring file. Use SYSTEMD_LOG_LEVEL=debug journalctl --file=/var/log/journal/ca0002d173ab497aba312acd6693956c/system to see the details. -- No entries -- Running the suggested command yields: $ SYSTEMD_LOG_LEVEL=debug journalctl --file=/var/log/journal/ca0002d173ab497aba312acd6693956c/system Journal file /var/log/journal/ca0002d173ab497aba312acd6693956c/system uses incompatible flag lz4-compressed disabled at compilation time. Failed to open journal file /var/log/journal/ca0002d173ab497aba312acd6693956c/system: Protocol not supported mmap cache statistics: 0 hit, 1 miss Failed to open files: Protocol not supported Expected results: System Journal is shown Additional info: $ journalctl --version systemd 234 -PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL -XZ -LZ4 -SECCOMP +BLKID -ELFUTILS -KMOD -IDN2 -IDN default-hierarchy=hybrid $ dnf info systemd Installed Packages Name : systemd Version : 243.4 Release : 1.fc31 Architecture : x86_64 Size : 12 M Source : systemd-243.4-1.fc31.src.rpm Repository : @System From repo : updates
I cannot really deduct from anywhere why it is -LZ4 for journalctl, while systemd writes exactly that format. Any clue?
Sorry for the slow reply. The only explanation I see is that you're running a different journalctl binary. Did you compile systemd for testing by any chance? journalctl from systemd-243.4-1.fc31.x86_64.rpm that I downloaded now from koji says: $ LD_LIBRARY_PATH=. ./journalctl --version systemd 243 (v243.4-1.fc31) +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified (Those strings are compiled into libsystemd-shared.so, they are not generated dynamically. So if some package was missing or in a different version, the journalctl binary would not start.) This seems to be a local problem.