Detached GNU screen session unexpectedly killed upon terminal close












0














I am using GNU screen for years now on several servers with the same configuration and never ran into this strange problem:



After connecting to the server via SSH I start screen (without options). Then, no matter if I close my terminal application (iTerm or Terminal, by clicking on "the x" or via CMD+W
) or detach the screen session first using CTRL+A D, in any case the screen process gets killed and the session is gone. For debugging, I have explicitly set autodetach to on now, but that does not help.




  • Its not a Ubuntu 18 problem per se, as it does not show up on another Ubuntu 18 VM

  • It is not a problem with iTerm2 per se, as it shows up under Max OS Xs Terminal as well


Any idea how to quickly tackle this?










share|improve this question


















  • 1




    You could try and debug by attaching a strace -fo strace.log -p "$pid" where $pid is the pid of the screen server.
    – Stéphane Chazelas
    25 mins ago










  • Does it happen as well with screen -c /dev/null. Or when using a different value of $SHELL.
    – Stéphane Chazelas
    23 mins ago
















0














I am using GNU screen for years now on several servers with the same configuration and never ran into this strange problem:



After connecting to the server via SSH I start screen (without options). Then, no matter if I close my terminal application (iTerm or Terminal, by clicking on "the x" or via CMD+W
) or detach the screen session first using CTRL+A D, in any case the screen process gets killed and the session is gone. For debugging, I have explicitly set autodetach to on now, but that does not help.




  • Its not a Ubuntu 18 problem per se, as it does not show up on another Ubuntu 18 VM

  • It is not a problem with iTerm2 per se, as it shows up under Max OS Xs Terminal as well


Any idea how to quickly tackle this?










share|improve this question


















  • 1




    You could try and debug by attaching a strace -fo strace.log -p "$pid" where $pid is the pid of the screen server.
    – Stéphane Chazelas
    25 mins ago










  • Does it happen as well with screen -c /dev/null. Or when using a different value of $SHELL.
    – Stéphane Chazelas
    23 mins ago














0












0








0







I am using GNU screen for years now on several servers with the same configuration and never ran into this strange problem:



After connecting to the server via SSH I start screen (without options). Then, no matter if I close my terminal application (iTerm or Terminal, by clicking on "the x" or via CMD+W
) or detach the screen session first using CTRL+A D, in any case the screen process gets killed and the session is gone. For debugging, I have explicitly set autodetach to on now, but that does not help.




  • Its not a Ubuntu 18 problem per se, as it does not show up on another Ubuntu 18 VM

  • It is not a problem with iTerm2 per se, as it shows up under Max OS Xs Terminal as well


Any idea how to quickly tackle this?










share|improve this question













I am using GNU screen for years now on several servers with the same configuration and never ran into this strange problem:



After connecting to the server via SSH I start screen (without options). Then, no matter if I close my terminal application (iTerm or Terminal, by clicking on "the x" or via CMD+W
) or detach the screen session first using CTRL+A D, in any case the screen process gets killed and the session is gone. For debugging, I have explicitly set autodetach to on now, but that does not help.




  • Its not a Ubuntu 18 problem per se, as it does not show up on another Ubuntu 18 VM

  • It is not a problem with iTerm2 per se, as it shows up under Max OS Xs Terminal as well


Any idea how to quickly tackle this?







gnu-screen






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 35 mins ago









MischaMischa

1012




1012








  • 1




    You could try and debug by attaching a strace -fo strace.log -p "$pid" where $pid is the pid of the screen server.
    – Stéphane Chazelas
    25 mins ago










  • Does it happen as well with screen -c /dev/null. Or when using a different value of $SHELL.
    – Stéphane Chazelas
    23 mins ago














  • 1




    You could try and debug by attaching a strace -fo strace.log -p "$pid" where $pid is the pid of the screen server.
    – Stéphane Chazelas
    25 mins ago










  • Does it happen as well with screen -c /dev/null. Or when using a different value of $SHELL.
    – Stéphane Chazelas
    23 mins ago








1




1




You could try and debug by attaching a strace -fo strace.log -p "$pid" where $pid is the pid of the screen server.
– Stéphane Chazelas
25 mins ago




You could try and debug by attaching a strace -fo strace.log -p "$pid" where $pid is the pid of the screen server.
– Stéphane Chazelas
25 mins ago












Does it happen as well with screen -c /dev/null. Or when using a different value of $SHELL.
– Stéphane Chazelas
23 mins ago




Does it happen as well with screen -c /dev/null. Or when using a different value of $SHELL.
– Stéphane Chazelas
23 mins ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493024%2fdetached-gnu-screen-session-unexpectedly-killed-upon-terminal-close%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493024%2fdetached-gnu-screen-session-unexpectedly-killed-upon-terminal-close%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

濃尾地震