[IPython-User] notebook server dies when logging out of terminal

K.-Michael Aye kmichael.aye@gmail....
Thu Mar 14 15:54:47 CDT 2013

On 2013-03-14 19:34:41 +0000, K.-Michael Aye said:

> On 2013-03-13 21:47:47 +0000, Moritz Beber said:
>> Detach only Ctrl d and then exit the SSH session
> I just did exactly that:
> ipython notebook --profile=notebook
> (without backgrounding)
> then detached it with Ctrl-A and exited the SSH session.
> Then i logged into the https secured notebook springboard which was
> fine, but when i launched a notebook, the cells were already not
> executing. :(

I found at least out now, that it must have something to do with an X 
connection breakdown. Because:
1. I get an error message in the screen console where the notebook is 
running about failure to connect X.
2. When I shut down the notebook server, and immediately try to launch 
an xterm, it fails as well, both in- and outside of 'screen'.
3. I logged out of the remote machine, logged back in, tried that X is 
working via launching an xterm and relaunched the notebook server as 
above, detached and logged out, and currently it is working. It's just 
very likely it will stop working sometime later again, but now, when I 
notice, I will immediately check for the X connection to confirm the 


>> On 13 Mar 2013 14:21, "Vasco Tenner" <vasco@tenner.nl> wrote:
>> Hash: SHA1
>> Hi Moritz,
>> On 03/13/2013 02:28 AM, K.-Michael Aye wrote:
>>>> without them being affected. I highly recommend 'screen' as
>>>> Matthias already mentioned. You can even start the notebook
>>>> inside a screen session with a single command:
>>>> $ screen -dmS your_screen_session_name_here ipython notebook
>>>> --profile=nbserver
>>>> 'screen' is a great utility to learn anyway since you can have
>>>> "multiple terminals" through a single ssh session. When you later
>>>> want to interact with programs running inside of screen, simply
>>>> type:
>>>> $ screen -r or $ screen -r your_screen_session_name_here
>>>> if you have multiple screen instances.
>>> I even have issues when using screen as a base for the notebook
>>> server. It sometimes leaves the notebook 'inactive' (cells are not
>>> executed) UNTIL I would put the screen session where the notebook
>>> server is running into the foreground!
>> Do you put it in the background (CRTL-Z), or do you detach the screen
>> (CRTL-A D)?
>> Vasco
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>> sHM6cj507b4/w0z5r0VEMnXXaXqr3mlR0MkCV+iPKARtwmwSiUl/Ni+MPZ3pdn3P
>> fbO+54wvaaIhj9CORxTWzKFxCLuCJ536kk0c33vNDS98Kbl7DWUNzJ0rd59XawPx
>> /yx7mdHBf10ELFpNHL6PYUfn01d5OLDZ9vdf7pHGV64XAD5e3qe74S8zeN8+46qm
>> WbaoKyuxA7XtkOur9/gmy9x2eCkS/r8xSGPe60q07ZO6UYkoBRKbiXK8FJQfNt/b
>> 6Mfd7ykuIa1BEtyi9vDi8c0W2mLSdXrWpM/3CeVQcKDdoim6inmQktMv5xOsdKA=
>> =oyOO
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> IPython-User mailing list
>> IPython-User@scipy.org
>> http://mail.scipy.org/mailman/listinfo/ipython-user
>> _______________________________________________
>> IPython-User mailing list
>> IPython-User@scipy.org
>> http://mail.scipy.org/mailman/listinfo/ipython-user

More information about the IPython-User mailing list