Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1172588 [details]
journalctl verify

Description of problem:
  journalctl --verify
  Error was encountered while opening journal files: Invalid argument
  000000: missing entry array                                                                                                                              
  File corruption detected at
     /var/log/journal/e5cf1e868b0b4be0ace73f747c9e80fb/user-
     2100@d0f911ab162e4bd3b2cd549e626d1ea4-0000000000000000-
     0000000000000000.journal:000000 (of 8388608 bytes, 0%).


Version-Release number of selected component (if applicable):
   Red Hat Atomic

How reproducible:
   Not yet reproduced in our environment

Actual results:
  journalctl --verify
     Error was encountered while opening journal files: Invalid argument
     000000: missing entry array                                                                                                                              
     File corruption detected at
        /var/log/journal/e5cf1e868b0b4be0ace73f747c9e80fb/user-
        2100@d0f911ab162e4bd3b2cd549e626d1ea4-0000000000000000-
        0000000000000000.journal:000000 (of 8388608 bytes, 0%).

Expected results:
  journalctl commands show the log files properly

Additional info:
 https://github.com/poettering/systemd/commit/dade37d403f1b8c1d7bb2efbe2361f2a3e999613

Created attachment 1172589 [details]
Screenshot of error

patches commited to staging ->
journalctl: don't print -- No entries -- in quiet mode
https://github.com/lnykryn/systemd-rhel/commit/13f2490

journalctl: make sure 'journalctl -f -t unmatched' blocks
https://github.com/lnykryn/systemd-rhel/commit/3045db8

journal: uppercase first character in verify error messages
https://github.com/lnykryn/systemd-rhel/commit/2a9dd53

journalctl: properly detect empty journal files
https://github.com/lnykryn/systemd-rhel/commit/8290b73

journal: explain the error when we find a non-DATA object that is compressed
https://github.com/lnykryn/systemd-rhel/commit/8cfa250

journal: when verifying journal files, handle empty ones nicely
https://github.com/lnykryn/systemd-rhel/commit/0c2f52b

journal: avoid mapping empty data and field hash tables
https://github.com/lnykryn/systemd-rhel/commit/283df68

journal-verify: don't hit SIGFPE when determining progress
https://github.com/lnykryn/systemd-rhel/commit/1466d84
-> post

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2216.html