Open dbl001 opened 7 years ago
takluyver
commented
7 years ago Is it actually telling you that the kernel died, or just failing to connect? If the kernels are dying without printing any error to the terminal, that usually means there's something wrong at the C level which is causing the process to crash. If it can't connect, that means there's a problem establishing the websocket connection, which might be caused by some layer between you and the server (e.g. a proxy).
dbl001
commented
7 years ago I don’t see the kernel dying. In fact, the ps output shows the processes are still running.
I adjusted the config file to change Jupyter to accept remote connections
(e.g. Localhost ==> my EC2 elastic IP address.)
Perhaps there’s still something wrong in my configuration settings.
On Apr 11, 2017, at 3:14 AM, Thomas Kluyver notifications@github.com wrote:
Is it actually telling you that the kernel died, or just failing to connect? If the kernels are dying without printing any error to the terminal, that usually means there's something wrong at the C level which is causing the process to crash. If it can't connect, that means there's a problem establishing the websocket connection, which might be caused by some layer between you and the server (e.g. a proxy).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jupyter/notebook/issues/2386#issuecomment-293213916, or mute the thread https://github.com/notifications/unsubscribe-auth/AC9i24ZELZuaYP3mktePBuZqI0H4zzfdks5ru1J3gaJpZM4M3Nqt.
dbl001
commented
7 years ago Here’s my .jupyter/jupyter_notebook_config.py file:
On Apr 11, 2017, at 3:38 AM, David Laxer davidl@softintel.com wrote:
I don’t see the kernel dying. In fact, the ps output shows the processes are still running. I adjusted the config file to change Jupyter to accept remote connections (e.g. Localhost ==> my EC2 elastic IP address.)
Perhaps there’s still something wrong in my configuration settings.On Apr 11, 2017, at 3:14 AM, Thomas Kluyver <notifications@github.com mailto:notifications@github.com> wrote:
Is it actually telling you that the kernel died, or just failing to connect? If the kernels are dying without printing any error to the terminal, that usually means there's something wrong at the C level which is causing the process to crash. If it can't connect, that means there's a problem establishing the websocket connection, which might be caused by some layer between you and the server (e.g. a proxy).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jupyter/notebook/issues/2386#issuecomment-293213916, or mute the thread https://github.com/notifications/unsubscribe-auth/AC9i24ZELZuaYP3mktePBuZqI0H4zzfdks5ru1J3gaJpZM4M3Nqt.
abhinavkgp
commented
7 years ago I have faced similar issue couple of times in the past. In one case, it was happening since I was behind a corporate firewall. In another case, it got resolved by switching to another browser (A weird hack but it worked!)
dbl001
commented
7 years ago What OS were you using?
Was OS/Jupyter hosted on AWS?
I was using the Safari browser on my Mac. to connect to Jupyter.
On May 29, 2017, at 6:42 AM, Abhinav Gupta notifications@github.com wrote:
I have faced similar issue couple of times in the past. In one case, it was happening since I was behind a corporate firewall. In another case, it got resolved by switching to another browser (A weird hack but it worked!)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jupyter/notebook/issues/2386#issuecomment-304664103, or mute the thread https://github.com/notifications/unsubscribe-auth/AC9i2_05d2Ys9QZ9WavQzfYUh76hddS6ks5r-stSgaJpZM4M3Nqt.
abhinavkgp
commented
7 years ago I was using Windows 8.1 OS and it was hosted on AWS Server. For me, Chrome solved the problem.
dbl001
commented
7 years ago Chrome couldn’t connect either.
On May 30, 2017, at 1:36 AM, Abhinav Gupta notifications@github.com wrote:
I was using Windows 8.1 OS and it was hosted on AWS Server. For me, Chrome solved the problem.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jupyter/notebook/issues/2386#issuecomment-304811696, or mute the thread https://github.com/notifications/unsubscribe-auth/AC9i26-VJjPM-Qop0KOXeKB6CUKoV4E6ks5r-9UHgaJpZM4M3Nqt.
dbl001
commented
7 years ago I finally got it to work with Safari. :-)
On May 30, 2017, at 1:36 AM, Abhinav Gupta notifications@github.com wrote:
I was using Windows 8.1 OS and it was hosted on AWS Server. For me, Chrome solved the problem.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jupyter/notebook/issues/2386#issuecomment-304811696, or mute the thread https://github.com/notifications/unsubscribe-auth/AC9i26-VJjPM-Qop0KOXeKB6CUKoV4E6ks5r-9UHgaJpZM4M3Nqt.
I configured Jupyter to run from my AWS Unbuntu instance. I am able to connect to Jupyter from Safari on my Mac, however, my Python 2.7 instance are dying (even after restarting the kernel).
Start Jupyter notebook:
Processes running: