-
-
Notifications
You must be signed in to change notification settings - Fork 415
Jupyter Server Not Found (executable not in PATH) #238
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
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
The problem occurs even if I point jupyterlab_app to the "true" python executable (not the pyenv shim), i.e. |
Same thing happens with me, except I'm on Windows 10 OS. For some reason, it keeps thinking it should search for the python.exe located in the C:\JupyterLab folder despite me manually pointing it to the python.exe of the Python virtual env that has jupyterlab and server installed. EDIT: I am using just venv module for my virtual environments, not pyenv. |
I think that jupyter_app was designed to be started from the icon file provided which takes care of selecting appropriate environment. For example on Ubuntu/GNOME this is an icon showing up in the application grid: I expect that on Windows there is an icon in the start menu, and something similar on Mac. When you start jupyterlab-app from the menu entry/desktop icon does this error show up too? |
@krassowski I was starting jupyter from the mac spotlight search (cmd-space -> "jupyter..." -> enter). I think this is the same as using the icon but I also just tried finding the icon in the application folder manually and double clicking and the result is the same. |
@alejandroschuler @pybokeh JupyterLab App bundles a Python environment and uses that environment explicitly. Clicking launcher icons are the right way to launch as @krassowski noted.
|
@mbektas yes I can see |
Is your goal to run a kernel from your installation, or to run a server from your installation? While I see a case for the former, I don't see when the latter would be required. |
Ah, I see what you mean @krassowski. I would be more than content to run a kernel for my installation. That would suffice for packages installed via terminal pip to be accessible from jupyter, right? Either way, it seems I can't even do that at the moment (i.e. the app fails to start even its own bundled server!) |
Moreover, if the app is using its own installation of jupyter, why does the error message inform me that I should try to install or update jupyter?? That seems needlessly confusing. |
The error message was added a long time ago when the things worked differently and is probably worth replacing with something better (please feel welcome to contribute!). This app was just revived, please bear with us 🐻 while it is going through its infancy issues. As for re-using kernels from other virtual environments/installations, it depends on the kernel, but when using IPython (ipykernel) you can:
Now, it works for me on Ubuntu but I don't have Windows/Mac to test it. It would be great if you could follow these steps and let us know how it goes. |
There is also nb_conda_kernels and jupyter_environment_kernels which allow for auto-discovery of kernels and maybe we should consider including those by default. This discussion is in #169 (comment). |
@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? |
I also can't do anything, because starting JupyterLab-Desktop stops at "Jupyter Server not found". I've tried to select the installed Anaconda's python executabele, I'll see the "jlab_server" but cannot select it after "choose path". I've also checked MacOS (dammed)Privacy rules, no success. I'll wait until later. Sorry, JupyterLab Desktop looks promising but does not work for me yet. |
Coming from #321:
1.: Yes, I tried "install for all users" with the same result. I have installed several python versions via pyenv on this machine, maybe this has a side effect. I had hoped for a nice sandboxed environment that doesn't interact with existing Python installations (and doesn't require a previous python installation).
|
One more comment: Last week, about 15 students in my DSP course had installed Jupyterlab Desktop without a problem, making me feel a little stupid. One major difference could be that they didn't have previous installations of Python and / or JupyterLab while my path contains:
Are there known issues with parallel Python / JupyterLab installations? |
Dear all, My environment is: MacOSX 12.0.1 For the creation of virtual environment I followed the instruction on: |
@Kaisershmarren what is the version of JupyterLab installed in your |
Dear @krassowski, Name: jupyterlab When you're saying to start JupiterLab are you meaning to start jupyter-server ? [I 2021-11-18 19:15:04.997 ServerApp] jupyterlab | extension was successfully linked.
I don't know if it could be useful, but I also managed to start JupiterNotebook (of course it's not nice to use as the desktop version... but it's working...) from Anaconda Navigator (in the section of environments): |
That's very useful, thank you. Could you do this once more for me but execute the following command:
please? |
I've launched the command... and this is the output... there is an error at the end... The Jupyter Server. This launches a Tornado-based Jupyter Server. SubcommandsSubcommands are launched as list OptionsArguments that take values are actually convenience aliases to full --debug To see all available configurables, use Examples
[C 2021-11-18 19:42:00.080 ServerApp] Bad config encountered during initialization: |
Sorry, that's my mistake, there should be an equal sign between
|
Ok. Perfect. Here's the output. (mobile_net_ssd2) max@MacBook-Pro-di-Massimiliano jupyterlab-desktop % /Users/max/opt/anaconda3/envs/mobile_net_ssd2/bin/python -m jupyterlab --no-browser --JupyterApp.config_file_name='' [I 2021-11-18 20:18:27.422 ServerApp] jupyterlab | extension was successfully linked.
|
You're right. The version of traitlets is 4.3.3 (mobile_net_ssd2) max@MacBook-Pro-di-Massimiliano ~ % pip show traitlets But... (mobile_net_ssd2) max@MacBook-Pro-di-Massimiliano ~ % pip install --upgrade traitlets==5.0.0 |
This is interesting. Newer versions are certainly available on PyPI: https://pypi.org/project/traitlets/ Maybe you have a version of Python which is no longer supported by trailers in 5.x? Or, less likely maybe you use a PyPI mirror which was not updated? |
In mobile_net_ssd2 I've python version 3.6.13. and it seems that traitlets 5.0.0 support only python >= 3.7 |
I tried to install the app just for me under Win 10 64b (still I have to elevate the access rights). Then I run into the problem of a greyed out "install" button during selection of the install location: I cancelled installation at that point and restarted which skipped the first part of installation and gave me the message: I tried to select the bundled Python environment and got the same pop-up window once more. On my system I have c:\Users\Chris.pyenv\pyenv-win\shims\python For some reason, I cannot select the Windows Python.exe, when selecting the first entry I get the following error: And here is the log file: |
@chipmuenk You need to install jupyterlab in the selected environment ( pyenv activate pyenv-win
pip install -U "jupyterlab>=3.1" The issue with greyed out "Next" button is interesting. Could it be that you have less space available than required by installer? |
I'm sorry but then I don't see the point of the Jupyterlab Desktop App. I thought it was targeted at newbies as a simple one-file-click-to-install solution? I have always done a simple On my c:\ drive I have 72 GB free space which should be enough. |
Yes, the idea is to work like that. For some reason your installation failed. When you attempted to recover the installation by running the installer once again, it must have skipped the installation of the ready-to-go virtual environment targeted at newbies. Knowing that you are an advanced user (based on your previous comments) and seeing that you are able to recover by selecting a different virtual environment I suggested to run pip install in a way which should ensure that the required version is installed. It is not a prerequisite of using JupyterLab Desktop when the installation process works as it should. If you believe that you already have correct version of jupyterlab installed in that environment please provide PS. I would appreciate more understanding tone. There is no need for rhetorical questions. |
I'm sorry if I came across unfriendly but my question was meant seriously. For me, the installation experience has been quite confusing so far and it sounded to me as if previous installation of the jupyterlab package was a requirement, especially as I had problems with the jupyter server every time. I'm afraid I can't give you a |
Sorry, I do not follow. Do you mean that you pointed the first of the two Windows installers to use Or, do you mean that after starting the application which showed you the "Set Python Environment" window you pointed it to |
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:
|
Great work, @krassowski!!! Thank you so much. |
This is still broken for me on macOS 11.6.1 (Big Sur), even with the latest version main.log output
|
@flavio87 could you please provide earlier logs from |
ah yes, here is the previous message. I don't know why it is already executing some code (and then failing at loading a particular file) when I am just opening the app?
|
@flavio87 thank you. It looks like you have a file which shadows the Python built-in Do you happen to have Maybe we should start Python in |
omg, I had created a file called random.py to play around with some code, and that is what it was importing. I just had to rename this file to random2.py and now it works again... I don't think any of the |
Hello. I have a related problem to this one (I think?) I am on the MacOS, and I would like to access the jlab executable like this webpage describes:
But when I try to run it, it's not there:
But there is no app subfolder, there's onlyt his app.asar file:
Any ideas? Thanks!
macos: 10.14.6 |
@doctor-duus I believe this is unrelated. We would need more information. Could you please open a new bug report providing all the details requested in the template? |
Hello. It turns out I apparently did not fully follow the uninstall instructions. When I redid (or correctly did?) the uninstall instructions and reinstalled, it worked fine. |
Hi @krassowski could you kindly guide me on how to resolve this issue, I still get the error message below. I also attached my windows log below for your support. |
@Okaforemeka it looks like you are experiencing the |
@krassowski Many thanks for your specific guidance, it resolves my issue and i'm now able to reuse Jupyter lab. This was very helpful. Thanks. Wish you a great year. |
This issue has been mentioned on Jupyter Community Forum. There might be relevant details there: https://discourse.jupyter.org/t/how-to-solve-jupyter-server-initialization-failed/12469/2 |
Just checked and everything works for me with the latest version (with my own environment, following the instructions on the user guide). Not sure what the problem was but it's all good now. I'm going to close the issue since there are other more specific issues that seem to apply for other problems but feel free to reopen if this is a good general-purpose forum. |
Description
When starting jupyterlab_app, I get the message:
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 theCHOOSE 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:
(MK): Extra details from title: jupyterlab_app fails to start on MacOS 11.5.2 with (pyenv issue?)
The text was updated successfully, but these errors were encountered: