Failed to connect to the remote Jupyter Server running on Google dataproc

[TarjinderSingh]

I have been unsuccessfully trying to use the remote Jupyter Server function for a while, and finally thought I should ask for help!

I have a Jupyter Notebook running on port 8123 on Google Dataproc, and I can access the notebook fine (normally) after port forwarding at localhost:8123 in my browser. However, I keep failing to connect to the remote Jupyter Server using vscode, with the following error message that I don't quite understand, ending with SessionManager cannot enumerate kernelspecs. Returning default {}.

Am I missing something, and is there something fixable for me to access the Notebook?

Info 18:50:02: Notebook Closed vscode-interactive:Interactive-1.interactive
Info 18:50:02: Closing interactive window: vscode-interactive:Interactive-1.interactive
Info 18:50:02: Creating server with settings : {"baseUrl":"https://localhost:8123/","appUrl":"","wsUrl":"wss://localhost:8123/","token":"12345","appendToken":true,"init":{"cache":"no-store","credentials":"same-origin"}}
[I 18:50:02.330 NotebookApp] Kernel shutdown: a6901b75-a9e9-41d0-b793-870f3506eefb
Info 18:50:04: Starting interactive window with controller ID ms-toolsai.jupyter/.jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f./Users/tsingh/anaconda3/envs/schema2/python./Users/tsingh/anaconda3/envs/schema2/python.-m#ipykernel_launcher
Info 18:50:04: Setting setActiveController for vscode-interactive:Interactive-1.interactive
Info 18:50:04: TargetController found ID: .jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f./Users/tsingh/anaconda3/envs/schema2/python./Users/tsingh/anaconda3/envs/schema2/python.-m#ipykernel_launcher (Interactive) for document vscode-interactive:Interactive-1.interactive
Info 18:50:04: Setting controller affinity for vscode-interactive:Interactive-1.interactive .jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f./Users/tsingh/anaconda3/envs/schema2/python./Users/tsingh/anaconda3/envs/schema2/python.-m#ipykernel_launcher (Interactive)
Info 18:50:04: Process Execution: > ~/anaconda3/envs/schema2/bin/python -m pip list
> ~/anaconda3/envs/schema2/bin/python -m pip list
Info 18:50:04: Starting Notebook in kernel.ts id = .jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f./Users/tsingh/anaconda3/envs/schema2/python./Users/tsingh/anaconda3/envs/schema2/python.-m#ipykernel_launcher
[I 18:50:04.725 NotebookApp] Creating new notebook in 
Info 18:50:04: installMissingDependencies ~/anaconda3/envs/schema2/bin/python
Info 18:50:04: IPykernel found previously in this environment ~/anaconda3/envs/schema2/bin/python
Info 18:50:04: Spec argv[0] updated from '/Users/tsingh/anaconda3/envs/schema2/bin/python' to '~/anaconda3/envs/schema2/bin/python'
Info 18:50:04: Starting a new session for kernel id = .jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f./Users/tsingh/anaconda3/envs/schema2/python./Users/tsingh/anaconda3/envs/schema2/python.-m#ipykernel_launcher, name = python374jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f
[I 18:50:04.979 NotebookApp] Kernel started: b1f6326c-637f-4fb6-82fb-279a63f7bc47, name: python374jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f
Info 18:50:05: Waiting for idle on (kernel): b1f6326c-637f-4fb6-82fb-279a63f7bc47 -> unknown
[W 18:50:05.034 NotebookApp] delete /Untitled-2-jvsc-272d630a-d76f-4344-acac-81534fecab10.ipynb
Info 18:50:06: Finished waiting for idle on (kernel): b1f6326c-637f-4fb6-82fb-279a63f7bc47 -> idle
Info 18:50:06: Started session for kernel .jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f./Users/tsingh/anaconda3/envs/schema2/python./Users/tsingh/anaconda3/envs/schema2/python.-m#ipykernel_launcher
Info 18:50:06: Waiting for idle (session) kernel .jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f./Users/tsingh/anaconda3/envs/schema2/python./Users/tsingh/anaconda3/envs/schema2/python.-m#ipykernel_launcher
Info 18:50:06: Waiting for idle on (kernel): b1f6326c-637f-4fb6-82fb-279a63f7bc47 -> idle
Info 18:50:06: Finished waiting for idle on (kernel): b1f6326c-637f-4fb6-82fb-279a63f7bc47 -> idle
Info 18:50:06: Finished connecting kernel .jvsc74a57bd0f8e3ce338964ead362a45c6e0e786e8b405b1b1657107be6f98479240d02113f./Users/tsingh/anaconda3/envs/schema2/python./Users/tsingh/anaconda3/envs/schema2/python.-m#ipykernel_launcher
Info 18:50:06: Executing silently Code (idle) = import sys\nprint(sys.executable)
Info 18:50:07: Executing silently Code (completed) = import sys\nprint(sys.executable)
Info 18:50:07: Executing silently Code (idle) = import site\nsite.addsitedir(site.getusersitepackages())\n__vsc_ipynb_file__ = 'Untitled-2'\n%config Co
Info 18:50:07: Executing silently Code (completed) = import site\nsite.addsitedir(site.getusersitepackages())\n__vsc_ipynb_file__ = 'Untitled-2'\n%config Co
Info 18:50:07: Waiting for idle on (kernel): b1f6326c-637f-4fb6-82fb-279a63f7bc47 -> idle
Info 18:50:07: Finished waiting for idle on (kernel): b1f6326c-637f-4fb6-82fb-279a63f7bc47 -> idle
Info 18:50:07: Executing silently Code (idle) = __file__ = 'Untitled-2'
Info 18:50:07: Creating server with settings : {"baseUrl":"https://localhost:8123/","appUrl":"","wsUrl":"wss://localhost:8123/","token":"12345","appendToken":true,"init":{"cache":"no-store","credentials":"same-origin"}}
Info 18:50:07: Executing silently Code (completed) = __file__ = 'Untitled-2'
Error 18:50:22: SessionManager cannot enumerate kernelspecs. Returning default {}.
Error 18:50:27: SessionManager cannot enumerate kernelspecs. Returning default {}.

[DonJayamanne]

thanks for posting this message, this looks like a bug in the extension,
I'll transfer this to the issues so we can address this there.
I'll try to create an extension with additional logging, will also try this myself.

[TarjinderSingh]

Great - let me know if there is anything I can do to help!

[DonJayamanne]

I have transferred the issue here #9099, lets continue this discussion there for now. Thanks

[DonJayamanne]

This issue is being tracked here #9099