Open mariusgrigoriu opened 5 years ago
Judging by the number of journals I'm guessing that machine has been running a while. Can you reproduce on a fresh machine?
While I pasted errors from our production systems that have been up a while, I did also see this on fresh machines too.
Issue Report
Bug
Container Linux Version
2079.4.0
Environment
AWS m4.10xlarge
Expected Behavior
journalctl --verify
completes successfullyActual Behavior
Seeing intermittent
Bad message
errors when runningjournalctl --verify
. I believe this problem is causing issues in other applications (fluentd in this case).Reproduction Steps
Unknown. It appears to be random whether
journalctl --verify
completes successfully.Other Information