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 1141945 [details]
abrt directory tarball

I don't have a huge amount of context for this one: I booted my RHEL-7.2 VM and abrt complained about this.

Please find ccpp data attached.

looks like this https://bugzilla.redhat.com/show_bug.cgi?id=1300212

(In reply to Lukáš Nykrýn from comment #2)
> looks like this https://bugzilla.redhat.com/show_bug.cgi?id=1300212

Makes sense.  Not sure if this caused it, but this was on a VM while the host was `pm-suspend`ed and resumed probably several times.

The problem has recurred.  I can attach another abrt directory if that's helpful.

(In reply to Lukáš Nykrýn from comment #2)
> looks like this https://bugzilla.redhat.com/show_bug.cgi?id=1300212

I don't think it is the same problem. From abrt data I can see that journal daemon, at the time of the crash, didn't have any actual on-disk file mmap-ed, Only run time journal was in use.

There's not much we can do with no context.