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.

Description of problem:

The system journal rotation may fail when flushing to /var in the following piece of code:

int server_flush_to_var(Server *s) {
[...]
                server_rotate(s);
                server_vacuum(s);

                if (!s->system_journal) {
                        log_notice("Didn't flush runtime journal since rotation of system journal wasn't successful.");
                        r = -EIO;
HERE ---->              goto finish;
                }
[...]
finish:
        journal_file_post_change(s->system_journal);
[...]
This leads to calling journal_file_post_change with NULL pointer argument, causing the following assertion to fail:

void journal_file_post_change(JournalFile *f) {
        assert(f);
        [...]
}


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

systemd-219 -> latest upstream


How reproducible:

Don't know


Additional info:

Upstream PR: https://github.com/systemd/systemd/pull/9893

Fixed in Upstream by fd790d6f09b10a87b007b71403cb018f18ff91c9

https://github.com/lnykryn/systemd-rhel/pull/230

fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/230 -> 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://access.redhat.com/errata/RHSA-2019:2091