28 Apr
2016
28 Apr
'16
1:46 a.m.
Once upon a time, Chris Murphy lists@colorremedies.com said:
Also I wonder if merely restarting the journal daemon solves it:
systemctl restart systemd-journald
What should happen is it realizes its own logs are corrupt and ignores them, and starts working on new copies. And journalctl should still try to read the old ones but skips the corrupt entries.
I tried that and it didn't work (at least not every time). I had to actually remove the journal file to get it functional again.
So far, turning off the compression appears to have worked (but I'll have to watch it for a day or two to really see).
--
Chris Adams linux@cmadams.net