search

dask / dask-ec2

Start a cluster in EC2 for dask.distributed
106 stars 37 forks source link

Could not connect to salt server #100

Open mccarthyryanc opened 7 years ago

mccarthyryanc commented 7 years ago

Originally posted to issue #32, but on closer inspection it looks like the errors are slightly different:

Error with request: <urlopen error [Errno -2] Name or service not known>
ERROR: Could not connect to salt server. Try `dask-ec2 provision` and try again

Also noticed this in /var/log/syslog:

Sep 14 22:54:30 hostname salt-minion[16091]: [ERROR   ] DNS lookup or connection check of 'None' failed.
Sep 14 22:54:30 hostname salt-minion[16091]: [ERROR   ] Master hostname: 'None' not found or not responsive. Retrying in 30 seconds

Command I am running:

dask-ec2 up --ami ami-XXXXXXXX \
            --keyname keyname \
            --keypair keypair.pem \
            --name dasknode \
            --tags Name:dasknode \
            --count 2 \
            --region-name us-west-2 \
            --security-group-id sg-XXXXXXXX \
            --iaminstance-name profile_name \
            --subnet-id subnet-XXXXXXXX

Continue to get the same error after running: dask-ec2 provision.

dask-ec2, version 0.5.0+5.g1849efc Python 3.5.4

DanCardin commented 7 years ago

I'm currently also hitting this. I feel like it has something to do with how the subnet you're using is configured.

The subnet I'm creating them in is not set to assign public ips to instances, which meant I was getting None values in the cluster.yml file. After manually switching them over to the private ips of the corresponding machines in the subnet, I started hitting this problem; but im not sure where to go from there