Content list call http://127.0.0.1:8888/api/contents/ failed with status error.

[deadlytackler5]

while starting ein with M-x ein:notebooklist-open

its throwing error

ein: [error] Kernelspc query call failed with status error.
ein: [error] Content list call http://127.0.0.1:8888/api/contents/ failed with status error.

what am I doing wrong ?

emacs - 24.5.1 (i686-pc-mingw32)
ein - 20160310.1319 thru melpa

[millejoh]

Not sure, but it will help if you can answer the following best you are able: What version of ipython are you running and how are you starting it? Is there any output in the console running ipython/jupyter from when you try to execute ein:notebooklist-open?

[deadlytackler5]

Jupyter notebook version: 4.1.0

There is no output in the console . It’s blank

ein:log-all has following entries

[error] Kernelspc query call failed with status error. @#<buffer *GNU Emacs*>

[verbose] Error thrown: (error . "exited abnormally with code 7") @#<buffer *GNU Emacs*>

[error] Content list call http://127.0.0.1:8888/api/contents/ failed with status error. @#<buffer *GNU Emacs*>

Regards

From: John Miller [mailto:[email protected]]
Sent: Saturday, March 12, 2016 11:36 PM
To: tkf/emacs-ipython-notebook [email protected]
Cc: deadlytackler [email protected]
Subject: Re: [emacs-ipython-notebook] Content list call http://127.0.0.1:8888/api/contents/ failed with status error. (#176)

Not sure, but it will help if you can answer the following best you are able: What version of ipython are you running and how are you starting it? Is there any output in the console running ipython/jupyter from when you try to execute ein:notebooklist-open?

—
Reply to this email directly or view it on GitHub #176 (comment) . https://github.com/notifications/beacon/AGqi7VriwWt6ltFtNUtHQb6RBe0fsh5Yks5pswB_gaJpZM4HvQKN.gif

[shelper]

i had the similar problem

windows 7
python 3.5, ipython 4.1.2 (jupyter)
emacs 24.5

turn on debug does not help in emacs, just an error msg:

ein: [error] Content list call http://127.0.0.1:8888/api/notebooks/ failed with status error.

and in the ipython console, it says:

[W 17:09:43.884 NotebookApp] 404 GET /api/kernels/8a300bcc-f24f-4e5d-8b79-dce9e57e258a/channels?session_id=E15E4BB2DE8445DA9D61CA862A9C9BD7 (::1) 13.00ms referer=None

[millejoh]

404 is URL not found. It looks like you are at least getting a list of notebooks when you call ein:notebooklist-open? I have very nearly the same setup (Win 7, python 3.5 as installed by anaconda, jupyter 4.1.0). When I launch jupyter notebook and open a notebook I get the following:

If your console is blank then my first thought is that something is wrong with jupyter. Is the web interface working okay?

[shelper]

i worked out by using url-retrieve instead of curl,
i dont know why, i actually do have the curl.exe in the path on my windows

the web interface worked

[millejoh]

Good to know. I've noticed a number of odd, hard to reproduce problems that seem to be solved by using url-retrieve instead of curl. In particular ein authentication on password-enabled jupyter notebook seems only to work when using url-retrieve as the requests backend.

I think in future releases of ein I may try to force the use of url-retrieve.

[shwangdev]

Would you please share me how to use url-retrieve instead of curl?

[apteas]

I had a similar problem but the problem was authentication. I had to 'ein:notebooklist-login' first in order to enter the token/password and then 'ein:notebooklist-open' to open the list.

[slackline]

I had a similar problem but the problem was authentication. I had to 'ein:notebooklist-login' first in order to enter the token/password and then 'ein:notebooklist-open' to open the list.

This was very helpful as I was struggling to connect. I found however that I had to first manually set my jupyter notebook password using....

jupyter notebook password
jupyter notebook

I could ein:notebooklist-login and explicitly providing the URL:port and after entering the password I then could connect via ein:notebooklist-open (again explicitly providing the URL:port).