Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691549 - systemd-journald Cannot allocate memory
Summary: systemd-journald Cannot allocate memory
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 28
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-21 21:16 UTC by Adam Pribyl
Modified: 2019-04-01 08:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Adam Pribyl 2019-03-21 21:16:12 UTC
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.

Comment 1 Adam Pribyl 2019-03-21 21:25:46 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.