Actions
Bug #36235
closed90 seconds boot delay because systemd-journal-flush.service won't start
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Image
Description
In FDI 4.1.0 we've noticed a 90 seconds boot delay because systemd-journal-flush.service won't start.
This behavior is seen isn't seen in FDI 3.8.0
[root@fdi ~]# systemctl status systemd-journal-flush.service
● systemd-journal-flush.service - Flush Journal to Persistent Storage
Loaded: loaded (/usr/lib/systemd/system/systemd-journal-flush.service; static; vendor preset: disabled)
Active: failed (Result: timeout) since Mon 2023-03-27 19:45:36 UTC; 16min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Process: 808 ExecStart=/usr/bin/journalctl --flush (code=killed, signal=TERM)
Main PID: 808 (code=killed, signal=TERM)
Mar 27 19:44:06 fdi systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 27 19:45:36 fdi systemd[1]: systemd-journal-flush.service: start operation timed out. Terminating.
Mar 27 19:45:36 fdi systemd[1]: systemd-journal-flush.service: Main process exited, code=killed, status=15/TERM
Mar 27 19:45:36 fdi systemd[1]: systemd-journal-flush.service: Failed with result 'timeout'.
Mar 27 19:45:36 fdi systemd[1]: Failed to start Flush Journal to Persistent Storage.
[root@fdi ~]#
After the 90 seconds, FDI works as expected.
Updated by Patrick Kuijvenhoven over 1 year ago
Updated by Ewoud Kohl van Wijngaarden over 1 year ago
- Status changed from New to Closed
Updated by Ewoud Kohl van Wijngaarden over 1 year ago
Also linking here: https://bugzilla.redhat.com/show_bug.cgi?id=2174645 is the cause of this.
Actions