Bug 2178897

Summary:	systemd-journal-flush.service fails at initialization.
Product:	Red Hat Enterprise Linux 8	Reporter:	hidenori.i <hidenori.i>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, dtardon, jwboyer, systemd-maint-list, vogt
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-16 16:18:48 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:

Description hidenori.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:

Comment 1 Gerald Vogt 2023-03-16 05:40:00 UTC

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.

Comment 2 David Tardon 2023-03-16 16:18:48 UTC


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