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.
Descriptionhidenori.i@prime-strategy.co.jp
2023-03-16 05:19:18 UTC
Description of problem:
After reboot of the CentOS Stream 8, systemd hangs at 'initializing' for about 90s due to waiting for timeout in systemd-jounal-flush.service.
Following is the log:
You can see that systemd-journal-flush.service waits start operation timed out
for 90s.
-- Logs begin at Thu 2023-03-16 02:52:57 UTC. --
Mar 16 02:52:57 hogehoge systemd-journald[512]: Journal started
Mar 16 02:52:57 hogehoge systemd-journald[512]: Runtime journal (/run/log/journal/1a6666fbb1fb48a5857970d94b2c5fd9) is 8.0M, max 4.0G, 3.9G free.
Mar 16 02:52:57 hogehoge systemd-sysctl[514]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory
Mar 16 02:52:57 hogehoge systemd-sysctl[514]: Couldn't write '81920' to 'net/core/optmem_max', ignoring: No such file or directory
Mar 16 02:52:57 hogehoge systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 16 02:52:57 hogehoge systemd-journald[512]: Runtime journal (/run/log/journal/1a6666fbb1fb48a5857970d94b2c5fd9) is 8.0M, max 4.0G, 3.9G free.
Mar 16 02:54:27 hogehoge systemd[1]: systemd-journal-flush.service: start operation timed out. Terminating.
Mar 16 02:54:27 hogehoge systemd[1]: systemd-journal-flush.service: Main process exited, code=killed, status=15/TERM
Mar 16 02:54:27 hogehoge systemd[1]: systemd-journal-flush.service: Failed with result 'timeout'.
Mar 16 02:54:27 hogehoge systemd[1]: Failed to start Flush Journal to Persistent Storage.
Mar 16 02:54:27 hogehoge systemd[1]: Starting Create Volatile Files and Directories...
Version-Release number of selected component (if applicable):
systemd-239-73.el8.x86_64
Reverting to systemd-239-71.el8.x86_64 solves this issue.
How reproducible:
Steps to Reproduce:
1. Install clean CentOS Stream 8.
2. Update systemd to systemd-239-73.el8.x86_64.
3. Reboot.
Actual results:
As shown at the top, systemd-journal-flush.service waits for its time out for 90s which results in prolonging the boot time for an extra 90s.
Manual restart of systemd-journal-flush.service also fails.
Expected results:
systemd-journal-flush.service starts up cleanly so that the OS boot does not take more than 90s.
Additional info:
I see the same issue. Upgraded CentOS Stream 8 servers today, including an update of systemd from systemd-239-71.el8.x86_64 to systemd-239-73.el8.x86_64.
The problem is that
# journalctl --flush
hangs indefinitely and thus systemd kill the process after 90s timeout.
I have 8 servers updated, all have this problem. The servers not updated yet are fine.
None of the servers write presistent logs so basically it should really do anything, i.e. /var/log/journal does not exist.