Completely disable oom killer
I'm having some intermittent issues that appear to be related to the oomkiller purging some child processes, but I can't see why.
Is there a convenient way that I can suppress all oomkiller activity through sysctl?
I've found some instructions that say these should work, but they do not exist for me.
sysctl -w memory.oom_control=1
sysctl -w vm.oom-kill=0
I have also seen these two being suggested, but the oom killer carries right on.
sysctl vm.overcommit_memory=2
sysctl vm.overcommit_kbytes=0
out-of-memory
bumped to the homepage by Community♦ 4 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm having some intermittent issues that appear to be related to the oomkiller purging some child processes, but I can't see why.
Is there a convenient way that I can suppress all oomkiller activity through sysctl?
I've found some instructions that say these should work, but they do not exist for me.
sysctl -w memory.oom_control=1
sysctl -w vm.oom-kill=0
I have also seen these two being suggested, but the oom killer carries right on.
sysctl vm.overcommit_memory=2
sysctl vm.overcommit_kbytes=0
out-of-memory
bumped to the homepage by Community♦ 4 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm having some intermittent issues that appear to be related to the oomkiller purging some child processes, but I can't see why.
Is there a convenient way that I can suppress all oomkiller activity through sysctl?
I've found some instructions that say these should work, but they do not exist for me.
sysctl -w memory.oom_control=1
sysctl -w vm.oom-kill=0
I have also seen these two being suggested, but the oom killer carries right on.
sysctl vm.overcommit_memory=2
sysctl vm.overcommit_kbytes=0
out-of-memory
I'm having some intermittent issues that appear to be related to the oomkiller purging some child processes, but I can't see why.
Is there a convenient way that I can suppress all oomkiller activity through sysctl?
I've found some instructions that say these should work, but they do not exist for me.
sysctl -w memory.oom_control=1
sysctl -w vm.oom-kill=0
I have also seen these two being suggested, but the oom killer carries right on.
sysctl vm.overcommit_memory=2
sysctl vm.overcommit_kbytes=0
out-of-memory
out-of-memory
edited Mar 20 '18 at 1:49
thrig
25.2k23257
25.2k23257
asked Mar 19 '18 at 20:39
Brando___Brando___
133
133
bumped to the homepage by Community♦ 4 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 4 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You could use /proc/sys/vm/overcommit_memory
(see proc(5)), e.g.
echo 0 > /proc/sys/vm/overcommit_memory
as root to disable it. See also the kernel's Documentation/vm/overcommit-accounting
(If you are running an old kernel, consider upgrading it)
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%2f432171%2fcompletely-disable-oom-killer%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
You could use /proc/sys/vm/overcommit_memory
(see proc(5)), e.g.
echo 0 > /proc/sys/vm/overcommit_memory
as root to disable it. See also the kernel's Documentation/vm/overcommit-accounting
(If you are running an old kernel, consider upgrading it)
add a comment |
You could use /proc/sys/vm/overcommit_memory
(see proc(5)), e.g.
echo 0 > /proc/sys/vm/overcommit_memory
as root to disable it. See also the kernel's Documentation/vm/overcommit-accounting
(If you are running an old kernel, consider upgrading it)
add a comment |
You could use /proc/sys/vm/overcommit_memory
(see proc(5)), e.g.
echo 0 > /proc/sys/vm/overcommit_memory
as root to disable it. See also the kernel's Documentation/vm/overcommit-accounting
(If you are running an old kernel, consider upgrading it)
You could use /proc/sys/vm/overcommit_memory
(see proc(5)), e.g.
echo 0 > /proc/sys/vm/overcommit_memory
as root to disable it. See also the kernel's Documentation/vm/overcommit-accounting
(If you are running an old kernel, consider upgrading it)
answered Mar 20 '18 at 5:43
Basile StarynkevitchBasile Starynkevitch
8,1312041
8,1312041
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%2f432171%2fcompletely-disable-oom-killer%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