Hey Justin,
Thanks for the reply. if there's a problem with the AMI it's my fault -- i
built it :). This was my first AMI so it's entirely possible -- and quite
likely -- I did not build it correctly.
Below is the debug output:
2012-09-13 13:06:47,604 PID: 30819 cluster.py:1502 - INFO - Running plugin
ipcluster
2012-09-13 13:06:47,797 PID: 30819 __init__.py:539 - DEBUG -
/opt/anaconda/bin/ipython
2012-09-13 13:06:48,096 PID: 30819 __init__.py:539 - DEBUG -
/opt/anaconda/bin/ipcluster
2012-09-13 13:06:50,385 PID: 30819 __init__.py:539 - DEBUG - 0.13
2012-09-13 13:06:50,672 PID: 30819 __init__.py:539 - DEBUG - 1
2012-09-13 13:06:50,895 PID: 30819 __init__.py:539 - DEBUG - 1
2012-09-13 13:06:51,247 PID: 30819 __init__.py:97 - DEBUG - connecting to
host ec2-23-22-249-3.compute-1.amazonaws.com on port 22 as user disco
2012-09-13 13:06:52,088 PID: 30819 __init__.py:186 - DEBUG - creating sftp
connection
2012-09-13 13:06:52,274 PID: 30819 ipcluster.py:92 - INFO - Writing IPython
cluster config files
2012-09-13 13:06:55,542 PID: 30819 __init__.py:539 - DEBUG -
[ProfileCreate] Generating default config file:
u'/opt/anaconda/var/disco/.ipython/profile_default/ipython_config.py'
2012-09-13 13:06:55,542 PID: 30819 __init__.py:539 - DEBUG -
[ProfileCreate] Generating default config file:
u'/opt/anaconda/var/disco/.ipython/profile_default/ipython_notebook_con
fig.py'
2012-09-13 13:06:56,371 PID: 30819 ipcluster.py:172 - INFO - Starting
IPython cluster with 1 engines
2012-09-13 13:06:57,705 PID: 30819 __init__.py:539 - DEBUG - 2012-09-13
18:07:50,902.902 [IPClusterStart] Using existing profile dir:
u'/opt/anaconda/var/disco/.ipython/profile_def
ault'
2012-09-13 13:06:57,705 PID: 30819 ipcluster.py:180 - INFO - Waiting for
JSON connector file...
2012-09-13 13:07:29,305 PID: 30939 config.py:551 - DEBUG - Loading config
2012-09-13 13:07:29,305 PID: 30939 config.py:118 - DEBUG - Loading file:
/home/quasiben/.starcluster/config
On Thu, Sep 13, 2012 at 1:13 PM, Justin Riley <justin.t.riley_at_gmail.com>wrote:
> Hi Ben,
>
> Looks like you're using the Anaconda AMI from Continuum IO which in
> theory should work with StarCluster. I'm not sure if they've prepared
> it to work properly with the IPython plugin or not. I'll try to launch
> an IPython cluster with their AMI and see what's going on but for now
> you can get some good hints as to what the issue is looking in
> $HOME/.starcluster/logs/debug.log. If you could post the lines
> surrounding "Waiting for JSON connector file..." that would be useful
> in figuring out what the issue is.
>
> ~Justin
>
> On Thu, Sep 13, 2012 at 12:26 PM, Ben Zaitlen <ben.zaitlen_at_continuum.io>
> wrote:
> > Hi All,
> >
> > I seem to be having a similar problem as described in a closed github
> issue:
> > https://github.com/ipython/ipython/issues/2171
> >
> > the plugin hangs on the following line:
> >>>> Waiting for JSON connector file.../
> >
> > According to the issue tracker the it's been resolved. However, I just
> > cloned the latest git repo and the plugin never makes it past the "JSON
> > connector file" line
> >
> > Notes:
> >
> > AMI: ami-15893d7c
> > Linux 3.2.20-1.29.6 x86_64
> > Amazon Linux AMI release 2012.03 (CentOS)
> > IPython 0.13
> > StarCluster 0.93.3
> >
> > Any ideas on how to proceed?
> >
> > --Ben
> >
> > _______________________________________________
> > StarCluster mailing list
> > StarCluster_at_mit.edu
> > http://mailman.mit.edu/mailman/listinfo/starcluster
> >
>
Received on Thu Sep 13 2012 - 14:18:35 EDT