Is it normal for process ids in Linux to continually increment into the high thousands after a few weeks?
I'm not an expert with Linux and have no idea how to begin debugging this issue or whether it's an issue at all.
I'm running a Linux server on a Windows machine (dual booting) and every few days running ps aux the process ids that get assigned get higher and higher. After about two weeks the process ids that get allocated are around 17,000.
Is this normal behavior?
I would've expected process ids to be reused.
linux
edited Feb 15 at 1:33
Anaksunaman
5,62821423
asked Feb 15 at 1:12
EdwarEdwar
61
add a comment |
I'm not an expert with Linux and have no idea how to begin debugging this issue or whether it's an issue at all.
I'm running a Linux server on a Windows machine (dual booting) and every few days running ps aux the process ids that get assigned get higher and higher. After about two weeks the process ids that get allocated are around 17,000.
Is this normal behavior?
I would've expected process ids to be reused.
linux
edited Feb 15 at 1:33
Anaksunaman
5,62821423
asked Feb 15 at 1:12
EdwarEdwar
61
add a comment |
I'm not an expert with Linux and have no idea how to begin debugging this issue or whether it's an issue at all.
I'm running a Linux server on a Windows machine (dual booting) and every few days running ps aux the process ids that get assigned get higher and higher. After about two weeks the process ids that get allocated are around 17,000.
Is this normal behavior?
I would've expected process ids to be reused.
linux
edited Feb 15 at 1:33
Anaksunaman
5,62821423
asked Feb 15 at 1:12
EdwarEdwar
61
I'm not an expert with Linux and have no idea how to begin debugging this issue or whether it's an issue at all.
I'm running a Linux server on a Windows machine (dual booting) and every few days running ps aux the process ids that get assigned get higher and higher. After about two weeks the process ids that get allocated are around 17,000.
Is this normal behavior?
I would've expected process ids to be reused.
linux
linux
edited Feb 15 at 1:33
Anaksunaman
5,62821423
asked Feb 15 at 1:12
EdwarEdwar
61
edited Feb 15 at 1:33
Anaksunaman
5,62821423
asked Feb 15 at 1:12
EdwarEdwar
61
edited Feb 15 at 1:33
Anaksunaman
5,62821423
edited Feb 15 at 1:33
Anaksunaman
5,62821423
edited Feb 15 at 1:33
Anaksunaman
5,62821423
5,62821423
asked Feb 15 at 1:12
EdwarEdwar
61
asked Feb 15 at 1:12
EdwarEdwar
61
asked Feb 15 at 1:12
EdwarEdwar
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is not a issue and is expected, normal behavior.
“I'm not an expert with linux and have no idea how to begin debugging this issue or weather its an issue at all.”
It’s not an issue. Linux ids run up to a specified amount and then roll backs back to the beginning after reaching that maximum number. ]
You can check this from the terminal by running this command:
cat /proc/sys/kernel/pid_max
The output I get on a an Ubuntu 16.04.5 server I manage is:
32768
As explained on the proc man page:
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in this file is one greater than the maximum PID). The default value for this file, 32768, results in the same range of PIDs as on earlier kernels. On 32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems, pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 million).
And that number is not significant for 99% of usage cases since you would only need to be concerned if you are somehow running 32,768 simultaneous processes at once with no chance of termination; ain’t a common thing to happen and doubt it can be done for any practical reason.
answered Feb 15 at 1:27
JakeGouldJakeGould
32.2k1098141
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f1405915%2fis-it-normal-for-process-ids-in-linux-to-continually-increment-into-the-high-tho%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
This is not a issue and is expected, normal behavior.
“I'm not an expert with linux and have no idea how to begin debugging this issue or weather its an issue at all.”
It’s not an issue. Linux ids run up to a specified amount and then roll backs back to the beginning after reaching that maximum number. ]
You can check this from the terminal by running this command:
cat /proc/sys/kernel/pid_max
The output I get on a an Ubuntu 16.04.5 server I manage is:
32768
As explained on the proc man page:
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in this file is one greater than the maximum PID). The default value for this file, 32768, results in the same range of PIDs as on earlier kernels. On 32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems, pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 million).
And that number is not significant for 99% of usage cases since you would only need to be concerned if you are somehow running 32,768 simultaneous processes at once with no chance of termination; ain’t a common thing to happen and doubt it can be done for any practical reason.
answered Feb 15 at 1:27
JakeGouldJakeGould
32.2k1098141
add a comment |
This is not a issue and is expected, normal behavior.
“I'm not an expert with linux and have no idea how to begin debugging this issue or weather its an issue at all.”
It’s not an issue. Linux ids run up to a specified amount and then roll backs back to the beginning after reaching that maximum number. ]
You can check this from the terminal by running this command:
cat /proc/sys/kernel/pid_max
The output I get on a an Ubuntu 16.04.5 server I manage is:
32768
As explained on the proc man page:
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in this file is one greater than the maximum PID). The default value for this file, 32768, results in the same range of PIDs as on earlier kernels. On 32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems, pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 million).
And that number is not significant for 99% of usage cases since you would only need to be concerned if you are somehow running 32,768 simultaneous processes at once with no chance of termination; ain’t a common thing to happen and doubt it can be done for any practical reason.
answered Feb 15 at 1:27
JakeGouldJakeGould
32.2k1098141
add a comment |
This is not a issue and is expected, normal behavior.
“I'm not an expert with linux and have no idea how to begin debugging this issue or weather its an issue at all.”
It’s not an issue. Linux ids run up to a specified amount and then roll backs back to the beginning after reaching that maximum number. ]
You can check this from the terminal by running this command:
cat /proc/sys/kernel/pid_max
The output I get on a an Ubuntu 16.04.5 server I manage is:
32768
As explained on the proc man page:
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in this file is one greater than the maximum PID). The default value for this file, 32768, results in the same range of PIDs as on earlier kernels. On 32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems, pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 million).
And that number is not significant for 99% of usage cases since you would only need to be concerned if you are somehow running 32,768 simultaneous processes at once with no chance of termination; ain’t a common thing to happen and doubt it can be done for any practical reason.
answered Feb 15 at 1:27
JakeGouldJakeGould
32.2k1098141
This is not a issue and is expected, normal behavior.
“I'm not an expert with linux and have no idea how to begin debugging this issue or weather its an issue at all.”
It’s not an issue. Linux ids run up to a specified amount and then roll backs back to the beginning after reaching that maximum number. ]
You can check this from the terminal by running this command:
cat /proc/sys/kernel/pid_max
The output I get on a an Ubuntu 16.04.5 server I manage is:
32768
As explained on the proc man page:
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in this file is one greater than the maximum PID). The default value for this file, 32768, results in the same range of PIDs as on earlier kernels. On 32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems, pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 million).
And that number is not significant for 99% of usage cases since you would only need to be concerned if you are somehow running 32,768 simultaneous processes at once with no chance of termination; ain’t a common thing to happen and doubt it can be done for any practical reason.
answered Feb 15 at 1:27
JakeGouldJakeGould
32.2k1098141
edited Feb 15 at 1:35
answered Feb 15 at 1:27
JakeGouldJakeGould
32.2k1098141
answered Feb 15 at 1:27
JakeGouldJakeGould
32.2k1098141
answered Feb 15 at 1:27
JakeGouldJakeGould
32.2k1098141
32.2k1098141
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1405915%2fis-it-normal-for-process-ids-in-linux-to-continually-increment-into-the-high-tho%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
