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.
Bug 1649857 - systemd-journal-flush.service fails in timeout causing boot to be delayed by 1min30
Summary: systemd-journal-flush.service fails in timeout causing boot to be delayed by ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-14 16:15 UTC by Renaud Métrich
Modified: 2023-03-17 11:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-15 07:31:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
console output with "rd.debug" (230.78 KB, text/plain)
2018-11-14 16:39 UTC, Renaud Métrich 		no flags Details
console output with "debug rd.debug" (no issue) (1.16 MB, text/plain)
2018-11-14 16:39 UTC, Renaud Métrich 		no flags Details
View All

Description Renaud Métrich 2018-11-14 16:15:32 UTC 
Description of problem:

When booting with FIPS enabled and "rd.debug" flag, which causes a lot of messages to be displayed on the console and recorded to the journal, the systemd-journal-flush.service fails in timeout, which delays the boot by 1min30 (the service timeout).
This happens even when there is no persistent journal. It's probably unrelated to FIPS but due to having tons of messages.

Boot messages:

[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[   13.885949] systemd-journald[4183]: File /run/log/journal/4f49f3f30a6622e1e22e91da82df2e77/system.journal corrupted or uncleanly shut down, renaming and replacing.
[  OK  ] Started Journal Service.
[FAILED] Failed to start Flush Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.


# journalctl -u systemd-journal-flush.service
-- Logs begin at Wed 2018-11-14 14:38:31 CET, end at Wed 2018-11-14 17:06:50 CET. --
Nov 14 14:38:41 vm-fips7 systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 14 14:40:11 vm-fips7 systemd[1]: systemd-journal-flush.service start operation timed out. Terminating
Nov 14 14:40:11 vm-fips7 systemd[1]: Failed to start Flush Journal to Persistent Storage.
Nov 14 14:40:11 vm-fips7 systemd[1]: Unit systemd-journal-flush.service entered failed state.
Nov 14 14:40:11 vm-fips7 systemd[1]: systemd-journal-flush.service failed.


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

systemd-219-62.el7.x86_64 but also prior releases (e.g. systemd-219-57.el7_5.3.x86_64)


How reproducible:

Always


Steps to Reproduce:

1. Enable FIPS

  # yum -y install dracut-fips
  # dracut -f

  # sed -i "s/^GRUB_CMDLINE_LINUX=\"\\(.*\\)\"/GRUB_CMDLINE_LINUX=\"\\1 fips=1 boot=$(awk '$2 == "/boot" { print $1 }' /etc/fstab) rd.debug\"/" /etc/default/grub
  # grub2-mkconfig -o /etc/grub2.cfg

2. Boot

Actual results:

[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[   13.885949] systemd-journald[4183]: File /run/log/journal/4f49f3f30a6622e1e22e91da82df2e77/system.journal corrupted or uncleanly shut down, renaming and replacing.
[  OK  ] Started Journal Service.
[FAILED] Failed to start Flush Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.


Expected results:

No delay / no error
Comment 2 Renaud Métrich 2018-11-14 16:38:36 UTC 
The issue doesn't happen when booting with both "debug" and "rd.debug".
Attaching console outputs:
- rddebug.txt: issue happening with "rd.debug"
- debug_rddebug.txt: issue not happening with "debug" and "rd.debug"
Comment 3 Renaud Métrich 2018-11-14 16:39:10 UTC 
Created attachment 1505729 [details]
console output with "rd.debug"
Comment 4 Renaud Métrich 2018-11-14 16:39:52 UTC 
Created attachment 1505730 [details]
console output with "debug rd.debug" (no issue)
Comment 7 RHEL Program Management 2021-03-15 07:31:37 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 8 David Auer 2023-03-17 11:24:06 UTC 
Since this is the top google hit, allow me to link to a current bug with the same error message but a different cause:
https://bugzilla.redhat.com/show_bug.cgi?id=2179327
Note You need to log in before you can comment on or make changes to this bug.