Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Nov 20 00:26:53 eicilld064 user.info journal: Runtime journal is using 200.0M (max allowed 189.1M, trying to leave 283.7M free of 1.6G available → current limit 200.0M).
Nov 20 00:26:53 eicilld064 user.info journal: Runtime journal is using 184.0M (max allowed 189.1M, trying to leave 283.7M free of 1.6G available → current limit 189.1M).
Nov 20 00:26:53 eicilld064 user.info journal: Journal started
Nov 20 00:26:53 eicilld064 daemon.err systemd: systemd-journald.service watchdog timeout (limit 1min)!
Nov 20 00:26:53 eicilld064 daemon.info systemd: Starting Flush Journal to Persistent Storage...
Nov 20 00:26:53 eicilld064 daemon.info systemd: Started Flush Journal to Persistent Storage.
Nov 20 00:32:13 eicilld064 daemon.info systemd: Time has been changed
Version-Release number of selected component (if applicable):
latest
How reproducible:
NA
It seems systemd upstream have changed from 1min to 3min.
https://github.com/systemd/systemd/commit/c2fc2c2560f0ca0fab383753c065e45d76f465e5
Where are you experiencing the behavior? What environment?
LAB environment.
When does the behavior occur? Frequently? Repeatedly? At certain times?
It seems to occur when the storage infra is more busy.
What information can you provide around timeframes and urgency?
It seems to occur between midnight and 1 a.m.