# Unicast Cluster / Host can't see its own publish\_host **URL:** \ **Category:** Elasticsearch\ **Created:** [January 5, 2015, 2:59pm UTC](https://discuss.elastic.co/t/unicast-cluster-host-cant-see-its-own-publish-host/21483 "2015-01-05T14:59:12Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mhughes](https://avatars.discourse-cdn.com/v4/letter/m/85e7bf/32.png) [@mhughes](https://discuss.elastic.co/u/mhughes)\ **Post date:** [January 5, 2015, 2:59pm UTC](https://discuss.elastic.co/t/unicast-cluster-host-cant-see-its-own-publish-host/21483/1 "2015-01-05T14:59:12Z")
In my VM environment, a VM can't actually see its public IP address. I have the following setup: network.publish\_host: 10.255.207.123 discovery.zen.ping.unicast.hosts: 10.255.207.123,10.255.207.124,10.255. 207.125 My VM can see 124 and 125 just fine, but due to issues completely unrelated to ES, it cannot see its own public IP. As a result, the logs on each machine fill up with these exceptions: org.elasticsearch.transport.ConnectTransportException: [elk2][inet[/10.255.207.123:9300]] connect\_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:807) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:741) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:714) at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:150) at org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:521) 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: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.255.207.123:9300 at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss. processConnectTimeout(NioClientBoss.java:139) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process (NioClientBoss.java:83) 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) I believe this is pretty innocuous as I've been running this way for 6 months, but I've always been curious as to way my node is even _trying_ to connect to itself like this? As it goes through the list of 'discovery.zen.ping.unicast.hosts', shouldn't it ignore itself? Maybe ES doesn't use 'network.publish\_host' to determine if the IP belongs to the current machine? -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 5, 2015, 10:42pm UTC](https://discuss.elastic.co/t/unicast-cluster-host-cant-see-its-own-publish-host/21483/2 "2015-01-05T22:42:26Z")
It sounds like because that isn't a local interface that ES is bound to it tries to access it. Are you using NAT on a higher layer? On 6 January 2015 at 01:59, Matt Hughes [hughes.matt@gmail.com](mailto:hughes.matt@gmail.com) wrote: > In my VM environment, a VM can't actually see its public IP address. I > have the following setup: > > network.publish\_host: 10.255.207.123 > discovery.zen.ping.unicast.hosts: 10.255.207.123,10.255.207.124,10.255. > 207.125 > > My VM can see 124 and 125 just fine, but due to issues completely > unrelated to ES, it cannot see its own public IP. As a result, the logs on > each machine fill up with these exceptions: > > org.elasticsearch.transport.ConnectTransportException: [elk2][inet[/ > 10.255.207.123:9300]] connect\_timeout[30s] > at > org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:807) > at > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:741) > at > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:714) > at > org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:150) > at > org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:521) > 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: org.elasticsearch.common.netty.channel.ConnectTimeoutException: > connection timed out: /10.255.207.123:9300 > at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss. > processConnectTimeout(NioClientBoss.java:139) > at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss. > process(NioClientBoss.java:83) > 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) > > I believe this is pretty innocuous as I've been running this way for 6 > months, but I've always been curious as to way my node is even _trying_ to > connect to itself like this? As it goes through the list of > 'discovery.zen.ping.unicast.hosts', shouldn't it ignore itself? Maybe ES > doesn't use 'network.publish\_host' to determine if the IP belongs to the > current machine? > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-4Zk90wSrM8Z6oqHR1LGNdLLSB4vcYVqdPp%2BvLWoRMgA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-4Zk90wSrM8Z6oqHR1LGNdLLSB4vcYVqdPp%2BvLWoRMgA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![mhughes](https://avatars.discourse-cdn.com/v4/letter/m/85e7bf/32.png) [@mhughes](https://discuss.elastic.co/u/mhughes)\ **Post date:** [January 6, 2015, 3:07pm UTC](https://discuss.elastic.co/t/unicast-cluster-host-cant-see-its-own-publish-host/21483/3 "2015-01-06T15:07:14Z")
Well ES is bound to 0.0.0.0. Each node _gets_ traffic from other nodes, it just can't communicate with its own public IP. My guess is that on normal systems where NetworkInterface.getNetworkInterfaces returns 10.255.207.123, Elasticsearch would not even try to connect to itself when going over the list of unicast.hosts. The problem -- I presume -- is that it should also use 'network.publish\_host', e.g.: val ipsOfSelf = NetworkInterface.getNetworkInterfaces.map ( \_.getIp ).toSet unicastHosts.foreach { host =\> if (!ipsOfSet.contains(host) && host != publishHostIp) { // check connectivity to other host in the cluster } } On Monday, January 5, 2015 5:42:55 PM UTC-5, Mark Walkom wrote: > It sounds like because that isn't a local interface that ES is bound to it > tries to access it. Are you using NAT on a higher layer? > > On 6 January 2015 at 01:59, Matt Hughes \<[hughe...@gmail.com](mailto:hughe...@gmail.com) \\> > wrote: > > > In my VM environment, a VM can't actually see its public IP address. I > > have the following setup: > > > > network.publish\_host: 10.255.207.123 > > discovery.zen.ping.unicast.hosts: 10.255.207.123,10.255.207.124,10.255. > > 207.125 > > > > My VM can see 124 and 125 just fine, but due to issues completely > > unrelated to ES, it cannot see its own public IP. As a result, the logs on > > each machine fill up with these exceptions: > > > > org.elasticsearch.transport.ConnectTransportException: [elk2][inet[/ > > 10.255.207.123:9300]] connect\_timeout[30s] > > at > > org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:807) > > at > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:741) > > at > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:714) > > at > > org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:150) > > at > > org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:521) > > 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: > > org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection > > timed out: /10.255.207.123:9300 > > at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss. > > processConnectTimeout(NioClientBoss.java:139) > > at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss. > > process(NioClientBoss.java:83) > > 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) > > > > I believe this is pretty innocuous as I've been running this way for 6 > > months, but I've always been curious as to way my node is even _trying_ to > > connect to itself like this? As it goes through the list of > > 'discovery.zen.ping.unicast.hosts', shouldn't it ignore itself? Maybe ES > > doesn't use 'network.publish\_host' to determine if the IP belongs to the > > current machine? > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/fa2e66cf-1f96-4c9c-8b69-bd146f868ec7%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/af1e823d-1695-4049-80d9-d00e7e84312d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/af1e823d-1695-4049-80d9-d00e7e84312d%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:40am UTC](https://discuss.elastic.co/t/unicast-cluster-host-cant-see-its-own-publish-host/21483/4 "2017-07-06T00:40:30Z")