The Systemd Journald use too much memory and don't respect SystemMaxUse and RuntimeMaxUse?
Clash Royale CLAN TAG#URR8PPP
I found the systemd-journald takes like 1GB+ of memory. After some searching I set the value of SystemMaxUse and RuntimeMaxUse both to 8M in "/etc/systemd/journald.conf". Then restart the journald.
After a while I found that limit doesn't work, check through 'top' and procstat.memory_rss, the systemd-journald still consumes 100+M after a while (Below is the visualization of journald memory catch through procstat.memory_rss). Any idea?
My systemd version is 219.
linux centos systemd systemd-journald
asked Jan 24 at 23:19
batileibatilei
587
add a comment |
I found the systemd-journald takes like 1GB+ of memory. After some searching I set the value of SystemMaxUse and RuntimeMaxUse both to 8M in "/etc/systemd/journald.conf". Then restart the journald.
After a while I found that limit doesn't work, check through 'top' and procstat.memory_rss, the systemd-journald still consumes 100+M after a while (Below is the visualization of journald memory catch through procstat.memory_rss). Any idea?
My systemd version is 219.
linux centos systemd systemd-journald
asked Jan 24 at 23:19
batileibatilei
587
Yep, it does grab a lot of RAM.
– K7AAY
Jan 24 at 23:37
add a comment |
I found the systemd-journald takes like 1GB+ of memory. After some searching I set the value of SystemMaxUse and RuntimeMaxUse both to 8M in "/etc/systemd/journald.conf". Then restart the journald.
After a while I found that limit doesn't work, check through 'top' and procstat.memory_rss, the systemd-journald still consumes 100+M after a while (Below is the visualization of journald memory catch through procstat.memory_rss). Any idea?
My systemd version is 219.
linux centos systemd systemd-journald
asked Jan 24 at 23:19
batileibatilei
587
I found the systemd-journald takes like 1GB+ of memory. After some searching I set the value of SystemMaxUse and RuntimeMaxUse both to 8M in "/etc/systemd/journald.conf". Then restart the journald.
After a while I found that limit doesn't work, check through 'top' and procstat.memory_rss, the systemd-journald still consumes 100+M after a while (Below is the visualization of journald memory catch through procstat.memory_rss). Any idea?
My systemd version is 219.
linux centos systemd systemd-journald
linux centos systemd systemd-journald
asked Jan 24 at 23:19
batileibatilei
587
asked Jan 24 at 23:19
batileibatilei
587
asked Jan 24 at 23:19
batileibatilei
587
asked Jan 24 at 23:19
batileibatilei
587
asked Jan 24 at 23:19
batileibatilei
587
587
Yep, it does grab a lot of RAM.
– K7AAY
Jan 24 at 23:37
add a comment |
Yep, it does grab a lot of RAM.
– K7AAY
Jan 24 at 23:37
Yep, it does grab a lot of RAM.
– K7AAY
Jan 24 at 23:37
Yep, it does grab a lot of RAM.
– K7AAY
Jan 24 at 23:37
add a comment |
1 Answer
1
active
oldest
votes
Both SystemMaxUse and RuntimeMaxUse control disk space usage not memory usage. RuntimeMaxUse does apply to logs on the volatile file system (/run) but thats not captured by procstat.memory_rss Further neither of those options constrain active log files only archived ones.
If journald really is using a GB I would take a serious look at whats creating all of those logs.
answered Jan 25 at 9:33
jdwolfjdwolf
2,695216
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496574%2fthe-systemd-journald-use-too-much-memory-and-dont-respect-systemmaxuse-and-runt%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Both SystemMaxUse and RuntimeMaxUse control disk space usage not memory usage. RuntimeMaxUse does apply to logs on the volatile file system (/run) but thats not captured by procstat.memory_rss Further neither of those options constrain active log files only archived ones.
If journald really is using a GB I would take a serious look at whats creating all of those logs.
answered Jan 25 at 9:33
jdwolfjdwolf
2,695216
add a comment |
Both SystemMaxUse and RuntimeMaxUse control disk space usage not memory usage. RuntimeMaxUse does apply to logs on the volatile file system (/run) but thats not captured by procstat.memory_rss Further neither of those options constrain active log files only archived ones.
If journald really is using a GB I would take a serious look at whats creating all of those logs.
answered Jan 25 at 9:33
jdwolfjdwolf
2,695216
add a comment |
Both SystemMaxUse and RuntimeMaxUse control disk space usage not memory usage. RuntimeMaxUse does apply to logs on the volatile file system (/run) but thats not captured by procstat.memory_rss Further neither of those options constrain active log files only archived ones.
If journald really is using a GB I would take a serious look at whats creating all of those logs.
answered Jan 25 at 9:33
jdwolfjdwolf
2,695216
Both SystemMaxUse and RuntimeMaxUse control disk space usage not memory usage. RuntimeMaxUse does apply to logs on the volatile file system (/run) but thats not captured by procstat.memory_rss Further neither of those options constrain active log files only archived ones.
If journald really is using a GB I would take a serious look at whats creating all of those logs.
answered Jan 25 at 9:33
jdwolfjdwolf
2,695216
answered Jan 25 at 9:33
jdwolfjdwolf
2,695216
answered Jan 25 at 9:33
jdwolfjdwolf
2,695216
answered Jan 25 at 9:33
jdwolfjdwolf
2,695216
2,695216
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496574%2fthe-systemd-journald-use-too-much-memory-and-dont-respect-systemmaxuse-and-runt%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Yep, it does grab a lot of RAM.
– K7AAY
Jan 24 at 23:37