search for: f8ade260c5f84b8aa04095c233c041e0

...t;> > >> Determined with 'journalctl --verify' or another way? One system did get into this state overnight, and that said: [root at spamscan3 ~]# journalctl --verify 15bd478: invalid object File corruption detected at /run/log/journal/f8ade260c5f84b8aa04095c233c041e0/system.journal:15bd478 (of 25165824 bytes, 90%). FAIL: /run/log/journal/f8ade260c5f84b8aa04095c233c041e0/system.journal (Cannot assign requested address) (and then a bunch of passes on the rest of the files) > There's also this patch as a suggested fix: > https://bugzilla.redhat.com/show...

...gt;> >> >> >> Determined with 'journalctl --verify' or another way? > > One system did get into this state overnight, and that said: > > [root at spamscan3 ~]# journalctl --verify > 15bd478: invalid object > File corruption detected at /run/log/journal/f8ade260c5f84b8aa04095c233c041e0/system.journal:15bd478 (of 25165824 bytes, 90%). > FAIL: /run/log/journal/f8ade260c5f84b8aa04095c233c041e0/system.journal (Cannot assign requested address) > (and then a bunch of passes on the rest of the files) > >> There's also this patch as a suggested fix: >> https://bu...

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: > > I have several recently-installed CentOS 7 servers that keep having > > systemd-journald corruption > > Determined with 'journalctl --verify' or another way? I get messages like this in dmesg: [4756650.489117]