Jupyter Server Not Found (executable not in PATH)
See original GitHub issueDescription
When starting jupyterlab_app, I get the message:
Jupyter Server Not Found We were unable to launch a Jupyter server, which is a prerequisite for JupyterLab Native. If Jupyter is installed as a python module, but the python executable is not in your PATH, specify the executable location below. Otherwise, try installing or updating Jupyter. The Jupyter notebook version must be 4.3.0 or greater.
Despite a) having a working jupyter-lab installation that I can spin up from the terminal and which appears in the browser, b) having the python executable in my path, and c) having the requisite version of jupyter.
When I manually point jupyterlab_app to the python executable (/Users/aschuler/.pyenv/shims/python
) via the CHOOSE PATH
it spins the icon again for a moment and then returns the same “Server Not Found” message.
Context
I am running python through pyenv, which may be the issue here. Relevant information:
aschuler@Alejandros-MacBook-Air ~ % pyenv versions
system
* 3.9.6 (set by /Users/aschuler/.pyenv/version)
aschuler@Alejandros-MacBook-Air ~ % echo $PATH
/Users/aschuler/.pyenv/shims:/Applications/Sublime Text.app/Contents/SharedSupport/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin
aschuler@Alejandros-MacBook-Air ~ % jupyter --version
jupyter core : 4.7.1
jupyter-notebook : 6.4.0
qtconsole : 5.1.1
ipython : 7.26.0
ipykernel : 6.0.3
jupyter client : 6.1.12
jupyter lab : 3.1.13
nbconvert : 6.1.0
ipywidgets : 7.6.3
nbformat : 5.1.3
traitlets : 5.0.5
aschuler@Alejandros-MacBook-Air ~ % which python
/Users/aschuler/.pyenv/shims/python
aschuler@Alejandros-MacBook-Air ~ % which jupyter-lab
/Users/aschuler/.pyenv/shims/jupyter-lab
(MK): Extra details from title: jupyterlab_app fails to start on MacOS 11.5.2 with (pyenv issue?)
Issue Analytics
- State:
- Created 2 years ago
- Comments:50 (19 by maintainers)
Top GitHub Comments
@krassowski I’d love to try that, but, as I said, I can’t get the app to even start the server. Based on my understanding, I can’t really do anything about the kernel without a running server in the first place, right?
Hi @Kaisershmarren, @flashypepo, @alejandroschuler, @pybokeh the newly released v3.2.4-2 contains two fixes for this problem - would you mind testing it and letting us know if it works for you well now?
If it does not could you please provide the logs from:
~/.config/jupyterlab-desktop/logs/main.log
~/Library/Logs/jupyterlab-desktop/main.log
%USERPROFILE%\AppData\Roaming\jupyterlab-desktop\logs\main.log