Bug#825324: byobu: Byobu session closes on SSH disconnect
Ø tags 825324 -moreinfo -unreproducible Ø tags 825324 wontfix Ø thanks Ø Marking as wontfix as this is an issue due to tmux/screen and system Ø interactions, discussed in #825394. I sent this yesterday – but it doesn’t seem to reflect on the ticket , maybe I didn’t put all the right things into the to/subject fields… trying again… anyway : Closing the loop .. seems this is fixed in latest SID. Thanks Alex for your help engaging with the other teams to nail this down. I did also see the contribution : On Thu, 26 May 2016 14:43:56 +0900, SATOH Fumiyasu wrote: > systemd-logind in systemd version 230 set KillUserProcesses=yes > by default. See the logind(5) man page for details. logind.conf(5). I did not try it .. and if I have a vote I hope this is not going to be "standard" behavior .. I think a lot of people are going to be super confused if things like screen/tmux/nohup and byobu stop doing the thing we expect then to do .. ;) Anyway .. thanks a lot – happy ! Ivan. smime.p7s Description: S/MIME cryptographic signature
Bug#825324: byobu: Byobu session closes on SSH disconnect
tags 825324 -moreinfo -unreproducible tags 825324 wontfix thanks Marking as wontfix as this is an issue due to tmux/screen and systemd interactions, discussed in #825394. On Thu, May 26, 2016 at 2:17 AM, Ivan Frimmel wrote: > HI .. Thanks for your quick response. TBH .. I didn’t know where to > start. It looks like nohup and screen are doing the same thing. And > its only recent. I created a brand new user - enabled byobu and ran > something simple .. disconnect .. and the session closes completely. > > Screen sadly does the same thing from what I can see. Just to repeat - > byoby/screen and nohup are all doing it - I love Byobu - so this is > my first port of call ! :) ( please be gentle ) .. > > executing nohup /usr/bin/python /foo/pythonthing.py & works fine > while I am connected and then instantly terminates on disconnect of > the SSH. It is only very recent. And I don't think its anything I > did.. > > the baffling thing is that ROOT is unaffected by this disconnection .. > I wonder if their isn’t some new permission being pushd that makes > persistence a "option ?" seems silly to do that. > > Please help! > Tx > Ivan. > > > > > -Original Message- > From: Alex Chernyakhovsky [mailto:acher...@mit.edu] > Sent: Thursday, May 26, 2016 1:46 AM > To: Ivan Frimmel ; 825...@bugs.debian.org > Cc: Debian Bug Tracking System ; > cont...@bugs.debian.org > Subject: Re: Bug#825324: byobu: Byobu session closes on SSH disconnect > > tags 825324 moreinfo unreproducible > thanks > > Hi Ivan, > > Did your apt-get dist-upgrade include an update to tmux and/or screen? > byobu has not been pushed to sid or stretch recently, so I do not see > how it can be at fault. It is likely that some change in the > underlying tmux and/or screen backend you are using has changed. Try > `tmux list-sessions` or `screen -ls` depending on which byobu backend > you are using (tmux is currently the default) to see if the sessions > are present. Additionally, please try reproducing with tmux/screen > directly, without byobu. > > Sincerely, > -Alex > > > On Thu, May 26, 2016 at 1:19 AM, Ivan Frimmel wrote: >> Package: byobu >> Version: 5.87-1 >> Severity: important >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where >> appropriate *** >> >>* What led up to the situation? >> Did a apt-get dist-upgrade >>* What exactly did you do (or not do) that was effective (or >> ineffective)? >> root sessions will persist for some reason, but regular account >> sessions that used to allow disconnect of ssh now terminate immediately on >> disconnect and do not persist at all. I am not sure if byobu is crashing, I >> looked for dump files but here arent any that I can see. >>* What was the outcome of this action? >> I can't fix the problem. I searched all the byobu an bash >> documentation and /etc/profile and /etc/skel etc and I can't find anything >> that would be causing this all of a suddent. I don't think it's anything I >> did specifically. >>* What outcome did you expect instead? >> The sessions would persist after ssh disconnect. >> *** End of the template - remove these template lines *** >> >> >> -- System Information: >> Debian Release: stretch/sid >> APT prefers unstable >> APT policy: (500, 'unstable') >> Architecture: amd64 (x86_64) >> >> Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores) >> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> Init: systemd (via /run/systemd/system) >> >> Versions of packages byobu depends on: >> ii debconf [debconf-2.0] 1.5.59 >> ii gawk 1:4.1.3+dfsg-0.1 >> ii gettext-base 0.19.7-2 >> ii python 2.7.11-1 >> ii python-newt0.52.18-3 >> ii screen 4.3.1-3 >> ii tmux 2.2-2 >> >> Versions of packages byobu recommends: >> pn run-one >> ii screen 4.3.1-3 >> ii tmux 2.2-2 >> >> Versions of packages byobu suggests: >> pn apport >> pn ccze >> ii lsb-release 9.20160110 >> ii po-debconf 1.0.19 >> pn ttf-ubuntu-font-family >> pn update-notifier-common >> pn vim >> ii w3m 0.5.3-28 >> pn wireless-tools >> >> -- debconf information: >> byobu/launch-by-default: false
Bug#825324: byobu: Byobu session closes on SSH disconnect
HI .. Thanks for your quick response. TBH .. I didn’t know where to start. It looks like nohup and screen are doing the same thing. And its only recent. I created a brand new user - enabled byobu and ran something simple .. disconnect .. and the session closes completely. Screen sadly does the same thing from what I can see. Just to repeat - byoby/screen and nohup are all doing it - I love Byobu - so this is my first port of call ! :) ( please be gentle ) .. executing nohup /usr/bin/python /foo/pythonthing.py & works fine while I am connected and then instantly terminates on disconnect of the SSH. It is only very recent. And I don't think its anything I did.. the baffling thing is that ROOT is unaffected by this disconnection .. I wonder if their isn’t some new permission being pushd that makes persistence a "option ?" seems silly to do that. Please help! Tx Ivan. -Original Message- From: Alex Chernyakhovsky [mailto:acher...@mit.edu] Sent: Thursday, May 26, 2016 1:46 AM To: Ivan Frimmel ; 825...@bugs.debian.org Cc: Debian Bug Tracking System ; cont...@bugs.debian.org Subject: Re: Bug#825324: byobu: Byobu session closes on SSH disconnect tags 825324 moreinfo unreproducible thanks Hi Ivan, Did your apt-get dist-upgrade include an update to tmux and/or screen? byobu has not been pushed to sid or stretch recently, so I do not see how it can be at fault. It is likely that some change in the underlying tmux and/or screen backend you are using has changed. Try `tmux list-sessions` or `screen -ls` depending on which byobu backend you are using (tmux is currently the default) to see if the sessions are present. Additionally, please try reproducing with tmux/screen directly, without byobu. Sincerely, -Alex On Thu, May 26, 2016 at 1:19 AM, Ivan Frimmel wrote: > Package: byobu > Version: 5.87-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where > appropriate *** > >* What led up to the situation? > Did a apt-get dist-upgrade >* What exactly did you do (or not do) that was effective (or > ineffective)? > root sessions will persist for some reason, but regular account > sessions that used to allow disconnect of ssh now terminate immediately on > disconnect and do not persist at all. I am not sure if byobu is crashing, I > looked for dump files but here arent any that I can see. >* What was the outcome of this action? > I can't fix the problem. I searched all the byobu an bash > documentation and /etc/profile and /etc/skel etc and I can't find anything > that would be causing this all of a suddent. I don't think it's anything I > did specifically. >* What outcome did you expect instead? > The sessions would persist after ssh disconnect. > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages byobu depends on: > ii debconf [debconf-2.0] 1.5.59 > ii gawk 1:4.1.3+dfsg-0.1 > ii gettext-base 0.19.7-2 > ii python 2.7.11-1 > ii python-newt0.52.18-3 > ii screen 4.3.1-3 > ii tmux 2.2-2 > > Versions of packages byobu recommends: > pn run-one > ii screen 4.3.1-3 > ii tmux 2.2-2 > > Versions of packages byobu suggests: > pn apport > pn ccze > ii lsb-release 9.20160110 > ii po-debconf 1.0.19 > pn ttf-ubuntu-font-family > pn update-notifier-common > pn vim > ii w3m 0.5.3-28 > pn wireless-tools > > -- debconf information: > byobu/launch-by-default: false smime.p7s Description: S/MIME cryptographic signature
Bug#825324: byobu: Byobu session closes on SSH disconnect
Fix a typo. On Thu, 26 May 2016 14:43:56 +0900, SATOH Fumiyasu wrote: > systemd-logind in systemd version 230 set KillUserProcesses=yes > by default. See the logind(5) man page for details. logind.conf(5). -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA
Bug#825324: byobu: Byobu session closes on SSH disconnect
tags 825324 moreinfo unreproducible thanks Hi Ivan, Did your apt-get dist-upgrade include an update to tmux and/or screen? byobu has not been pushed to sid or stretch recently, so I do not see how it can be at fault. It is likely that some change in the underlying tmux and/or screen backend you are using has changed. Try `tmux list-sessions` or `screen -ls` depending on which byobu backend you are using (tmux is currently the default) to see if the sessions are present. Additionally, please try reproducing with tmux/screen directly, without byobu. Sincerely, -Alex On Thu, May 26, 2016 at 1:19 AM, Ivan Frimmel wrote: > Package: byobu > Version: 5.87-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > Did a apt-get dist-upgrade >* What exactly did you do (or not do) that was effective (or > ineffective)? > root sessions will persist for some reason, but regular account > sessions that used to allow disconnect of ssh now terminate immediately on > disconnect and do not persist at all. I am not sure if byobu is crashing, I > looked for dump files but here arent any that I can see. >* What was the outcome of this action? > I can't fix the problem. I searched all the byobu an bash > documentation and /etc/profile and /etc/skel etc and I can't find anything > that would be causing this all of a suddent. I don't think it's anything I > did specifically. >* What outcome did you expect instead? > The sessions would persist after ssh disconnect. > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages byobu depends on: > ii debconf [debconf-2.0] 1.5.59 > ii gawk 1:4.1.3+dfsg-0.1 > ii gettext-base 0.19.7-2 > ii python 2.7.11-1 > ii python-newt0.52.18-3 > ii screen 4.3.1-3 > ii tmux 2.2-2 > > Versions of packages byobu recommends: > pn run-one > ii screen 4.3.1-3 > ii tmux 2.2-2 > > Versions of packages byobu suggests: > pn apport > pn ccze > ii lsb-release 9.20160110 > ii po-debconf 1.0.19 > pn ttf-ubuntu-font-family > pn update-notifier-common > pn vim > ii w3m 0.5.3-28 > pn wireless-tools > > -- debconf information: > byobu/launch-by-default: false
Bug#825324: byobu: Byobu session closes on SSH disconnect
Hi, systemd-logind in systemd version 230 set KillUserProcesses=yes by default. See the logind(5) man page for details. Regards. -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA
Bug#825324: byobu: Byobu session closes on SSH disconnect
Package: byobu Version: 5.87-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Did a apt-get dist-upgrade * What exactly did you do (or not do) that was effective (or ineffective)? root sessions will persist for some reason, but regular account sessions that used to allow disconnect of ssh now terminate immediately on disconnect and do not persist at all. I am not sure if byobu is crashing, I looked for dump files but here arent any that I can see. * What was the outcome of this action? I can't fix the problem. I searched all the byobu an bash documentation and /etc/profile and /etc/skel etc and I can't find anything that would be causing this all of a suddent. I don't think it's anything I did specifically. * What outcome did you expect instead? The sessions would persist after ssh disconnect. *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages byobu depends on: ii debconf [debconf-2.0] 1.5.59 ii gawk 1:4.1.3+dfsg-0.1 ii gettext-base 0.19.7-2 ii python 2.7.11-1 ii python-newt0.52.18-3 ii screen 4.3.1-3 ii tmux 2.2-2 Versions of packages byobu recommends: pn run-one ii screen 4.3.1-3 ii tmux 2.2-2 Versions of packages byobu suggests: pn apport pn ccze ii lsb-release 9.20160110 ii po-debconf 1.0.19 pn ttf-ubuntu-font-family pn update-notifier-common pn vim ii w3m 0.5.3-28 pn wireless-tools -- debconf information: byobu/launch-by-default: false
