CPU spikes to 100% when using openSSH for windows
I am using openSSH for windows (OpenSSH 7.1p1-1). I noticed that after few days that the sshd.exe processes are at the range of 20% cpu the spike to 100% utilization all taken by the processes. i googled the issue and looked here and found one answer saying that when running openSSH along with an antivirus they can compete for resources, the thing is i do not have anti virus on this windows machine
Has anyone encountered this issue before?
windows openssh
add a comment |
I am using openSSH for windows (OpenSSH 7.1p1-1). I noticed that after few days that the sshd.exe processes are at the range of 20% cpu the spike to 100% utilization all taken by the processes. i googled the issue and looked here and found one answer saying that when running openSSH along with an antivirus they can compete for resources, the thing is i do not have anti virus on this windows machine
Has anyone encountered this issue before?
windows openssh
what is going on in logs? How many sshd precesses do you see there?
– Jakuje
Dec 22 '15 at 9:27
1
You can download Sysinternals suite to see what's going on with the processes, specifically you can check Process Monitor to check IO operations etc. and Process Explorer for process state such as threads etc.
– yonisha
Jun 13 '16 at 22:38
1
I would run:procdump -ma processname
(docs.microsoft.com/sysinternals/downloads/procdump) to get 2 or 3 dumps when it has the issue. You can get procdump to do this for you with switches if needed. Then open them in Windbg (There is a Store app, but I would set the Windows SDK for your platform and install the Debugging Tools). Run!runaway
against the dumps to find the busy threads. Then look at the stacks of these threads to try and glean what they are doing, which modules are involved etc.. I would suggest performing the following on a few dumps to see if it's consistent.
– HelpingHand
Jul 1 '18 at 12:22
add a comment |
I am using openSSH for windows (OpenSSH 7.1p1-1). I noticed that after few days that the sshd.exe processes are at the range of 20% cpu the spike to 100% utilization all taken by the processes. i googled the issue and looked here and found one answer saying that when running openSSH along with an antivirus they can compete for resources, the thing is i do not have anti virus on this windows machine
Has anyone encountered this issue before?
windows openssh
I am using openSSH for windows (OpenSSH 7.1p1-1). I noticed that after few days that the sshd.exe processes are at the range of 20% cpu the spike to 100% utilization all taken by the processes. i googled the issue and looked here and found one answer saying that when running openSSH along with an antivirus they can compete for resources, the thing is i do not have anti virus on this windows machine
Has anyone encountered this issue before?
windows openssh
windows openssh
edited Dec 22 '15 at 8:39
DavidPostill♦
107k27234268
107k27234268
asked Dec 22 '15 at 8:34
docdoc
434
434
what is going on in logs? How many sshd precesses do you see there?
– Jakuje
Dec 22 '15 at 9:27
1
You can download Sysinternals suite to see what's going on with the processes, specifically you can check Process Monitor to check IO operations etc. and Process Explorer for process state such as threads etc.
– yonisha
Jun 13 '16 at 22:38
1
I would run:procdump -ma processname
(docs.microsoft.com/sysinternals/downloads/procdump) to get 2 or 3 dumps when it has the issue. You can get procdump to do this for you with switches if needed. Then open them in Windbg (There is a Store app, but I would set the Windows SDK for your platform and install the Debugging Tools). Run!runaway
against the dumps to find the busy threads. Then look at the stacks of these threads to try and glean what they are doing, which modules are involved etc.. I would suggest performing the following on a few dumps to see if it's consistent.
– HelpingHand
Jul 1 '18 at 12:22
add a comment |
what is going on in logs? How many sshd precesses do you see there?
– Jakuje
Dec 22 '15 at 9:27
1
You can download Sysinternals suite to see what's going on with the processes, specifically you can check Process Monitor to check IO operations etc. and Process Explorer for process state such as threads etc.
– yonisha
Jun 13 '16 at 22:38
1
I would run:procdump -ma processname
(docs.microsoft.com/sysinternals/downloads/procdump) to get 2 or 3 dumps when it has the issue. You can get procdump to do this for you with switches if needed. Then open them in Windbg (There is a Store app, but I would set the Windows SDK for your platform and install the Debugging Tools). Run!runaway
against the dumps to find the busy threads. Then look at the stacks of these threads to try and glean what they are doing, which modules are involved etc.. I would suggest performing the following on a few dumps to see if it's consistent.
– HelpingHand
Jul 1 '18 at 12:22
what is going on in logs? How many sshd precesses do you see there?
– Jakuje
Dec 22 '15 at 9:27
what is going on in logs? How many sshd precesses do you see there?
– Jakuje
Dec 22 '15 at 9:27
1
1
You can download Sysinternals suite to see what's going on with the processes, specifically you can check Process Monitor to check IO operations etc. and Process Explorer for process state such as threads etc.
– yonisha
Jun 13 '16 at 22:38
You can download Sysinternals suite to see what's going on with the processes, specifically you can check Process Monitor to check IO operations etc. and Process Explorer for process state such as threads etc.
– yonisha
Jun 13 '16 at 22:38
1
1
I would run:
procdump -ma processname
(docs.microsoft.com/sysinternals/downloads/procdump) to get 2 or 3 dumps when it has the issue. You can get procdump to do this for you with switches if needed. Then open them in Windbg (There is a Store app, but I would set the Windows SDK for your platform and install the Debugging Tools). Run !runaway
against the dumps to find the busy threads. Then look at the stacks of these threads to try and glean what they are doing, which modules are involved etc.. I would suggest performing the following on a few dumps to see if it's consistent.– HelpingHand
Jul 1 '18 at 12:22
I would run:
procdump -ma processname
(docs.microsoft.com/sysinternals/downloads/procdump) to get 2 or 3 dumps when it has the issue. You can get procdump to do this for you with switches if needed. Then open them in Windbg (There is a Store app, but I would set the Windows SDK for your platform and install the Debugging Tools). Run !runaway
against the dumps to find the busy threads. Then look at the stacks of these threads to try and glean what they are doing, which modules are involved etc.. I would suggest performing the following on a few dumps to see if it's consistent.– HelpingHand
Jul 1 '18 at 12:22
add a comment |
1 Answer
1
active
oldest
votes
If you're using Windows 10 you could try installing Windows's Official OpenSSH Client (and server too if you'd like remote access to Windows over SSH).
From Control Panel -> Apps, in Apps & Features tab, click on Manage Optional Features and add OpenSSH Client.
You might have to uninstall the other client, run ssh.exe using full path or adjust your %Path% to run the correct version. Once installed Windows's version of ssh.exe should be installed in %windir%System32OpenSSH
with this directory added to your %Path%.
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%2f1016655%2fcpu-spikes-to-100-when-using-openssh-for-windows%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
If you're using Windows 10 you could try installing Windows's Official OpenSSH Client (and server too if you'd like remote access to Windows over SSH).
From Control Panel -> Apps, in Apps & Features tab, click on Manage Optional Features and add OpenSSH Client.
You might have to uninstall the other client, run ssh.exe using full path or adjust your %Path% to run the correct version. Once installed Windows's version of ssh.exe should be installed in %windir%System32OpenSSH
with this directory added to your %Path%.
add a comment |
If you're using Windows 10 you could try installing Windows's Official OpenSSH Client (and server too if you'd like remote access to Windows over SSH).
From Control Panel -> Apps, in Apps & Features tab, click on Manage Optional Features and add OpenSSH Client.
You might have to uninstall the other client, run ssh.exe using full path or adjust your %Path% to run the correct version. Once installed Windows's version of ssh.exe should be installed in %windir%System32OpenSSH
with this directory added to your %Path%.
add a comment |
If you're using Windows 10 you could try installing Windows's Official OpenSSH Client (and server too if you'd like remote access to Windows over SSH).
From Control Panel -> Apps, in Apps & Features tab, click on Manage Optional Features and add OpenSSH Client.
You might have to uninstall the other client, run ssh.exe using full path or adjust your %Path% to run the correct version. Once installed Windows's version of ssh.exe should be installed in %windir%System32OpenSSH
with this directory added to your %Path%.
If you're using Windows 10 you could try installing Windows's Official OpenSSH Client (and server too if you'd like remote access to Windows over SSH).
From Control Panel -> Apps, in Apps & Features tab, click on Manage Optional Features and add OpenSSH Client.
You might have to uninstall the other client, run ssh.exe using full path or adjust your %Path% to run the correct version. Once installed Windows's version of ssh.exe should be installed in %windir%System32OpenSSH
with this directory added to your %Path%.
answered Feb 16 at 5:29
Thomas Guyot-SionnestThomas Guyot-Sionnest
26027
26027
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%2f1016655%2fcpu-spikes-to-100-when-using-openssh-for-windows%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
what is going on in logs? How many sshd precesses do you see there?
– Jakuje
Dec 22 '15 at 9:27
1
You can download Sysinternals suite to see what's going on with the processes, specifically you can check Process Monitor to check IO operations etc. and Process Explorer for process state such as threads etc.
– yonisha
Jun 13 '16 at 22:38
1
I would run:
procdump -ma processname
(docs.microsoft.com/sysinternals/downloads/procdump) to get 2 or 3 dumps when it has the issue. You can get procdump to do this for you with switches if needed. Then open them in Windbg (There is a Store app, but I would set the Windows SDK for your platform and install the Debugging Tools). Run!runaway
against the dumps to find the busy threads. Then look at the stacks of these threads to try and glean what they are doing, which modules are involved etc.. I would suggest performing the following on a few dumps to see if it's consistent.– HelpingHand
Jul 1 '18 at 12:22