PuTTY Network Timeout Error
I'm using PuTTY on my Windows machine to use SSH on my university server. I run analyses that take up to 3 days to complete. I can connect and start the analyses but eventually get an error message 'PuTTY Network Error: Software caused connection abort'. I have problem solved this - the issue lies with the period of inactivity on PuTTY where it is running the analyses. The network connections ect are all fine. At the moment the only way I can get the analyses to complete is to press enter every couple of hours. This really is annoying as I have to get up during the night!
I'm not a computer whizz whatsoever and would really apprentice if anyone could suggest a solution.
Thanks :)
ssh putty
bumped to the homepage by Community♦ yesterday
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 using PuTTY on my Windows machine to use SSH on my university server. I run analyses that take up to 3 days to complete. I can connect and start the analyses but eventually get an error message 'PuTTY Network Error: Software caused connection abort'. I have problem solved this - the issue lies with the period of inactivity on PuTTY where it is running the analyses. The network connections ect are all fine. At the moment the only way I can get the analyses to complete is to press enter every couple of hours. This really is annoying as I have to get up during the night!
I'm not a computer whizz whatsoever and would really apprentice if anyone could suggest a solution.
Thanks :)
ssh putty
bumped to the homepage by Community♦ yesterday
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 using PuTTY on my Windows machine to use SSH on my university server. I run analyses that take up to 3 days to complete. I can connect and start the analyses but eventually get an error message 'PuTTY Network Error: Software caused connection abort'. I have problem solved this - the issue lies with the period of inactivity on PuTTY where it is running the analyses. The network connections ect are all fine. At the moment the only way I can get the analyses to complete is to press enter every couple of hours. This really is annoying as I have to get up during the night!
I'm not a computer whizz whatsoever and would really apprentice if anyone could suggest a solution.
Thanks :)
ssh putty
I'm using PuTTY on my Windows machine to use SSH on my university server. I run analyses that take up to 3 days to complete. I can connect and start the analyses but eventually get an error message 'PuTTY Network Error: Software caused connection abort'. I have problem solved this - the issue lies with the period of inactivity on PuTTY where it is running the analyses. The network connections ect are all fine. At the moment the only way I can get the analyses to complete is to press enter every couple of hours. This really is annoying as I have to get up during the night!
I'm not a computer whizz whatsoever and would really apprentice if anyone could suggest a solution.
Thanks :)
ssh putty
ssh putty
asked Oct 30 '16 at 10:13
Magpie101
112
112
bumped to the homepage by Community♦ yesterday
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♦ yesterday
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 |
2 Answers
2
active
oldest
votes
Either of the following methods (I prefer the second but YMMV)
- Prevent timeout
- Fiddle with Putty's settings such as
Enable TCP Keepalives
andseconds between keepalives
. - Tell the shell not to get bored (
unset TMOUT
)
- Fiddle with Putty's settings such as
- Change what you are doing so you don't hold a session open while inactive for several days
- output redirection (
>
) - disconnecting STDIN from tty (
&
) - prevent disconnection signalling the process (
nohup
)
- output redirection (
e.g.
nohup ./my_analysis > analysis.out 2> analysis.err &; exit;
You can check progress by e.g. logging in again and using
tail -f analysis.out
More complicated needs can often be accomodated using named pipes.
Other references
- how to make putty ssh connection never to timeout when user is idle?
- How to make putty to not break my session after some time?
- PuTTY and how to keep alive telnet session
Ah you're brilliant! Thanks ever so much, I can get a good nights sleep tonight :)
– Magpie101
Oct 30 '16 at 12:57
@Magpie101: Glad to help - See stackoverflow.com/help/someone-answers
– RedGrittyBrick
Oct 30 '16 at 14:02
add a comment |
You could also use screen
if it's available.
It would allow you do run whatever command within a screen session (which wouldn't timeout) and you'd be able to reconnect it later. A basic use could look like the following:
- Run
screen
- Start analysis
- Detach (Ctrl+A D) the screen (or wait for the timeout)
- Reconnect later using
screen -r
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%2f1140463%2fputty-network-timeout-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Either of the following methods (I prefer the second but YMMV)
- Prevent timeout
- Fiddle with Putty's settings such as
Enable TCP Keepalives
andseconds between keepalives
. - Tell the shell not to get bored (
unset TMOUT
)
- Fiddle with Putty's settings such as
- Change what you are doing so you don't hold a session open while inactive for several days
- output redirection (
>
) - disconnecting STDIN from tty (
&
) - prevent disconnection signalling the process (
nohup
)
- output redirection (
e.g.
nohup ./my_analysis > analysis.out 2> analysis.err &; exit;
You can check progress by e.g. logging in again and using
tail -f analysis.out
More complicated needs can often be accomodated using named pipes.
Other references
- how to make putty ssh connection never to timeout when user is idle?
- How to make putty to not break my session after some time?
- PuTTY and how to keep alive telnet session
Ah you're brilliant! Thanks ever so much, I can get a good nights sleep tonight :)
– Magpie101
Oct 30 '16 at 12:57
@Magpie101: Glad to help - See stackoverflow.com/help/someone-answers
– RedGrittyBrick
Oct 30 '16 at 14:02
add a comment |
Either of the following methods (I prefer the second but YMMV)
- Prevent timeout
- Fiddle with Putty's settings such as
Enable TCP Keepalives
andseconds between keepalives
. - Tell the shell not to get bored (
unset TMOUT
)
- Fiddle with Putty's settings such as
- Change what you are doing so you don't hold a session open while inactive for several days
- output redirection (
>
) - disconnecting STDIN from tty (
&
) - prevent disconnection signalling the process (
nohup
)
- output redirection (
e.g.
nohup ./my_analysis > analysis.out 2> analysis.err &; exit;
You can check progress by e.g. logging in again and using
tail -f analysis.out
More complicated needs can often be accomodated using named pipes.
Other references
- how to make putty ssh connection never to timeout when user is idle?
- How to make putty to not break my session after some time?
- PuTTY and how to keep alive telnet session
Ah you're brilliant! Thanks ever so much, I can get a good nights sleep tonight :)
– Magpie101
Oct 30 '16 at 12:57
@Magpie101: Glad to help - See stackoverflow.com/help/someone-answers
– RedGrittyBrick
Oct 30 '16 at 14:02
add a comment |
Either of the following methods (I prefer the second but YMMV)
- Prevent timeout
- Fiddle with Putty's settings such as
Enable TCP Keepalives
andseconds between keepalives
. - Tell the shell not to get bored (
unset TMOUT
)
- Fiddle with Putty's settings such as
- Change what you are doing so you don't hold a session open while inactive for several days
- output redirection (
>
) - disconnecting STDIN from tty (
&
) - prevent disconnection signalling the process (
nohup
)
- output redirection (
e.g.
nohup ./my_analysis > analysis.out 2> analysis.err &; exit;
You can check progress by e.g. logging in again and using
tail -f analysis.out
More complicated needs can often be accomodated using named pipes.
Other references
- how to make putty ssh connection never to timeout when user is idle?
- How to make putty to not break my session after some time?
- PuTTY and how to keep alive telnet session
Either of the following methods (I prefer the second but YMMV)
- Prevent timeout
- Fiddle with Putty's settings such as
Enable TCP Keepalives
andseconds between keepalives
. - Tell the shell not to get bored (
unset TMOUT
)
- Fiddle with Putty's settings such as
- Change what you are doing so you don't hold a session open while inactive for several days
- output redirection (
>
) - disconnecting STDIN from tty (
&
) - prevent disconnection signalling the process (
nohup
)
- output redirection (
e.g.
nohup ./my_analysis > analysis.out 2> analysis.err &; exit;
You can check progress by e.g. logging in again and using
tail -f analysis.out
More complicated needs can often be accomodated using named pipes.
Other references
- how to make putty ssh connection never to timeout when user is idle?
- How to make putty to not break my session after some time?
- PuTTY and how to keep alive telnet session
edited May 23 '17 at 12:41
Community♦
1
1
answered Oct 30 '16 at 10:50
RedGrittyBrick
66.5k12105160
66.5k12105160
Ah you're brilliant! Thanks ever so much, I can get a good nights sleep tonight :)
– Magpie101
Oct 30 '16 at 12:57
@Magpie101: Glad to help - See stackoverflow.com/help/someone-answers
– RedGrittyBrick
Oct 30 '16 at 14:02
add a comment |
Ah you're brilliant! Thanks ever so much, I can get a good nights sleep tonight :)
– Magpie101
Oct 30 '16 at 12:57
@Magpie101: Glad to help - See stackoverflow.com/help/someone-answers
– RedGrittyBrick
Oct 30 '16 at 14:02
Ah you're brilliant! Thanks ever so much, I can get a good nights sleep tonight :)
– Magpie101
Oct 30 '16 at 12:57
Ah you're brilliant! Thanks ever so much, I can get a good nights sleep tonight :)
– Magpie101
Oct 30 '16 at 12:57
@Magpie101: Glad to help - See stackoverflow.com/help/someone-answers
– RedGrittyBrick
Oct 30 '16 at 14:02
@Magpie101: Glad to help - See stackoverflow.com/help/someone-answers
– RedGrittyBrick
Oct 30 '16 at 14:02
add a comment |
You could also use screen
if it's available.
It would allow you do run whatever command within a screen session (which wouldn't timeout) and you'd be able to reconnect it later. A basic use could look like the following:
- Run
screen
- Start analysis
- Detach (Ctrl+A D) the screen (or wait for the timeout)
- Reconnect later using
screen -r
add a comment |
You could also use screen
if it's available.
It would allow you do run whatever command within a screen session (which wouldn't timeout) and you'd be able to reconnect it later. A basic use could look like the following:
- Run
screen
- Start analysis
- Detach (Ctrl+A D) the screen (or wait for the timeout)
- Reconnect later using
screen -r
add a comment |
You could also use screen
if it's available.
It would allow you do run whatever command within a screen session (which wouldn't timeout) and you'd be able to reconnect it later. A basic use could look like the following:
- Run
screen
- Start analysis
- Detach (Ctrl+A D) the screen (or wait for the timeout)
- Reconnect later using
screen -r
You could also use screen
if it's available.
It would allow you do run whatever command within a screen session (which wouldn't timeout) and you'd be able to reconnect it later. A basic use could look like the following:
- Run
screen
- Start analysis
- Detach (Ctrl+A D) the screen (or wait for the timeout)
- Reconnect later using
screen -r
answered Nov 14 '16 at 14:42
Seth
6,03311128
6,03311128
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1140463%2fputty-network-timeout-error%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