-
-
Notifications
You must be signed in to change notification settings - Fork 258
Description
Describe the bug
Unable to start default pelias docker with default portland-metro project due to "Elasticsearch service did not come up, check configuration" error
Steps to Reproduce
- on a clear machine, logged as a sudo user i created a sh script taken from https://github.com/pelias/docker documentation
- git cloned my fork of repo (fork only differs from the original by adding a new region called wlkp - for later tests)
- edited the path/to/install to /home/{myname}/pelias folder that i created manually
- chmoded +x that sh script
- run the ./pelias.sh script
- during the process, i saw following errors:
Creating pelias _elasticsearch .. done
- pelias elastic wait
waiting for elasticsearch service to come up
...........................
Elasticsearch service did not come up, check configuration
- pelias elastic create
Creating pelias_schema_run ... done
Create index
Elasticsearch ERROR: 2020-09-15T11:53:21Z
Error: Request error, retrying
GET http://elasticsearch:9200/ => connect ECONNREFUSED 172.19.0.2:9200
[..]
Elasticsearch WARNING: 2020-09-15T11:53:21Z
Unable to revive connection http://elasticsearch:9200/
Elasticsearch WARNING: 2020-09-15T11:53:21Z
No living connections
[...]
unsupported elasticsearch version. try: >=7.4.2
- pelias download all
...
all next log items seem to be ok apart from tests.
Expected behavior
Elasticsearch should load and website api should return correct results?
Environment (please complete the following information):
Ubuntu Ubuntu 20.04 LTS Server 64bit
Docker version 19.03.12, build 48a66213fe
docker-compose version 1.27.2, build 18f557f9
Pastebin/Screenshots
Api works and returns data, but incomplete
[http://prntscr.com/uhnaf4]
References
As requested by @missinglink in issue #180 180 adding this a separate issue.