“screen” exit by itself after broken ssh?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm on Mac and ssh to a server (Ubuntu 18.04) to run a long Python job. I started the job in a screen session and then detached the screen.
After a few minutes, I receive a message packet_write_wait: Connection to 128.122.136.109 port 22: Broken pipe from my local terminal.
Then I reconnected to the server using ssh, and when I try to resume the screen session I got There is no screen to be resumed..
This is weird as I suppose screen should still be running even after the ssh is broken? This has also happened at least three times so it's not an incident.
What could go wrong, and how should I debug and repair it? Thanks!
ssh screen
asked Feb 13 at 20:29
yuqliyuqli
1033
add a comment |
I'm on Mac and ssh to a server (Ubuntu 18.04) to run a long Python job. I started the job in a screen session and then detached the screen.
After a few minutes, I receive a message packet_write_wait: Connection to 128.122.136.109 port 22: Broken pipe from my local terminal.
Then I reconnected to the server using ssh, and when I try to resume the screen session I got There is no screen to be resumed..
This is weird as I suppose screen should still be running even after the ssh is broken? This has also happened at least three times so it's not an incident.
What could go wrong, and how should I debug and repair it? Thanks!
ssh screen
asked Feb 13 at 20:29
yuqliyuqli
1033
1
Any chance the server crashed/was rebooted during that interval? Did you check the uptime?
– BowlOfRed
Feb 13 at 22:06
@BowlOfRed yes this is probably the issue. The uptime is suspiciously short. Thanks for the advice!
– yuqli
Feb 14 at 22:02
add a comment |
I'm on Mac and ssh to a server (Ubuntu 18.04) to run a long Python job. I started the job in a screen session and then detached the screen.
After a few minutes, I receive a message packet_write_wait: Connection to 128.122.136.109 port 22: Broken pipe from my local terminal.
Then I reconnected to the server using ssh, and when I try to resume the screen session I got There is no screen to be resumed..
This is weird as I suppose screen should still be running even after the ssh is broken? This has also happened at least three times so it's not an incident.
What could go wrong, and how should I debug and repair it? Thanks!
ssh screen
asked Feb 13 at 20:29
yuqliyuqli
1033
I'm on Mac and ssh to a server (Ubuntu 18.04) to run a long Python job. I started the job in a screen session and then detached the screen.
After a few minutes, I receive a message packet_write_wait: Connection to 128.122.136.109 port 22: Broken pipe from my local terminal.
Then I reconnected to the server using ssh, and when I try to resume the screen session I got There is no screen to be resumed..
This is weird as I suppose screen should still be running even after the ssh is broken? This has also happened at least three times so it's not an incident.
What could go wrong, and how should I debug and repair it? Thanks!
ssh screen
ssh screen
asked Feb 13 at 20:29
yuqliyuqli
1033
asked Feb 13 at 20:29
yuqliyuqli
1033
asked Feb 13 at 20:29
yuqliyuqli
1033
asked Feb 13 at 20:29
yuqliyuqli
1033
asked Feb 13 at 20:29
yuqliyuqli
1033
1033
1
Any chance the server crashed/was rebooted during that interval? Did you check the uptime?
– BowlOfRed
Feb 13 at 22:06
@BowlOfRed yes this is probably the issue. The uptime is suspiciously short. Thanks for the advice!
– yuqli
Feb 14 at 22:02
add a comment |
1
Any chance the server crashed/was rebooted during that interval? Did you check the uptime?
– BowlOfRed
Feb 13 at 22:06
@BowlOfRed yes this is probably the issue. The uptime is suspiciously short. Thanks for the advice!
– yuqli
Feb 14 at 22:02
1
1
Any chance the server crashed/was rebooted during that interval? Did you check the uptime?
– BowlOfRed
Feb 13 at 22:06
Any chance the server crashed/was rebooted during that interval? Did you check the uptime?
– BowlOfRed
Feb 13 at 22:06
@BowlOfRed yes this is probably the issue. The uptime is suspiciously short. Thanks for the advice!
– yuqli
Feb 14 at 22:02
@BowlOfRed yes this is probably the issue. The uptime is suspiciously short. Thanks for the advice!
– yuqli
Feb 14 at 22:02
add a comment |
1 Answer
1
active
oldest
votes
Both the ssh connection and the screen session are handled by running processes and both will be lost with a server reboot. You should check the server uptime, or look for boot indications in the messages file.
If it has rebooted, you'll need to diagnose that separately.
answered Feb 14 at 22:13
BowlOfRedBowlOfRed
20115
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',
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%2faskubuntu.com%2fquestions%2f1118043%2fscreen-exit-by-itself-after-broken-ssh%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
Both the ssh connection and the screen session are handled by running processes and both will be lost with a server reboot. You should check the server uptime, or look for boot indications in the messages file.
If it has rebooted, you'll need to diagnose that separately.
answered Feb 14 at 22:13
BowlOfRedBowlOfRed
20115
add a comment |
Both the ssh connection and the screen session are handled by running processes and both will be lost with a server reboot. You should check the server uptime, or look for boot indications in the messages file.
If it has rebooted, you'll need to diagnose that separately.
answered Feb 14 at 22:13
BowlOfRedBowlOfRed
20115
add a comment |
Both the ssh connection and the screen session are handled by running processes and both will be lost with a server reboot. You should check the server uptime, or look for boot indications in the messages file.
If it has rebooted, you'll need to diagnose that separately.
answered Feb 14 at 22:13
BowlOfRedBowlOfRed
20115
Both the ssh connection and the screen session are handled by running processes and both will be lost with a server reboot. You should check the server uptime, or look for boot indications in the messages file.
If it has rebooted, you'll need to diagnose that separately.
answered Feb 14 at 22:13
BowlOfRedBowlOfRed
20115
answered Feb 14 at 22:13
BowlOfRedBowlOfRed
20115
answered Feb 14 at 22:13
BowlOfRedBowlOfRed
20115
answered Feb 14 at 22:13
BowlOfRedBowlOfRed
20115
20115
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.
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%2f1118043%2fscreen-exit-by-itself-after-broken-ssh%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
Any chance the server crashed/was rebooted during that interval? Did you check the uptime?
– BowlOfRed
Feb 13 at 22:06
@BowlOfRed yes this is probably the issue. The uptime is suspiciously short. Thanks for the advice!
– yuqli
Feb 14 at 22:02