Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jupyter kernel not found after switching between two local machines connected to the same remote server #16065

Closed
1 of 2 tasks
TSBB2012nc opened this issue Sep 21, 2024 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@TSBB2012nc
Copy link

Applies To

  • Notebooks (.ipynb files)
  • Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

  • Initial connection: I connect to the remote server from Machine A using VS Code Server and successfully run Jupyter notebook code.
  • Disconnecting: I then disconnect from the remote server on Machine A.
  • Subsequent connection: I connect to the same remote server from Machine B using VS Code Server.
  • Kernel not found: When trying to run Jupyter notebooks on Machine B, the window keeps finding kernel

VS Code Version

Version: 1.92.0 (system setup) Commit: b1c0a14de1414fcdaa400695b4db1c0799bc3124 Date: 2024-07-31T23:26:45.634Z Electron: 30.1.2 ElectronBuildId: 9870757 Chromium: 124.0.6367.243 Node.js: 20.14.0 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0.22631

Jupyter Extension Version

v2024.7.0

Jupyter logs

No response

Coding Language and Runtime Version

No response

Language Extension Version (if applicable)

No response

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

Remote

@TSBB2012nc TSBB2012nc added the bug Issue identified by VS Code Team member as probable bug label Sep 21, 2024
@amunger
Copy link
Contributor

amunger commented Sep 25, 2024

Just to clarify, are you connecting to the remote machine with an ssh connection? (rather than just selecting a remote jupyter server kernel through the kernel picker)

Can you collect some logs for us:

  1. set "jupyter.logging.level": "trace"
  2. Repro the issue
  3. copy the logs from the output panel after running Jupyter: Show Output and paste them here

@amunger amunger added the info-needed Issue requires more information from poster label Sep 25, 2024
Copy link

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants