Closed DerSchwarzeJugo closed 6 months ago
I haven't seen this before, the getaddrinfo EAI_AGAIN elasticsearch
log entry indicates that the DNS lookup of the name 'elasticsearch' failed, however this DNS resolution is handled by Docker and has been the same for many years.
The ElasticsearchException[failed to bind service]
error seems to indicate that the port 9200 couldn't be bound, do you possibly have another service already bound on that port, such as another instance of elasticsearch running outside of Docker?
I haven't seen this before, the
getaddrinfo EAI_AGAIN elasticsearch
log entry indicates that the DNS lookup of the name 'elasticsearch' failed, however this DNS resolution is handled by Docker and has been the same for many years.
I have also never had any problems with Docker DNS, it usually worked as intended in the past.
The
ElasticsearchException[failed to bind service]
error seems to indicate that the port 9200 couldn't be bound, do you possibly have another service already bound on that port, such as another instance of elasticsearch running outside of Docker?
I do not have any other instance of elasticsearch running on this machine. Also if I check the output of netstat, I don't see any binded service on port 9200.
I see now that windows is not supported in the documentation requirements... does this also include when running over WSL?
The DNS error may be a consequence of the failed bind.
None of the core team have ever tested on Windows, I'd suggest using Linux or Mac to test the config out to see if it's WSL specifically causing the issues.
I would also suggest digging through the WSL settings to see if Docker has all the permissions it needs to do things like bind to ports on the host machine.
You might want to also search through the issues on this repo to see if there are any other users running on Windows and their experiences.
Just also a gentle reminder to use the issue templates, it saves a lot of time diagnosing issues when people are clear about their environment when posting the issue.
Well i found this Answer here where someone was able to set up with WSL.
I will try to setup the default portland-metro project, to see if I have maybe misconfigured something. If this does not work aswell, I have to find a solution to test it on Linux. Ist it Possible to run it inside a VM from Virtualbox maybe?
there seems to be some kind of weird behaviour.. after deleting all the contents of the data folder and running the build script again, the elasticsearch container does not restart anymore and has no errors.
Hi, I am trying to set up a custom instance, with the maps of switzerland. I have created a custom config in the directory projects/switzerland. I have run the provided script after doing all the config stuff (created .env, elasticsearch.yml, pelias.json, docker-compose.yml). As a starting point i used "projects/austria" and then changed the necessary parts in the files pelias.json and .env
I have tested the API an am able to send and receive requests over the endpoint "/search"
Describe the bug While creating the index it had some errors. When I try to create the index manually with "pelias elastic create" i run into this error
Log output of elastic in docker
Steps to Reproduce .env
docker-compose.yml
pelias.json
Expected behavior Clean Install and created Index, working setup..
Environment (please complete the following information): OS: Ubuntu WSL, Windows 10
Docker:
Docker Compose version v2.23.0-desktop.1