Open OriHoch opened 7 years ago
check if elasticsearch is running and available on 192.168.170.195:9200 from both host and from inside the docker
you can run something like this to run commands from inside the docker instance:
docker exec -it docker-instance-name /bin/sh
(replace docker-instance-name with the actual instance name)
then, inside docker, you can do curl 192.168.170.195:9200
to check if elasticsearch is running
also, check elasticsearch logs for errors
sudo cat /var/log/elasticsearch/elasticsearch.log
@Libisch this is resolved? if not, please paste the logs
@OriHoch I ran the checks and everything looked o.k. Anyway, the error hasn't reoccurred since. I'll update if it happens again.
@Libisch commented on Sun Jul 02 2017
With all tests passing and pipelines running, process fails. See log:
@Libisch commented on Sun Jul 02 2017
@OriHoch
@OriHoch commented on Sun Jul 02 2017
looks like it can't connect to elasticsearch
@Libisch commented on Sun Jul 02 2017
I figured that one :) had some connection issues that were fixed by modifying the
network.host
in both docker-compose.override.yaml and elastisearch.yaml, but I'm not sure how to handle the timeout issue. It happens after the app is running for quite a while.