Cannot reopen Jupyter notebooks on Google Cloud Dataproc cluster after stopping cluster -

i using google cloud dataproc run jupyter notebook (following these instructions: https://cloud.google.com/dataproc/docs/tutorials/jupyter-notebook).

i ran notebook, saved it, , @ point later on, stopped cluster (using gui). later restarted cluster , tried run jupyter notebook again same instructions in last step, when try open jupyter in chrome get:

"this site can't reached. webpage @ http://<my-cluster-name>:8123/ might temporarily down or may have moved permanently new web address. err_socks_connection_failed."  

also (i don't know if helps) in terminal window configured browser, have message:

error:child_thread_impl.cc(762)] request unknown channel-associated interface: ui::mojom::gpumain   google chrome[695:8548] nswindow warning: adding unknown subview: <fullsizecontentview: 0x7fdfd3e291e0>. break on nslog debug.   google chrome[695:8548] call stack: ( "+callstacksymbols disabled performance reasons" ) 

in terminal window ssh-ed cluster have these messages:

channel 3: open failed: connect failed: connection refused   channel 4: open failed: connect failed: connection refused   channel 5: open failed: connect failed: connection refused     channel 6: open failed: connect failed: connection refused    channel 12: open failed: connect failed: connection refused    channel 12: open failed: administratively prohibited: open failed   channel 13: open failed: administratively prohibited: open failed   channel 14: open failed: administratively prohibited: open failed   channel 14: open failed: connect failed: connection refused   channel 8: open failed: connect failed: connection refused   

also, earlier before had stopped cluster close jupyter notebooks, disconnect cluster, , reopen jupyter notebook. ran problem after had stopped cluster. ideas might going on?

this because current initialization action explicitly launches jupyter notebook service calling launch-jupyter-kernel.sh. initialization actions aren't same gce startup-scripts in don't re-run on startup; intent initialization actions need not idempotent, instead if want restart on startup need add init.d/systemd configs explicitly.

for one-off case, can ssh master, do:

sudo su source /etc/profile.d/conda.sh nohup jupyter notebook --allow-root --no-browser >> /var/log/jupyter_notebook.log 2>&1 & 

if want happen automatically on startup, can try put in startup script via gce metadata, though if you're doing @ cluster creation time you'll need make sure doesn't collide dataproc initialization action (also, startup scripts might run before dataproc init action, first attempt might want allow fail silently).

longer term, should update initialization action add entry init.d/systemd init action configures auto restart on reboot. there's no 1 dedicated @ moment, if or know task, contributions appreciated; filed https://github.com/googlecloudplatform/dataproc-initialization-actions/issues/108 track feature.