Bug 1649857
| Summary: | systemd-journal-flush.service fails in timeout causing boot to be delayed by 1min30 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Renaud Métrich <rmetrich> | ||||||
| Component: | systemd | Assignee: | systemd-maint | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 7.6 | CC: | dreua, systemd-maint-list | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-03-15 07:31:37 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
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" Created attachment 1505729 [details]
console output with "rd.debug"
Created attachment 1505730 [details]
console output with "debug rd.debug" (no issue)
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. 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 |
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