Re: No route to self
Assuming you are running docker it is most likely a firewall issue: Packets that originate from a docker container are seen from the host as coming from the ‘docker0’ interface. By default this traffic is blocked. sudo iptables -L -v -n --line-numbers Chain INPUT (policy ACCEPT 0 packets, 0 bytes) num pkts bytes target prot opt in out source destination 1 3633 281K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 20 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 3160 ACCEPT all -- docker0 * 0.0.0.0/0 0.0.0.0/0 4 13 968 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 54 256 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 6 1187 81739 REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited 70 0 LOGGINGall -- * * 0.0.0.0/0 0.0.0.0/0 To fix this issue, I added line #3. Note that everything that comes from ‘lo’ is wide open. I just duplicated that rule for ‘docker0’. sudo iptables -I INPUT 3 -i docker0 -j ACCEPT sudo service iptables save The line ‘3’ may be different depending on any other rules you may have added. On March 2, 2015 at 6:37:29 AM, wzcwts521 (wzcwts...@gmail.com) wrote: 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 you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/9KACzNoTfYk/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1425062730392-4071354.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.54f677d8.74b0dc51.3c8%40Matthews-MacBook-Pro.local. For more options, visit https://groups.google.com/d/optout.
Re: No route to self
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 you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1425062730392-4071354.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
No route to self
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* 10.52.207.36. I turned up trace logging on transport, but I'm not seeing it. [2014-08-02 02:45:15,044][TRACE][discovery.zen.ping.unicast] [Box IV] [2] failed to connect to [Box IV][Mx8kHzp6S1K-0_FiNp36VA][elk3][inet[/10.52.207.36:9300]] org.elasticsearch.transport.ConnectTransportException: [Box IV][inet[/10.52.207.36:9300]] connect_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:727) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:656) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:624) at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:146) at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:289) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Caused by: java.net.NoRouteToHostException: No route to host at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) ... 3 more [2014-08-02 02:45:15,045][WARN ][transport.netty ] [Box IV] exception caught on transport layer [[id: 0xd840123a]], closing connection java.net.NoRouteToHostException: No route to host at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1702c4f9-c19d-49f0-b5eb-f698f9e1e4d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: No route to self
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 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* 10.52.207.36. I turned up trace logging on transport, but I'm not seeing it. [2014-08-02 02:45:15,044][TRACE][discovery.zen.ping.unicast] [Box IV] [2] failed to connect to [Box IV][Mx8kHzp6S1K-0_FiNp36VA][elk3][inet[/ 10.52.207.36:9300]] org.elasticsearch.transport.ConnectTransportException: [Box IV][inet[/ 10.52.207.36:9300]] connect_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:727) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:656) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:624) at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:146) at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:289) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Caused by: java.net.NoRouteToHostException: No route to host at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) ... 3 more [2014-08-02 02:45:15,045][WARN ][transport.netty ] [Box IV] exception caught on transport layer [[id: 0xd840123a]], closing connection java.net.NoRouteToHostException: No route to host at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1702c4f9-c19d-49f0-b5eb-f698f9e1e4d0%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/1702c4f9-c19d-49f0-b5eb-f698f9e1e4d0%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624aXtqFjiTsN_zZHES%2BFMKZ381Gjv8Ug%3D3nMT9J892ZBTg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: No route to self
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 04:23:01,102][DEBUG][monitor.network ] [elk3] net_info
host [elk3]
eth0display_name [eth0]
address [/fe80:0:0:0:4c54:85ff:fed5:2080%eth0] [/172.17.0.8]
mtu [1500] multicast [false] ptp [false] loopback [false] up [true]
virtual [false]
lodisplay_name [lo]
address [/0:0:0:0:0:0:0:1%lo] [/127.0.0.1]
mtu [16436] multicast [false] ptp [false] loopback [true] up [true]
virtual [false]
[2014-08-02 04:23:01,968][DEBUG][transport.netty ] [elk3] Bound to
address [/172.17.0.8:9300]
[2014-08-02 04:23:01,969][INFO ][transport] [elk3]
bound_address {inet[/172.17.0.8:9300]}, publish_address
{inet[/10.52.207.36:9300]}
[2014-08-02 04:23:03,018][TRACE][discovery.zen.ping.unicast] [elk3] [1]
failed to connect to
[elk3][kpbZDtI9TxWL2cHahUQImQ][elk3][inet[/10.52.207.36:9300]]
org.elasticsearch.transport.ConnectTransportException:
[elk3][inet[/10.52.207.36:9300]] connect_timeout[30s]
at
org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:727)
at
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:656)
at
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:624)
at
org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:146)
at
org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:289)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)
On Friday, August 1, 2014 10:07:35 PM UTC-4, Mark Walkom wrote:
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 javascript:
web: www.campaignmonitor.com
On 2 August 2014 11:51, Matt Hughes hughe...@gmail.com javascript:
wrote:
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*
10.52.207.36. I turned up trace logging on transport, but I'm not seeing
it.
[2014-08-02 02:45:15,044][TRACE][discovery.zen.ping.unicast] [Box IV] [2]
failed to connect to [Box IV][Mx8kHzp6S1K-0_FiNp36VA][elk3][inet[/
10.52.207.36:9300]]
org.elasticsearch.transport.ConnectTransportException: [Box IV][inet[/
10.52.207.36:9300]] connect_timeout[30s]
at
org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:727)
at
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:656)
at
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:624)
at
org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:146)
at
org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:289)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
... 3 more
[2014-08-02 02:45:15,045][WARN ][transport.netty ] [Box IV]
exception caught on transport
Re: No route to self
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 sk:880435d477c0
LISTEN 0 128
:::9300 :::* ino:90693 sk:880258716800
LISTEN 0 128
:::9301 :::* ino:90701 sk:880437504080
LISTEN 0 128
:::9302 :::* ino:90709 sk:880435454840
LISTEN 0 128
:::22:::* ino:18069 sk:880436aec080
LISTEN 0 128
:::9303 :::* ino:90717 sk:8804350ac840
LISTEN 0 128
::1:631 :::* ino:17217
sk:880436aec800
LISTEN 0 128
:::9304 :::* ino:90725 sk:8804378de0c0
LISTEN 0 128
:::9305 :::* ino:90669 sk:88036aaf7080
LISTEN 0 128
:::9306 :::* ino:90733 sk:880435b92040
LISTEN 0 50
:::9000 :::* ino:91504 sk:88041454f840
LISTEN 0 128
:::443 :::* ino:90661 sk:880437504800
LISTEN 0 128
:::444 :::*
On Friday, August 1, 2014 11:30:06 PM UTC-4, Matt Hughes wrote:
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 04:23:01,102][DEBUG][monitor.network ] [elk3] net_info
host [elk3]
eth0display_name [eth0]
address [/fe80:0:0:0:4c54:85ff:fed5:2080%eth0] [/172.17.0.8]
mtu [1500] multicast [false] ptp [false] loopback [false] up
[true] virtual [false]
lodisplay_name [lo]
address [/0:0:0:0:0:0:0:1%lo] [/127.0.0.1]
mtu [16436] multicast [false] ptp [false] loopback [true] up
[true] virtual [false]
[2014-08-02 04:23:01,968][DEBUG][transport.netty ] [elk3] Bound
to address [/172.17.0.8:9300]
[2014-08-02 04:23:01,969][INFO ][transport] [elk3]
bound_address {inet[/172.17.0.8:9300]}, publish_address {inet[/
10.52.207.36:9300]}
[2014-08-02 04:23:03,018][TRACE][discovery.zen.ping.unicast] [elk3] [1]
failed to connect to [elk3][kpbZDtI9TxWL2cHahUQImQ][elk3][inet[/
10.52.207.36:9300]]
org.elasticsearch.transport.ConnectTransportException: [elk3][inet[/
10.52.207.36:9300]] connect_timeout[30s]
at
org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:727)
at
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:656)
at
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:624)
at
org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:146)
at
org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:289)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)
On Friday, August 1, 2014 10:07:35 PM UTC-4, Mark Walkom wrote:
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 hughe...@gmail.com wrote:
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* 10.52.207.36. I turned up trace logging on transport, but I'm not
seeing it.
[2014-08-02 02:45:15,044][TRACE][discovery.zen.ping.unicast] [Box IV]
[2] failed to connect to [Box IV][Mx8kHzp6S1K-0_FiNp36VA][elk3][inet[/
