Hide Forgot
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.
We already have this change in rhel-7.4 https://github.com/lnykryn/systemd-rhel/commit/5be84b3ae46c0fd35c3e80d4f457bf5aedc8af8f
Does this matches criterias for z-stream? Users can easily change those values via drop-ins.
*** This bug has been marked as a duplicate of bug 1338806 ***