Dynamodb, Failed to establish a new connection.
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 334
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 50
Description
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)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with deploy/docker-ephemeral/init.sh and deploy/docker-ephemeral/run.sh, then inspect docker-compose ps and the DynamoDB, Elasticsearch, and Cassandra service names. Trace why the services cannot resolve or connect from the running containers; done means the ephemeral environment starts and all listed services are reachable without connection or name-resolution errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, haskell
- Domain
- backend, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100