conda tab doesn't work #23
Comments
|
That's weird... from the log, it looks like the front end JS extensions are loading but the back end (python nbserver extensions) aren't. |
|
Seems to be linked to nb_delta. After removing nb_delta conda tab works again. @bollwyvl maybe you can suggest what is going on here? |
|
Ah, but my command above didn't have nb_delta in it... |
|
Nonetheless, I had this exact problem with the Trial VM after installing all the latest notebook extension packages. Weird stuff ensued so I uninstalled |
|
Good find! We have talked about setting up a way to re-run the tests for all the extensions with them all installed... Perhaps in the meta package. These are really hard to catch without a browser and the rest of the app running. |
|
Just confirmed that I'm still seeing this in the Trial VM:
But in that case I notice another oddity: only the root environment is listed, even though this is inside AEN where the project environment should (I would have thought!) appear, and furthermore be selected as the "default". Importantly, notice in the screen shot that the URL bar shows
And so that is what I am actually (eventually, after ssh port forwarding) connecting to. |
|
The issue I reported immediately above with the error screenshot saying "Could not find URL: http://localhost:8080/..." is due to some combination of conda/conda#2457 and conda/conda#2458. However that is, I believe, different from the issue I originally reported (in the screen cast). So the problem remains. |
|
Still haven't been able to reproduce this locally. Currently reprovisioning my trial box to give it a whack there. In the meantime, I'll work on expanding the test coverage... in |
|
Can you run these two commands in an offending environment? Here's what I get... if we're seeing something different, that could help a lot in tracking this down! |
|
No 🎲 reproducing the error on the trial box: |
|
However, creating a new environment hangs the notebook server Also, it is not finding the r kernel (i assume these are installed?) Here's the bad news from the log: |
|
The above is with nb_conda 0.1.4 and notebook 4.1... trying to update... |
|
@bollwyvl did you have a chance to try the Phase 2 Trial VM? There is a FD thread in the *ae-trial` flow from ~Wednesday describing the steps to fetch it. 10 GB still... |
|
@bollwyvl I am definitely still getting this behavior with a "fresh" setup following exactly this procedure: This results in this output in the terminal (up to the point where I click on the "Conda" tab): And here is a screenshot of what I see (same as before):
In case it is germaine: |
|
What is the output of:
and
I am suspecting in some conflict because of config files in different places... |
|
@damianavila here you go: and also: |
|
Nice. Yeah, try backing up |
|
I ran into this issue myself (404s on /environments and /packages) on a fresh install. Here's the output of I then ran the following commands: Before running these commands, This caused nb_conda to start working properly. When I move that file out of the way by renaming it, nb_conda starts failing again, even though the output of jupyter serverextension list is unchanged. |
|
@dankrause thanks for the report, I am wondering why the list command is not telling you the right thing... |
|
@dankrause what is the content of you ~./jupyter folder? Can you try backing up that folder, delete it and make a fresh install? I am thinking about some issue with already present conf files at |
|
I have the same issue with the 400 errors and the conda tab. It seems there is some incompability with nbextensions-configurator. I can't get anaconda to work in combination with it at least. I'm using jupyterhub with a custom notebook container. Dockerfile
|
|
Same issue here. I removed /usr/local/etc/jupyter, restarted Jupiter notebook and the 'conda' tab works now. |
|
Same issue. Had to rm jupyter_notebook_config.json from ~/.jupyter |
|
Hi I have similar issue, but the source of error is different. I have conda installed in /opt/conda I am running jupyterhub through Supervisor I can use the [root] conda env, but when I access the conda tab I get following entry in stderr log The issue is obvious. To find out if conda directory is in $PATH I logged the sys.path b4 executing the errorneous command and it is there. Now I am lost, not sure what to do. Any ideas? |
|
On 02/19/2017 10:34 AM, Robin Nemeth wrote:
Hi I have similar issue, but the source of error is different.
I have conda installed in /opt/conda
I am running jupyterhub through Supervisor I can use the [root] conda
env, but when I access the conda tab I get following entry in stderr log
|[E 2017-02-19 18:20:16.788 nemeth handlers:514] Unhandled error in API
request Traceback (most recent call last): File
"/opt/conda/lib/python3.5/site-packages/notebook/base/handlers.py", line
503, in wrapper result = yield gen.maybe_future(method(self, *args,
**kwargs)) File
"/opt/conda/lib/python3.5/site-packages/nb_conda/handlers.py", line 51,
in get self.finish(json.dumps(self.env_manager.list_envs())) File
"/opt/conda/lib/python3.5/site-packages/nb_conda/envmanager.py", line
60, in list_envs info = self.clean_conda_json(self._execute('conda info
--json')) File
"/opt/conda/lib/python3.5/site-packages/nb_conda/envmanager.py", line
46, in _execute output = check_output(cmdline) File
"/opt/conda/lib/python3.5/subprocess.py", line 626, in check_output
**kwargs).stdout File "/opt/conda/lib/python3.5/subprocess.py", line
693, in run with Popen(*popenargs, **kwargs) as process: File
"/opt/conda/lib/python3.5/subprocess.py", line 947, in __init__
restore_signals, start_new_session) File
"/opt/conda/lib/python3.5/subprocess.py", line 1551, in _execute_child
raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno
2] No such file or directory: 'conda' |
The issue is obvious. To find out if conda directory is in $PATH I
logged the sys.path b4 executing the errorneous command and *it is there.*
But do you or the process trying to access it have the necessary
privileges to use the directory?
…
Now I am lost, not sure what to do. Any ideas?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAoLVCYYqviZdluuOIUFRhmmKyTwlj0Hks5reIsngaJpZM4IKLkr>.
--
Adrian Klaver
adrian.klaver@aklaver.com
|
|
Hi Robin,
A few comments:
On 2/19/17 1:34 PM, Robin Nemeth wrote:
Hi I have similar issue, but the source of error is different.
I have conda installed in /opt/conda
Anaconda is optimized to run on a single system and for a single user.
It definitely SHOULD run correctly when installed in a centralized
location such as /opt/conda (though perhaps /opt/anaconda would be a
better name). Anaconda and conda are two different things -- I admit
this is somewhat confusing -- with Anaconda a full data science
distribution, and conda the package manager that Anaconda relies upon.
But there are definitely scenarios where Anaconda isn't going to work
properly when deployed centrally for multi-user access. If this is
something that is important to you then I'd suggest you look at Anaconda
Enterprise which is designed specifically for this audience: compute
clusters, centralized deployment, multi-user access. Look it up at
continuum.io or contact our sales team sales@continuum.io
I am running jupyterhub through Supervisor I can use the [root] conda
env, but when I access the conda tab I get following entry in stderr log
Processes started by supervisor are unlikely to have the same PATH as
what you get from the command line. You could debug this by adding in
an "echo $PATH" statement (or if it is a Python script "import os;
print(os.environ['PATH'])").
nb_conda has never been tested with JupyterHub. Having this capability
(multi-user login to Jupyter Notebooks with in-Jupyter access to conda
package and environment management) is an integral part of Anaconda
Enterprise.
Regards,
Ian
|
|
The original issue seems related with some failures when you install There is second issue related with some configs in the user space conflicting with the config we use at the sys-prefix... that could be investigated later in the following issue: #49 Finally, there is some issue related with jupyterhub, that will follow up in the this issue: #50 Closing this one now. |
I just recorded a screencast of this problem: http://screencast.com/t/jnBVQlce4
In short:
I created a conda env with:
I entered that conda environment to run conda:
I started Jupyter and then tried to go to the Conda tab. I get the error shown in the 2 minute video above. The full log from the start of Jupyter is below:
The text was updated successfully, but these errors were encountered: