Am 07.08.20 um 18:02 schrieb Michael Biebl: > Am 07.08.20 um 15:22 schrieb 積丹尼 Dan Jacobson:
>> # journalctl -f >> Journal file >> /var/log/journal/64f9b494837d480e9ecd81ea0cef1551/system@5cd966d8e5d24653b114e239c300135e-00000000000e3792-0005ac0f7ccf0a84.journal >> uses an unsupported feature, ignoring file. >> Use SYSTEMD_LOG_LEVEL=debug journalctl >> --file=/var/log/journal/64f9b494837d480e9ecd81ea0cef1551/system@5cd966d8e5d24653b114e239c300135e-00000000000e3792-0005ac0f7ccf0a84.journal >> to see the details. >> >> # SYSTEMD_LOG_LEVEL=debug journalctl >> --file=/var/log/journal/64f9b494837d480e9ecd81ea0cef1551/system@5cd966d8e5d24653b114e239c300135e-00000000000e3792-0005ac0f7ccf0a84.journal >> Journal effective settings seal=no compress=no compress_threshold_bytes=8B >> Journal file >> /var/log/journal/64f9b494837d480e9ecd81ea0cef1551/system@5cd966d8e5d24653b114e239c300135e-00000000000e3792-0005ac0f7ccf0a84.journal >> has unknown incompatible flags 0xc >> Failed to open journal file >> /var/log/journal/64f9b494837d480e9ecd81ea0cef1551/system@5cd966d8e5d24653b114e239c300135e-00000000000e3792-0005ac0f7ccf0a84.journal: >> Protocol not supported >> mmap cache statistics: 0 hit, 1 miss >> Failed to open files: Protocol not supported >> >> Maybe this was caused by me >> downgrading 246-2 to 245.7-1 ? > > Correct. Keep in mind, that downgrades are in general not supported. To be more specific: journald was compiled with zstd support in v246 and this is used as default compression, apparently. Older journalctl versions don't support zstd. Maybe we should keep lz4 as default compression (for one additional release cycle), even if zstd support was enabled. This way we would have some sort of forward compatibility. Thoughts? Anyone willing to work on this?
signature.asc
Description: OpenPGP digital signature
