I'm trying to start a cluster using dask-ec2 up. Here's the command I'm using:
dask-ec2 up --keypair ~/.aws/dask_poc.pem \
--name dask_poc \
--region-name eu-west-1 \ # Note I'm using different region from the default
--ami ami-47a23a30 \ # I also change the image to match the region I use
--type t2.nano \ # Very small machine; just for testing
--security-group dask-ec2-default \
--volume-size 100 \
--keyname dask_poc \
--tags dummy:tag
The process finished without errors but seems not to provide a cluster.
From the cluster: dask-ec2 ssh works, but ipython for instance is not installed. Furthermore, in the python shell from dask.distributed import Client, progress suggests that dask is not installed on the node.
From local: In Ipython,
In [1]: from dask.distributed import Client, progress
In [2]: e = Client('34.252.95.207:8786')
Yields a timeout/connection refused error OSError: Timed out trying to connect to 'tcp://34.252.95.207:8786' after 5 s: in <distributed.comm.tcp.TCPConnector object at 0x10727e9b0>: ConnectionRefusedError: [Errno 61] Connection refused
In addition, I cannot access http://34.252.95.207:8888/ but I can ping the IP.
I'm trying to start a cluster using
dask-ec2 up
. Here's the command I'm using:The process finished without errors but seems not to provide a cluster.
From the cluster:
dask-ec2 ssh
works, butipython
for instance is not installed. Furthermore, in thepython
shellfrom dask.distributed import Client, progress
suggests thatdask
is not installed on the node.From local: In
Ipython
,Yields a timeout/connection refused error
OSError: Timed out trying to connect to 'tcp://34.252.95.207:8786' after 5 s: in <distributed.comm.tcp.TCPConnector object at 0x10727e9b0>: ConnectionRefusedError: [Errno 61] Connection refused
In addition, I cannot access
http://34.252.95.207:8888/
but I can ping the IP.While the script was running, I noticed:
Which might already suggest that there's a problem.