Once upon a time, Chris Murphy <lists at 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 at cmadams.net>
Once upon a time, Chris Adams <linux at cmadams.net> said:> 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).Just to follow up: turning off journald compression does appear to have fixed the corruption problem I was seeing. I'll watch for an updated systemd package. -- Chris Adams <linux at cmadams.net>
On Fri, Apr 29, 2016 at 6:26 AM, Chris Adams <linux at cmadams.net> wrote:> Once upon a time, Chris Adams <linux at cmadams.net> said: >> 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). > > Just to follow up: turning off journald compression does appear to have > fixed the corruption problem I was seeing. I'll watch for an updated > systemd package.Does journalctl --verify no longer complain of corruption? Or is it possible there's corruption but journalctl and rsyslogd now tolerate it somehow? -- Chris Murphy