Bug 2179327

Summary:	systemd-journal-flush.service fails in timeout
Product:	Red Hat Enterprise Linux 8	Reporter:	David Auer <dreua>
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
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-20 11:36:31 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 David Auer 2023-03-17 11:21:47 UTC

Description of problem:
After the regular system update and reboot, "systemctl --failed" showd me that systemctl-journal-flush failed.

The status for this service showed me that it ran into a timeout:

Mar 17 11:20:17 redacted systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 17 11:21:48 redacted systemd[1]: systemd-journal-flush.service: start operation timed out. Terminating.
Mar 17 11:21:48 redacted systemd[1]: systemd-journal-flush.service: Main process exited, code=killed, status=15/TERM
Mar 17 11:21:48 redacted systemd[1]: systemd-journal-flush.service: Failed with result 'timeout'.
Mar 17 11:21:48 redacted systemd[1]: Failed to start Flush Journal to Persistent Storage.



Version-Release number of selected component (if applicable):
systemd.x86_64 251.11-2.fc37        

How reproducible:
Unknown, reboot did not fix it.

Steps to Reproduce:
Simple update.

Additional info:
This is CentOS 8 Stream (Upgraded from CentOS 8 before that went eol)

Workaround:
I enabled persistent logging (it was disabled by default, because I like that anyway and the service ran fine after a reboot.

Comment 1 David Auer 2023-03-17 11:28:15 UTC

Additional info:
The log itself looks good to me, uses about 8 MB for a regular boot. There is enough free disk space on all partitions and ram usage is minimal.

Comment 2 David Tardon 2023-03-20 11:36:31 UTC


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