Running a process through SSH command and keeping it alive
up vote
0
down vote
favorite
I try running a python program on a remote server using nohup as explained in:
How to keep processes running after ending ssh session?
When I do ssh server -C "nohup prog.py &", the python program exists with BrokenPipeError: [Errno 32] Broken pipe.
When I do ssh server -C "nohup prog.py", the python program runs smoothly, but the ssh connection obviously stays alive. Once I ctrl^c it, I get the Broken pipe error again.
Obviously I'm missing something here, but no idea what.
server ssh python nohup
asked Dec 2 at 9:06
Elad Weiss
1466
add a comment |
up vote
0
down vote
favorite
I try running a python program on a remote server using nohup as explained in:
How to keep processes running after ending ssh session?
When I do ssh server -C "nohup prog.py &", the python program exists with BrokenPipeError: [Errno 32] Broken pipe.
When I do ssh server -C "nohup prog.py", the python program runs smoothly, but the ssh connection obviously stays alive. Once I ctrl^c it, I get the Broken pipe error again.
Obviously I'm missing something here, but no idea what.
server ssh python nohup
asked Dec 2 at 9:06
Elad Weiss
1466
1
Is the program writing output to stdout/stderr? If so did you try to reroute that to file or /dev/null?
– xenoid
Dec 2 at 9:24
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I try running a python program on a remote server using nohup as explained in:
How to keep processes running after ending ssh session?
When I do ssh server -C "nohup prog.py &", the python program exists with BrokenPipeError: [Errno 32] Broken pipe.
When I do ssh server -C "nohup prog.py", the python program runs smoothly, but the ssh connection obviously stays alive. Once I ctrl^c it, I get the Broken pipe error again.
Obviously I'm missing something here, but no idea what.
server ssh python nohup
asked Dec 2 at 9:06
Elad Weiss
1466
I try running a python program on a remote server using nohup as explained in:
How to keep processes running after ending ssh session?
When I do ssh server -C "nohup prog.py &", the python program exists with BrokenPipeError: [Errno 32] Broken pipe.
When I do ssh server -C "nohup prog.py", the python program runs smoothly, but the ssh connection obviously stays alive. Once I ctrl^c it, I get the Broken pipe error again.
Obviously I'm missing something here, but no idea what.
server ssh python nohup
server ssh python nohup
asked Dec 2 at 9:06
Elad Weiss
1466
asked Dec 2 at 9:06
Elad Weiss
1466
asked Dec 2 at 9:06
Elad Weiss
1466
asked Dec 2 at 9:06
Elad Weiss
1466
asked Dec 2 at 9:06
Elad Weiss
1466
1466
1
Is the program writing output to stdout/stderr? If so did you try to reroute that to file or /dev/null?
– xenoid
Dec 2 at 9:24
add a comment |
1
Is the program writing output to stdout/stderr? If so did you try to reroute that to file or /dev/null?
– xenoid
Dec 2 at 9:24
1
1
Is the program writing output to stdout/stderr? If so did you try to reroute that to file or /dev/null?
– xenoid
Dec 2 at 9:24
Is the program writing output to stdout/stderr? If so did you try to reroute that to file or /dev/null?
– xenoid
Dec 2 at 9:24
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
Like xenoid pointed out in the comment, redirecting the stdout/stderr to anywhere other than the screen fixed the problem.
answered Dec 2 at 9:49
Elad Weiss
1466
add a comment |
up vote
0
down vote
Try GNU Screen (ssh server -t "screen python prog.py").
Screen will protect the process from dying. Use ^A then d to detach and screen -xr to reattach.
answered Dec 2 at 11:08
Mm2PL
11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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',
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%2faskubuntu.com%2fquestions%2f1097851%2frunning-a-process-through-ssh-command-and-keeping-it-alive%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
up vote
0
down vote
Like xenoid pointed out in the comment, redirecting the stdout/stderr to anywhere other than the screen fixed the problem.
answered Dec 2 at 9:49
Elad Weiss
1466
add a comment |
up vote
0
down vote
Like xenoid pointed out in the comment, redirecting the stdout/stderr to anywhere other than the screen fixed the problem.
answered Dec 2 at 9:49
Elad Weiss
1466
add a comment |
up vote
0
down vote
up vote
0
down vote
Like xenoid pointed out in the comment, redirecting the stdout/stderr to anywhere other than the screen fixed the problem.
answered Dec 2 at 9:49
Elad Weiss
1466
Like xenoid pointed out in the comment, redirecting the stdout/stderr to anywhere other than the screen fixed the problem.
answered Dec 2 at 9:49
Elad Weiss
1466
answered Dec 2 at 9:49
Elad Weiss
1466
answered Dec 2 at 9:49
Elad Weiss
1466
answered Dec 2 at 9:49
Elad Weiss
1466
1466
add a comment |
add a comment |
up vote
0
down vote
Try GNU Screen (ssh server -t "screen python prog.py").
Screen will protect the process from dying. Use ^A then d to detach and screen -xr to reattach.
answered Dec 2 at 11:08
Mm2PL
11
add a comment |
up vote
0
down vote
Try GNU Screen (ssh server -t "screen python prog.py").
Screen will protect the process from dying. Use ^A then d to detach and screen -xr to reattach.
answered Dec 2 at 11:08
Mm2PL
11
add a comment |
up vote
0
down vote
up vote
0
down vote
Try GNU Screen (ssh server -t "screen python prog.py").
Screen will protect the process from dying. Use ^A then d to detach and screen -xr to reattach.
answered Dec 2 at 11:08
Mm2PL
11
Try GNU Screen (ssh server -t "screen python prog.py").
Screen will protect the process from dying. Use ^A then d to detach and screen -xr to reattach.
answered Dec 2 at 11:08
Mm2PL
11
answered Dec 2 at 11:08
Mm2PL
11
answered Dec 2 at 11:08
Mm2PL
11
answered Dec 2 at 11:08
Mm2PL
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1097851%2frunning-a-process-through-ssh-command-and-keeping-it-alive%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
1
Is the program writing output to stdout/stderr? If so did you try to reroute that to file or /dev/null?
– xenoid
Dec 2 at 9:24