Dynamodb, Failed to establish a new connection.

[R4m4n]

While running, deploy/docker-ephemeral/init.sh , in the wire-server root, I'm getting

HTTPConnectionPool(host='dynamodb', port=8000): Max retries exceeded with url: / (Caused by NewConnectionError('<botocore.awsrequest.AWSHTTPConnection object at 0x7ff6d71bcb70>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

If I run deploy/docker-ephemeral/run.sh, I'm getting:

aws_cli_1 | HTTPConnectionPool(host='dynamodb', port=8000): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<botocore.awsrequest.AWSHTTPConnection object at 0x7f26b8e9ce50>, 'Connection to dynamodb timed out. (connect timeout=1)'))

I've checked using:

docker-compose ps

and I got this as output:

demo_wire_dynamodb                            /docker-entrypoint.sh --sh ...   Up      127.0.0.1:4567->8000/tcp

This error is occurring for all the services i.e.: host name: Just "elasticsearch", service name: Just "9200"): does not exist (Try again)) host name: Just "cassandra", service name: Just "9042"): does not exist (Try again)

[R4m4n]

@jschaul Continuously getting this error even when I set up on a different server, after stopping the services. Any idea what could be causing this.

[R4m4n]

@tiago-loureiro, This error has been a blocker for me to continue to the next process.

[tiago-loureiro]

@R4m4n Running deploy/docker-ephemeral/run.sh is the correct thing to do.

You can try to docker-compose stop from the deploy/docker-ephemeral folder, and then re-run deploy/docker-ephemeral/run.sh.

[R4m4n]

Thanks @tiago-loureiro, I've already tried that, but I'm getting,

ERROR: for demo_wire_redis cannot stop container: cf606ae776ff9f65149ffa80a08ea0c6b8a50bed295177996785bb2145d5d5f3: Cannot kill container cf606ae776ff9f65149ffa80a08ea0c6b8a50bed295177996785bb2145d5d5f3: unknown error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused "permission denied" : unknown

for all the processes: