You are not logged in.
Pages: 1
Hi everyone, so I've got a problem when I poweroff the system and with journalctl -b-1 | tail I've got this error message:
kernel: printk: systemd-shutdow: 47 output lines suppressed due to ratelimiting
Then, I make a research on Duckduckgo and I found that this message it isn't enough and I should have checked journalctl with journalctl --verify.
4b9fc0: Invalid hash (f6fe0b124df26c4c vs. 74cf7da3e53380ea
4b9fc0: Invalid object contents: Wrong message
File corruption detected at /var/log/journal/fc61b67a8b7d42668d34660a7c68a56c/system@000591cada07b873-4a0a721438bc2eb0.journal~:4b9fc0 (of 8388608 bytes, 59%).
What I should do to resolve this problem?
See, I'm not a monster. I'm just ahead of the curve.
Offline
What I should do to resolve this problem?
Do you mean repair the journal? As far as I am aware that is not possible. However the journal will not display content that it detects as corrupt.
If you are asking how to prevent the journal from being corrupted. Without knowing how the journal became corrupted I can not offer specific advice.
Offline
I believe this is part of systemd regression that has been discussed here.
Offline
Pages: 1