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
Ipcluster plugin is not working with Ipython 1.0dev #3936
Comments
Running current starcluster (develop branch) and IPython (master), the ipcluster plugin seems to work just fine. |
How are you trying to use IPython 1.0-dev? |
I have pip installed Ipython 1.0-dev in an AMI using the following template:
(I omitted aws info and global settings) And finally run:
|
can you ssh to the cluster and try to see what's going on? |
I can ssh via |
see if the notebook is running, maybe try to start another notebook instance and connect to that. |
Now it's working. When I started another notebook I got an error related to Jinja. The notebook did run but with a text-based interface. Maybe Jinja wasn't a dependency before. It would be nice to output those errors when an instance is created. Thank you for your help. |
This would be w3m. To prevent it from opening, start the notebook with
Jinja was not a dependency before. |
I have been running starcluster 0.94 with the ipcluster plugin without issues, however, when I try to use ipython 1.0 dev, I simply can't access the notebook. Starcluster provides the notebook url (https://ec2-xx-xx-xxx-xxx.compute-1.amazonaws.com:8888) but I get a 404.
Is this a known bug or do I need to configure something else to get it to work?
The text was updated successfully, but these errors were encountered: