a solution of this issue?
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/No-route-to-self-tp4061098p4071354.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
You received this message because you are subscribed to a topic
Hi Matt
I am wondering if you have a solution of this issue?
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/No-route-to-self-tp4061098p4071354.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
You received this message because
Originally I was getting a bunch of No Route to Host errors and tracked
it down to being out of file handles. I have fixed the file handle,
problem, but I still keep getting No route to host errors; the odd thing
is, the error says it can't connect to itself: These logs are *from*
Can you put your config into a gist/pastebin?
ES isn't binding to loopback is it?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 2 August 2014 11:51, Matt Hughes hughes.m...@gmail.com wrote:
Originally I was
No, not loopback. I should caveat that this is running in a docker
container.
The only values I specify in my config are:
network.publish_host: 10.52.207.36
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: 10.52.207.32,10.52.207.33,10.52.207.36
[2014-08-02
Just a bit more info to show the port is bound on the machine.
[hostos ~]$ ss -aen6
State Recv-Q Send-Q Local
Address:PortPeer Address:Port
LISTEN 0 128
:::111 :::* ino:13048