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:
After the regular system update and reboot, "systemctl --failed" showd me that systemctl-journal-flush failed.

The status for this service showed me that it ran into a timeout:

Mar 17 11:20:17 redacted systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 17 11:21:48 redacted systemd[1]: systemd-journal-flush.service: start operation timed out. Terminating.
Mar 17 11:21:48 redacted systemd[1]: systemd-journal-flush.service: Main process exited, code=killed, status=15/TERM
Mar 17 11:21:48 redacted systemd[1]: systemd-journal-flush.service: Failed with result 'timeout'.
Mar 17 11:21:48 redacted systemd[1]: Failed to start Flush Journal to Persistent Storage.



Version-Release number of selected component (if applicable):
systemd.x86_64 251.11-2.fc37        

How reproducible:
Unknown, reboot did not fix it.

Steps to Reproduce:
Simple update.

Additional info:
This is CentOS 8 Stream (Upgraded from CentOS 8 before that went eol)

Workaround:
I enabled persistent logging (it was disabled by default, because I like that anyway and the service ran fine after a reboot.

Additional info:
The log itself looks good to me, uses about 8 MB for a regular boot. There is enough free disk space on all partitions and ram usage is minimal.

*** This bug has been marked as a duplicate of bug 2174645 ***