Description of problem: There are many reports in past month about memory usage of problems in systemd-journald. #1665931 was closed as only having fix for F29, but I do have the similar issues on F28.i686 Version-Release number of selected component (if applicable): systemd-238-12.git07f8cd5.fc28.i686 How reproducible: Seldom... Steps to Reproduce: What happend now is: 1. dnf update get stuck 2. strace -p pidof dnf showed the dnf is stuck at connect to systemd-journald 3. log shows: Mar 21 21:51:24 server systemd-journald[27156]: Journal started Mar 21 21:51:24 server systemd-journald[27156]: System journal (/var/log/journal/04a63c443e830a2cb9e4df0046fc16aa) is 248.0M, max 200.0M, 0B free. Mar 21 21:51:24 edna systemd-journald[607]: Failed to open /var/log/journal/04a63c443e830a2cb9e4df0046fc16aa: Cannot allocate memory 4. restarting the systemd-journald fixes the issue Additional info: For past month I experienced freezes of the system with systemd-journald not able to allocate memory. In the munin graphs the slab caches grows over all available RAM.
journalctl -r: Mar 21 21:51:24 server systemd[1]: Stopped Journal Service. Mar 21 21:51:24 server kernel: printk: systemd-journal: 65178 output lines suppressed due to ratelimiting Mar 21 21:51:24 server systemd-journald[607]: Failed to open /var/log/journal/04a63c443e830a2cb9e4df0046fc16aa: Cannot allocate memory Mar 21 21:51:24 server systemd-journald[27156]: System journal (/var/log/journal/04a63c443e830a2cb9e4df0046fc16aa) is 248.0M, max 200.0M, 0B free. Mar 21 21:51:24 server systemd-journald[27156]: Journal started Mar 19 22:15:01 server audit[6807]: USER_ACCT pid=6807 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_access,pa> Mar 19 22:14:33 server systemd[1]: Removed slice User Slice of root. So there are two days of log missing... without restarting the systemd-journald it would consume the logs further.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** Bug 1698946 has been marked as a duplicate of this bug. ***
i think switching the bug to "F29" or rawhide and to an hardware independent state, can't hurt.
It was fixed in F29 and later, it's just F28 that remains potentially unfixed.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.