amazon web services - i/o timeout error using progrium/docker-consul -


i'm attempting set production-ready cluster on aws uses jeff lindsay's progrium/docker-consul image install consul on each host can't secondary , tertiary servers -join initial server.

i've followed running real consul cluster in production instructions i'm getting i/o timeout error when consul2 , consul3 nodes attempt -join consul1 private ip.

the instances

i spun 3 t2.micros on aws , got following private ip's assigned in vpc:

172.31.4.194 (intended `consul1`, leader) 172.31.4.195 (intended `consul2`) 172.31.4.193 (intended `consul3`) 



starting initial consul server instance

my consul1 node gets , waiting other 2 fine:

sudo docker run -d -h consul1 --name consul1 -v /mnt:/data \     -p 172.31.4.194:8300:8300 \     -p 172.31.4.194:8301:8301 \     -p 172.31.4.194:8301:8301/udp \     -p 172.31.4.194:8302:8302 \     -p 172.31.4.194:8302:8302/udp \     -p 172.31.4.194:8400:8400 \     -p 172.31.4.194:8500:8500 \     -p 172.17.42.1:53:53/udp \     progrium/consul -server -advertise 172.31.4.194-bootstrap-expect 3 



attempting run second server instance

but when attempt start consul2 node, using following:

sudo docker run -d -h consul2 --name consul2 -v /mnt:/data \     -p 172.31.4.195:8300:8300 \     -p 172.31.4.195:8301:8301 \     -p 172.31.4.195:8301:8301/udp \     -p 172.31.4.195:8302:8302 \     -p 172.31.4.195:8302:8302/udp \     -p 172.31.4.195:8400:8400 \     -p 172.31.4.195:8500:8500 \     -p 172.17.42.1:53:53/udp \     progrium/consul -server -advertise 172.31.4.195 -join 172.31.4.194 



the error

here's error i'm getting:

==> warning: highly recommended set gomaxprocs higher 1 ==> starting raft data migration... ==> starting consul agent... ==> starting consul agent rpc... ==> joining cluster... ==> dial tcp 172.31.4.194:8301: i/o timeout 



any idea of causing this? i've re-attempted 9 times , still no luck. did spur me more learning networking (which broad, deep, fascinating subject) can't figure out if there's issue in config, or if actual bug.

thanks in advance help.

problem solved!

turns out had forgotten open ports consul needs use in security group governs access instances.

opened 8300,8301,8302,8400, , 8500 , installed fine.


Comments

Popular posts from this blog

powershell Start-Process exit code -1073741502 when used with Credential from a windows service environment -

twig - Using Twigbridge in a Laravel 5.1 Package -

c# - LINQ join Entities from HashSet's, Join vs Dictionary vs HashSet performance -