# \[node1\] failed to reconnect to node \[node1\]

**URL:** <https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959>\
**Category:** Elasticsearch\
**Created:** [March 28, 2015, 10:21am UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959 "2015-03-28T10:21:45Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Azman\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@Azman\_Ahmad](https://discuss.elastic.co/u/Azman_Ahmad)\
**Post date:** [March 28, 2015, 10:21am UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/1 "2015-03-28T10:21:45Z")

</div>

Both nodes running on AWS. Both sides pingbles and curlable. Had check  
resolution in this forum but the case is not similar at all. Badly need  
help as project meeting dateline. Please....

yml setting.  
network.publish\_host: 52.74.94.198  
network.host: 10.0.0.111

etc/hosts  
127.0.0.1 localhost  
10.0.0.246 DataStoreVM1  
10.0.0.111 DataStoreVM2

[2015-03-27 13:12:21,239][WARN][cluster.service] [DataStoreVM2]  
failed to connect to node  
[[DataStoreVM1][X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:9300]]{master=false}]  
org.elasticsearch.transport.ConnectTransportException:  
[DataStoreVM1][inet[/52.74.93.147: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$UpdateTask.run(InternalClusterService.java:411)  
at  
org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:745)  
Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
connection timed out: /52.74.93.147: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)  
... 3 more  
[2015-03-27 13:12:51,037][WARN][cluster.service] [DataStoreVM2]  
failed to reconnect to node  
[DataStoreVM2][dAjDjc-0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false,  
master=false}  
org.elasticsearch.transport.ConnectTransportException:  
[DataStoreVM2][inet[/52.74.94.198: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:1145)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:745)  
Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
connection timed out: /52.74.94.198: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)

ubuntu@ip-10-0-0-111:~$ ifconfig  
eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
collisions:0 txqueuelen:1000  
RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)

lo Link encap:Local Loopback  
inet addr:127.0.0.1 Mask:255.0.0.0  
inet6 addr: ::1/128 Scope:Host  
UP LOOPBACK RUNNING MTU:65536 Metric:1  
RX packets:2304 errors:0 dropped:0 overruns:0 frame:0  
TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0  
collisions:0 txqueuelen:0  
RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)

--  
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/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**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:** [March 28, 2015, 9:08pm UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/2 "2015-03-28T21:08:57Z")

</div>

Are you using multicast or unicast?

On 28 March 2015 at 21:21, Azman Ahmad [lesdesprado2012@gmail.com](mailto:lesdesprado2012@gmail.com) wrote:

> Both nodes running on AWS. Both sides pingbles and curlable. Had check  
> resolution in this forum but the case is not similar at all. Badly need  
> help as project meeting dateline. Please....
> 
> yml setting.  
> network.publish\_host: 52.74.94.198  
> network.host: 10.0.0.111
> 
> etc/hosts  
> 127.0.0.1 localhost  
> 10.0.0.246 DataStoreVM1  
> 10.0.0.111 DataStoreVM2
> 
> [2015-03-27 13:12:21,239][WARN][cluster.service] [DataStoreVM2]  
> failed to connect to node  
> [[DataStoreVM1][X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:9300  
> ]]{master=false}]  
> org.elasticsearch.transport.ConnectTransportException:  
> [DataStoreVM1][inet[/52.74.93.147: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$UpdateTask.run(InternalClusterService.java:411)  
> at  
> org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)  
> at  
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
> at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(Thread.java:745)  
> Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> connection timed out: /52.74.93.147: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)  
> ... 3 more  
> [2015-03-27 13:12:51,037][WARN][cluster.service] [DataStoreVM2]  
> failed to reconnect to node  
> [DataStoreVM2][dAjDjc-0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false,  
> master=false}  
> org.elasticsearch.transport.ConnectTransportException:  
> [DataStoreVM2][inet[/52.74.94.198: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:1145)  
> at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(Thread.java:745)  
> Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> connection timed out: /52.74.94.198: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)
> 
> ubuntu@ip-10-0-0-111:~$ ifconfig  
> eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
> inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
> inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
> UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
> RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
> TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
> collisions:0 txqueuelen:1000  
> RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)
> 
> lo Link encap:Local Loopback  
> inet addr:127.0.0.1 Mask:255.0.0.0  
> inet6 addr: ::1/128 Scope:Host  
> UP LOOPBACK RUNNING MTU:65536 Metric:1  
> RX packets:2304 errors:0 dropped:0 overruns:0 frame:0  
> TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0  
> collisions:0 txqueuelen:0  
> RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)
> 
> --  
> 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/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%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-gFrHK%2BDZrfcjO\_tZ3eQ\_i3xDBN2vTPfjytE-eJhQDbw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-gFrHK%2BDZrfcjO_tZ3eQ_i3xDBN2vTPfjytE-eJhQDbw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![mohdjohari1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@mohdjohari1](https://discuss.elastic.co/u/mohdjohari1)\
**Post date:** [March 29, 2015, 12:48am UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/3 "2015-03-29T00:48:38Z")

</div>

unicast.

here  
discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts : ["10.0.0.187:9300","x.x.x.x:9300","x.x.x.x:9300"] \*x.x.x.x = VMs in digitalocean  
#discovery.zen.ping.unicast.hosts : ["10.0.0.187"]  
discovery.zen.ping.timeout: 180s  
discovery.zen.minimum\_master\_nodes: 2

just to share the error that i got when i played with yml

network.bind\_host: 10.0.0.111  
network.publish\_host: 52.74.94.198  
network.host: 127.0.0.1

log :  
detected\_master [I love S & DataStoreVM2] [node1]failed to connect to node [node1][....  
[transport] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]}, publish\_address {inet[/52.74.94.198:9300]}  
[http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]}, publish\_address {inet[/127.0.0.1:9200]}  
,,,,DataStoreVM2] failed to reconnect to node [DataSto....

Network.bind\_host: 127.0.0.1  
network.publish\_host: 52.74.94.198  
network.host: 10.0.0.111  
Log=  
failed to send join request to master [[I love Siti.... [transport] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/52.74.94.198:9300]  
[http] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/10.0.0.111:9200]

network.bind\_host: 127.0.0.1  
network.publish\_host: 10.0.0.111  
network.host: 10.0.0.111  
Log=  
DataStoreVM2] failed to reconnect to node [DataSto....  
bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/10.0.0.111:9300]}  
bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/10.0.0.111:9200]}

Network.bind\_host: 127.0.0.1  
network.publish\_host: 52.74.94.198  
network.host: 10.0.0.111  
http.host: 52.74.94.198  
Log =

- BindHttpException[Failed to bind to [9200]]  
ChannelException[Failed to bind to: /52.74.94.198:9200]  
BindException[Cannot assign requested address]

---

<div class="post-metadata">

**Author:** ![Azman\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@Azman\_Ahmad](https://discuss.elastic.co/u/Azman_Ahmad)\
**Post date:** [March 29, 2015, 12:56am UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/4 "2015-03-29T00:56:38Z")

</div>

unicast.

here  
discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts :  
["10.0.0.187:9300","x.x.x.x:9300","x.x.x.x:9300"] \*x.x.x.x = VMs in  
digitalocean  
#discovery.zen.ping.unicast.hosts : ["10.0.0.187"]  
discovery.zen.ping.timeout: 180s  
discovery.zen.minimum\_master\_nodes: 2

just to share the error that i got when i played with yml

network.bind\_host: 10.0.0.111  
network.publish\_host: 52.74.94.198  
network.host: 127.0.0.1

log :  
detected\_master [I love S & DataStoreVM2] [node1]failed to connect to node  
[node1][....  
[transport] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]},  
publish\_address {inet[/52.74.94.198:9300]}  
[http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]},  
publish\_address {inet[/127.0.0.1:9200]}  
,,,,DataStoreVM2] failed to reconnect to node [DataSto....

Network.bind\_host: 127.0.0.1  
network.publish\_host: 52.74.94.198  
network.host: 10.0.0.111  
Log=  
failed to send join request to master [[I love Siti.... [transport] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9300]},  
publish\_address {inet[/52.74.94.198:9300]  
[http] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9200]},  
publish\_address {inet[/10.0.0.111:9200]

network.bind\_host: 127.0.0.1  
network.publish\_host: 10.0.0.111  
network.host: 10.0.0.111  
Log=  
DataStoreVM2] failed to reconnect to node [DataSto....  
bound\_address {inet[/127.0.0.1:9300]}, publish\_address  
{inet[/10.0.0.111:9300]}  
bound\_address {inet[/127.0.0.1:9200]}, publish\_address  
{inet[/10.0.0.111:9200]}

Network.bind\_host: 127.0.0.1  
network.publish\_host: 52.74.94.198  
network.host: 10.0.0.111  
http.host: 52.74.94.198  
Log =

- BindHttpException[Failed to bind to [9200]]  
ChannelException[Failed to bind to: /52.74.94.198:9200]  
BindException[Cannot assign requested address]

On Sunday, March 29, 2015 at 5:09:26 AM UTC+8, Mark Walkom wrote:

> Are you using multicast or unicast?
> 
> On 28 March 2015 at 21:21, Azman Ahmad \<[lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) \<javascript:\>
> 
> > wrote:
> 
> > Both nodes running on AWS. Both sides pingbles and curlable. Had check  
> > resolution in this forum but the case is not similar at all. Badly need  
> > help as project meeting dateline. Please....
> > 
> > yml setting.  
> > network.publish\_host: 52.74.94.198  
> > network.host: 10.0.0.111
> > 
> > etc/hosts  
> > 127.0.0.1 localhost  
> > 10.0.0.246 DataStoreVM1  
> > 10.0.0.111 DataStoreVM2
> > 
> > [2015-03-27 13:12:21,239][WARN][cluster.service]  
> > [DataStoreVM2] failed to connect to node  
> > [[DataStoreVM1][X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:9300]]{master=false}]  
> > org.elasticsearch.transport.ConnectTransportException:  
> > [DataStoreVM1][inet[/52.74.93.147: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$UpdateTask.run(InternalClusterService.java:411)  
> > at  
> > org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)  
> > at  
> > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
> > at  
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > at java.lang.Thread.run(Thread.java:745)  
> > Caused by:  
> > org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection  
> > timed out: /52.74.93.147: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)  
> > ... 3 more  
> > [2015-03-27 13:12:51,037][WARN][cluster.service]  
> > [DataStoreVM2] failed to reconnect to node  
> > [DataStoreVM2][dAjDjc-0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false,  
> > master=false}  
> > org.elasticsearch.transport.ConnectTransportException:  
> > [DataStoreVM2][inet[/52.74.94.198: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:1145)  
> > at  
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > at java.lang.Thread.run(Thread.java:745)  
> > Caused by:  
> > org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection  
> > timed out: /52.74.94.198: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)
> > 
> > ubuntu@ip-10-0-0-111:~$ ifconfig  
> > eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
> > inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
> > inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
> > UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
> > RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
> > TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
> > collisions:0 txqueuelen:1000  
> > RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)
> > 
> > lo Link encap:Local Loopback  
> > inet addr:127.0.0.1 Mask:255.0.0.0  
> > inet6 addr: ::1/128 Scope:Host  
> > UP LOOPBACK RUNNING MTU:65536 Metric:1  
> > RX packets:2304 errors:0 dropped:0 overruns:0 frame:0  
> > TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0  
> > collisions:0 txqueuelen:0  
> > RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)
> > 
> > --  
> > 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) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%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/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Azman\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@Azman\_Ahmad](https://discuss.elastic.co/u/Azman_Ahmad)\
**Post date:** [March 29, 2015, 2:19am UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/5 "2015-03-29T02:19:12Z")

</div>

BTW, im not using elasticsearch-cloud-aws plugin.

On Sunday, March 29, 2015 at 8:56:38 AM UTC+8, Azman Ahmad wrote:

> unicast.
> 
> here  
> discovery.zen.ping.multicast.enabled: false  
> discovery.zen.ping.unicast.hosts : ["10.0.0.187:9300","x.x.x.x:9300","x.x.x.x:9300"]  
> \*x.x.x.x = VMs in digitalocean  
> #discovery.zen.ping.unicast.hosts : ["10.0.0.187"]  
> discovery.zen.ping.timeout: 180s  
> discovery.zen.minimum\_master\_nodes: 2
> 
> just to share the error that i got when i played with yml
> 
> network.bind\_host: 10.0.0.111  
> network.publish\_host: 52.74.94.198  
> network.host: 127.0.0.1
> 
> log :  
> detected\_master [I love S & DataStoreVM2] [node1]failed to connect to  
> node [node1][....  
> [transport] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]},  
> publish\_address {inet[/52.74.94.198:9300]}  
> [http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]},  
> publish\_address {inet[/127.0.0.1:9200]}  
> ,,,,DataStoreVM2] failed to reconnect to node [DataSto....
> 
> Network.bind\_host: 127.0.0.1  
> network.publish\_host: 52.74.94.198  
> network.host: 10.0.0.111  
> Log=  
> failed to send join request to master [[I love Siti.... [transport] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9300]},  
> publish\_address {inet[/52.74.94.198:9300]  
> [http] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9200]},  
> publish\_address {inet[/10.0.0.111:9200]
> 
> network.bind\_host: 127.0.0.1  
> network.publish\_host: 10.0.0.111  
> network.host: 10.0.0.111  
> Log=  
> DataStoreVM2] failed to reconnect to node [DataSto....  
> bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/  
> 10.0.0.111:9300]}  
> bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/  
> 10.0.0.111:9200]}
> 
> Network.bind\_host: 127.0.0.1  
> network.publish\_host: 52.74.94.198  
> network.host: 10.0.0.111  
> http.host: 52.74.94.198  
> Log =
> 
> - BindHttpException[Failed to bind to [9200]]  
> ChannelException[Failed to bind to: /52.74.94.198:9200]  
> BindException[Cannot assign requested address]
> 
> On Sunday, March 29, 2015 at 5:09:26 AM UTC+8, Mark Walkom wrote:
> 
> > Are you using multicast or unicast?
> > 
> > On 28 March 2015 at 21:21, Azman Ahmad [lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) wrote:
> > 
> > > Both nodes running on AWS. Both sides pingbles and curlable. Had check  
> > > resolution in this forum but the case is not similar at all. Badly need  
> > > help as project meeting dateline. Please....
> > > 
> > > yml setting.  
> > > network.publish\_host: 52.74.94.198  
> > > network.host: 10.0.0.111
> > > 
> > > etc/hosts  
> > > 127.0.0.1 localhost  
> > > 10.0.0.246 DataStoreVM1  
> > > 10.0.0.111 DataStoreVM2
> > > 
> > > [2015-03-27 13:12:21,239][WARN][cluster.service]  
> > > [DataStoreVM2] failed to connect to node  
> > > [[DataStoreVM1][X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:9300]]{master=false}]  
> > > org.elasticsearch.transport.ConnectTransportException:  
> > > [DataStoreVM1][inet[/52.74.93.147: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$UpdateTask.run(InternalClusterService.java:411)  
> > > at  
> > > org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:745)  
> > > Caused by:  
> > > org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection  
> > > timed out: /52.74.93.147: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)  
> > > ... 3 more  
> > > [2015-03-27 13:12:51,037][WARN][cluster.service]  
> > > [DataStoreVM2] failed to reconnect to node  
> > > [DataStoreVM2][dAjDjc-0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false,  
> > > master=false}  
> > > org.elasticsearch.transport.ConnectTransportException:  
> > > [DataStoreVM2][inet[/52.74.94.198: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:1145)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:745)  
> > > Caused by:  
> > > org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection  
> > > timed out: /52.74.94.198: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)
> > > 
> > > ubuntu@ip-10-0-0-111:~$ ifconfig  
> > > eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
> > > inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
> > > inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
> > > UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
> > > RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
> > > TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
> > > collisions:0 txqueuelen:1000  
> > > RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)
> > > 
> > > lo Link encap:Local Loopback  
> > > inet addr:127.0.0.1 Mask:255.0.0.0  
> > > inet6 addr: ::1/128 Scope:Host  
> > > UP LOOPBACK RUNNING MTU:65536 Metric:1  
> > > RX packets:2304 errors:0 dropped:0 overruns:0 frame:0  
> > > TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0  
> > > collisions:0 txqueuelen:0  
> > > RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)
> > > 
> > > --  
> > > 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/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%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/29a052bc-490c-4cf8-bd94-12a941a36dcd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/29a052bc-490c-4cf8-bd94-12a941a36dcd%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**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:** [March 29, 2015, 7:47am UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/6 "2015-03-29T07:47:36Z")

</div>

You're building a cluster between your AWS instances and your DigitalOcean  
ones, am I understanding this correctly?

On 29 March 2015 at 11:56, Azman Ahmad [lesdesprado2012@gmail.com](mailto:lesdesprado2012@gmail.com) wrote:

> unicast.
> 
> here  
> discovery.zen.ping.multicast.enabled: false  
> discovery.zen.ping.unicast.hosts : ["10.0.0.187:9300","x.x.x.x:9300","x.x.x.x:9300"]  
> \*x.x.x.x = VMs in digitalocean  
> #discovery.zen.ping.unicast.hosts : ["10.0.0.187"]  
> discovery.zen.ping.timeout: 180s  
> discovery.zen.minimum\_master\_nodes: 2
> 
> just to share the error that i got when i played with yml
> 
> network.bind\_host: 10.0.0.111  
> network.publish\_host: 52.74.94.198  
> network.host: 127.0.0.1
> 
> log :  
> detected\_master [I love S & DataStoreVM2] [node1]failed to connect to  
> node [node1][....  
> [transport] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]},  
> publish\_address {inet[/52.74.94.198:9300]}  
> [http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]},  
> publish\_address {inet[/127.0.0.1:9200]}  
> ,,,,DataStoreVM2] failed to reconnect to node [DataSto....
> 
> Network.bind\_host: 127.0.0.1  
> network.publish\_host: 52.74.94.198  
> network.host: 10.0.0.111  
> Log=  
> failed to send join request to master [[I love Siti.... [transport] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9300]},  
> publish\_address {inet[/52.74.94.198:9300]  
> [http] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9200]},  
> publish\_address {inet[/10.0.0.111:9200]
> 
> network.bind\_host: 127.0.0.1  
> network.publish\_host: 10.0.0.111  
> network.host: 10.0.0.111  
> Log=  
> DataStoreVM2] failed to reconnect to node [DataSto....  
> bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/  
> 10.0.0.111:9300]}  
> bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/  
> 10.0.0.111:9200]}
> 
> Network.bind\_host: 127.0.0.1  
> network.publish\_host: 52.74.94.198  
> network.host: 10.0.0.111  
> http.host: 52.74.94.198  
> Log =
> 
> - BindHttpException[Failed to bind to [9200]]  
> ChannelException[Failed to bind to: /52.74.94.198:9200]  
> BindException[Cannot assign requested address]
> 
> On Sunday, March 29, 2015 at 5:09:26 AM UTC+8, Mark Walkom wrote:
> 
> > Are you using multicast or unicast?
> > 
> > On 28 March 2015 at 21:21, Azman Ahmad [lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) wrote:
> > 
> > > Both nodes running on AWS. Both sides pingbles and curlable. Had check  
> > > resolution in this forum but the case is not similar at all. Badly need  
> > > help as project meeting dateline. Please....
> > > 
> > > yml setting.  
> > > network.publish\_host: 52.74.94.198  
> > > network.host: 10.0.0.111
> > > 
> > > etc/hosts  
> > > 127.0.0.1 localhost  
> > > 10.0.0.246 DataStoreVM1  
> > > 10.0.0.111 DataStoreVM2
> > > 
> > > [2015-03-27 13:12:21,239][WARN][cluster.service]  
> > > [DataStoreVM2] failed to connect to node [[DataStoreVM1][  
> > > X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:  
> > > 9300]]{master=false}]  
> > > org.elasticsearch.transport.ConnectTransportException:  
> > > [DataStoreVM1][inet[/52.74.93.147: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$  
> > > UpdateTask.run(InternalClusterService.java:411)  
> > > at org.elasticsearch.common.util.concurrent.  
> > > PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(  
> > > PrioritizedEsThreadPoolExecutor.java:153)  
> > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > ThreadPoolExecutor.java:1145)  
> > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:745)  
> > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > connection timed out: /52.74.93.147: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)  
> > > ... 3 more  
> > > [2015-03-27 13:12:51,037][WARN][cluster.service]  
> > > [DataStoreVM2] failed to reconnect to node [DataStoreVM2][dAjDjc-  
> > > 0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false,  
> > > master=false}  
> > > org.elasticsearch.transport.ConnectTransportException:  
> > > [DataStoreVM2][inet[/52.74.94.198: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:1145)  
> > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:745)  
> > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > connection timed out: /52.74.94.198: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)
> > > 
> > > ubuntu@ip-10-0-0-111:~$ ifconfig  
> > > eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
> > > inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
> > > inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
> > > UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
> > > RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
> > > TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
> > > collisions:0 txqueuelen:1000  
> > > RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)
> > > 
> > > lo Link encap:Local Loopback  
> > > inet addr:127.0.0.1 Mask:255.0.0.0  
> > > inet6 addr: ::1/128 Scope:Host  
> > > UP LOOPBACK RUNNING MTU:65536 Metric:1  
> > > RX packets:2304 errors:0 dropped:0 overruns:0 frame:0  
> > > TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0  
> > > collisions:0 txqueuelen:0  
> > > RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)
> > > 
> > > --  
> > > 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/](https://groups.google.com/d/)  
> > > msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%  
> > > [40googlegroups.com](http://40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%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/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%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-K52yddFas-W9B\_PVDH8UaOT6QpmZkYs%3DNhESDdURafw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-K52yddFas-W9B_PVDH8UaOT6QpmZkYs%3DNhESDdURafw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![mohdjohari1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@mohdjohari1](https://discuss.elastic.co/u/mohdjohari1)\
**Post date:** [March 29, 2015, 11:03am UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/7 "2015-03-29T11:03:29Z")

</div>

Yes, the plan is to decommision all vms in digitalocean. Before doing so, all data will be re-populated into aws then retire vms in digitalocean one by one. In aws i hv private & public ip while in Digitalocean all public ip. Thanks.

🚲

On Mar 29, 2015, at 3:48 PM, "Mark Walkom-2 [via Elasticsearch Users]" [ml-node+s115913n4072784h33@n3.nabble.com](mailto:ml-node+s115913n4072784h33@n3.nabble.com) wrote:

You're building a cluster between your AWS instances and your DigitalOcean ones, am I understanding this correctly?

> On 29 March 2015 at 11:56, Azman Ahmad \<[hidden email]\> wrote:  
> unicast.
> 
> here  
> discovery.zen.ping.multicast.enabled: false  
> discovery.zen.ping.unicast.hosts : ["10.0.0.187:9300","x.x.x.x:9300","x.x.x.x:9300"] \*x.x.x.x = VMs in digitalocean  
> #discovery.zen.ping.unicast.hosts : ["10.0.0.187"]  
> discovery.zen.ping.timeout: 180s  
> discovery.zen.minimum\_master\_nodes: 2
> 
> just to share the error that i got when i played with yml
> 
> network.bind\_host: 10.0.0.111  
> network.publish\_host: 52.74.94.198  
> network.host: 127.0.0.1
> 
> log :  
> detected\_master [I love S & DataStoreVM2] [node1]failed to connect to node [node1][....  
> [transport] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]}, publish\_address {inet[/52.74.94.198:9300]}  
> [http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]}, publish\_address {inet[/127.0.0.1:9200]}  
> ,,,,DataStoreVM2] failed to reconnect to node [DataSto....
> 
> Network.bind\_host: 127.0.0.1  
> network.publish\_host: 52.74.94.198  
> network.host: 10.0.0.111  
> Log=  
> failed to send join request to master [[I love Siti.... [transport] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/52.74.94.198:9300]  
> [http] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/10.0.0.111:9200]
> 
> network.bind\_host: 127.0.0.1  
> network.publish\_host: 10.0.0.111  
> network.host: 10.0.0.111  
> Log=  
> DataStoreVM2] failed to reconnect to node [DataSto....  
> bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/10.0.0.111:9300]}  
> bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/10.0.0.111:9200]}
> 
> Network.bind\_host: 127.0.0.1  
> network.publish\_host: 52.74.94.198  
> network.host: 10.0.0.111  
> http.host: 52.74.94.198  
> Log =
> 
> - BindHttpException[Failed to bind to [9200]]  
> ChannelException[Failed to bind to: /52.74.94.198:9200]  
> BindException[Cannot assign requested address]
> 
> > On Sunday, March 29, 2015 at 5:09:26 AM UTC+8, Mark Walkom wrote:  
> > Are you using multicast or unicast?
> > 
> > > On 28 March 2015 at 21:21, Azman Ahmad \<[hidden email]\> wrote:  
> > > Both nodes running on AWS. Both sides pingbles and curlable. Had check resolution in this forum but the case is not similar at all. Badly need help as project meeting dateline. Please....
> > > 
> > > yml setting.  
> > > network.publish\_host: 52.74.94.198  
> > > network.host: 10.0.0.111
> > > 
> > > etc/hosts  
> > > 127.0.0.1 localhost  
> > > 10.0.0.246 DataStoreVM1  
> > > 10.0.0.111 DataStoreVM2
> > > 
> > > [2015-03-27 13:12:21,239][WARN][cluster.service] [DataStoreVM2] failed to connect to node [[DataStoreVM1][X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:9300]]{master=false}]  
> > > org.elasticsearch.transport.ConnectTransportException: [DataStoreVM1][inet[/52.74.93.147: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$UpdateTask.run(InternalClusterService.java:411)  
> > > at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)  
> > > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
> > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:745)  
> > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /52.74.93.147: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)  
> > > ... 3 more  
> > > [2015-03-27 13:12:51,037][WARN][cluster.service] [DataStoreVM2] failed to reconnect to node [DataStoreVM2][dAjDjc-0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false, master=false}  
> > > org.elasticsearch.transport.ConnectTransportException: [DataStoreVM2][inet[/52.74.94.198: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:1145)  
> > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:745)  
> > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /52.74.94.198: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)
> > > 
> > > ubuntu@ip-10-0-0-111:~$ ifconfig  
> > > eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
> > > inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
> > > inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
> > > UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
> > > RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
> > > TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
> > > collisions:0 txqueuelen:1000  
> > > RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)
> > > 
> > > ## lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:2304 errors:0 dropped:0 overruns:0 frame:0 TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)
> > > 
> > > 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/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com).  
> > > 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 [hidden email].  
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com).  
> 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 [hidden email].  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-K52yddFas-W9B\_PVDH8UaOT6QpmZkYs%3DNhESDdURafw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-K52yddFas-W9B_PVDH8UaOT6QpmZkYs%3DNhESDdURafw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

If you reply to this email, your message will be added to the discussion below:  
[http://elasticsearch-users.115913.n3.nabble.com/node1-failed-to-reconnect-to-node-node1-tp4072759p4072784.html](http://elasticsearch-users.115913.n3.nabble.com/node1-failed-to-reconnect-to-node-node1-tp4072759p4072784.html)  
To unsubscribe from [node1] failed to reconnect to node [node1], click here.  
NAML

---

<div class="post-metadata">

**Author:** ![Azman\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@Azman\_Ahmad](https://discuss.elastic.co/u/Azman_Ahmad)\
**Post date:** [March 29, 2015, 2:33pm UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/8 "2015-03-29T14:33:30Z")

</div>

Yes, the plan was to decommision all vms in digitalocean. Before doing so,  
all data will be re-populated during clustering into aws then retire vms in  
digitalocean one by one. In aws i hv private & public ip while in  
Digitalocean all public ip. Thanks.

On Sunday, March 29, 2015 at 3:48:05 PM UTC+8, Mark Walkom wrote:

> You're building a cluster between your AWS instances and your DigitalOcean  
> ones, am I understanding this correctly?
> 
> On 29 March 2015 at 11:56, Azman Ahmad \<[lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) \<javascript:\>
> 
> > wrote:
> 
> > unicast.
> > 
> > here  
> > discovery.zen.ping.multicast.enabled: false  
> > discovery.zen.ping.unicast.hosts : ["10.0.0.187:9300","x.x.x.x:9300","x.x.x.x:9300"]  
> > \*x.x.x.x = VMs in digitalocean  
> > #discovery.zen.ping.unicast.hosts : ["10.0.0.187"]  
> > discovery.zen.ping.timeout: 180s  
> > discovery.zen.minimum\_master\_nodes: 2
> > 
> > just to share the error that i got when i played with yml
> > 
> > network.bind\_host: 10.0.0.111  
> > network.publish\_host: 52.74.94.198  
> > network.host: 127.0.0.1
> > 
> > log :  
> > detected\_master [I love S & DataStoreVM2] [node1]failed to connect to  
> > node [node1][....  
> > [transport] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]},  
> > publish\_address {inet[/52.74.94.198:9300]}  
> > [http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]},  
> > publish\_address {inet[/127.0.0.1:9200]}  
> > ,,,,DataStoreVM2] failed to reconnect to node [DataSto....
> > 
> > Network.bind\_host: 127.0.0.1  
> > network.publish\_host: 52.74.94.198  
> > network.host: 10.0.0.111  
> > Log=  
> > failed to send join request to master [[I love Siti.... [transport] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9300]},  
> > publish\_address {inet[/52.74.94.198:9300]  
> > [http] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9200]},  
> > publish\_address {inet[/10.0.0.111:9200]
> > 
> > network.bind\_host: 127.0.0.1  
> > network.publish\_host: 10.0.0.111  
> > network.host: 10.0.0.111  
> > Log=  
> > DataStoreVM2] failed to reconnect to node [DataSto....  
> > bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/  
> > 10.0.0.111:9300]}  
> > bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/  
> > 10.0.0.111:9200]}
> > 
> > Network.bind\_host: 127.0.0.1  
> > network.publish\_host: 52.74.94.198  
> > network.host: 10.0.0.111  
> > http.host: 52.74.94.198  
> > Log =
> > 
> > - BindHttpException[Failed to bind to [9200]]  
> > ChannelException[Failed to bind to: /52.74.94.198:9200]  
> > BindException[Cannot assign requested address]
> > 
> > On Sunday, March 29, 2015 at 5:09:26 AM UTC+8, Mark Walkom wrote:
> > 
> > > Are you using multicast or unicast?
> > > 
> > > On 28 March 2015 at 21:21, Azman Ahmad [lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) wrote:
> > > 
> > > > Both nodes running on AWS. Both sides pingbles and curlable. Had check  
> > > > resolution in this forum but the case is not similar at all. Badly need  
> > > > help as project meeting dateline. Please....
> > > > 
> > > > yml setting.  
> > > > network.publish\_host: 52.74.94.198  
> > > > network.host: 10.0.0.111
> > > > 
> > > > etc/hosts  
> > > > 127.0.0.1 localhost  
> > > > 10.0.0.246 DataStoreVM1  
> > > > 10.0.0.111 DataStoreVM2
> > > > 
> > > > [2015-03-27 13:12:21,239][WARN][cluster.service]  
> > > > [DataStoreVM2] failed to connect to node [[DataStoreVM1][  
> > > > X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:  
> > > > 9300]]{master=false}]  
> > > > org.elasticsearch.transport.ConnectTransportException:  
> > > > [DataStoreVM1][inet[/52.74.93.147: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$  
> > > > UpdateTask.run(InternalClusterService.java:411)  
> > > > at org.elasticsearch.common.util.concurrent.  
> > > > PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(  
> > > > PrioritizedEsThreadPoolExecutor.java:153)  
> > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > ThreadPoolExecutor.java:1145)  
> > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > ThreadPoolExecutor.java:615)  
> > > > at java.lang.Thread.run(Thread.java:745)  
> > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > connection timed out: /52.74.93.147: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)  
> > > > ... 3 more  
> > > > [2015-03-27 13:12:51,037][WARN][cluster.service]  
> > > > [DataStoreVM2] failed to reconnect to node [DataStoreVM2][dAjDjc-  
> > > > 0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false,  
> > > > master=false}  
> > > > org.elasticsearch.transport.ConnectTransportException:  
> > > > [DataStoreVM2][inet[/52.74.94.198: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:1145)  
> > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > ThreadPoolExecutor.java:615)  
> > > > at java.lang.Thread.run(Thread.java:745)  
> > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > connection timed out: /52.74.94.198: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)
> > > > 
> > > > ubuntu@ip-10-0-0-111:~$ ifconfig  
> > > > eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
> > > > inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
> > > > inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
> > > > UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
> > > > RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
> > > > TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
> > > > collisions:0 txqueuelen:1000  
> > > > RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)
> > > > 
> > > > lo Link encap:Local Loopback  
> > > > inet addr:127.0.0.1 Mask:255.0.0.0  
> > > > inet6 addr: ::1/128 Scope:Host  
> > > > UP LOOPBACK RUNNING MTU:65536 Metric:1  
> > > > RX packets:2304 errors:0 dropped:0 overruns:0 frame:0  
> > > > TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0  
> > > > collisions:0 txqueuelen:0  
> > > > RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)
> > > > 
> > > > --  
> > > > 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/](https://groups.google.com/d/)  
> > > > msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%  
> > > > [40googlegroups.com](http://40googlegroups.com)  
> > > > [https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > > To view this discussion on the web visit  
> > > [https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%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/e36a9c63-7aad-4f9e-87a9-0a15f265cd95%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e36a9c63-7aad-4f9e-87a9-0a15f265cd95%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Azman\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@Azman\_Ahmad](https://discuss.elastic.co/u/Azman_Ahmad)\
**Post date:** [March 29, 2015, 3:06pm UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/9 "2015-03-29T15:06:02Z")

</div>

Additional info, the firewall ports 9200-9400 for public ip in aws  
purposely is not open to communicate among VMs in aws due to security  
reason.

On Sunday, March 29, 2015 at 10:33:30 PM UTC+8, Azman Ahmad wrote:

> Yes, the plan was to decommision all vms in digitalocean. Before doing so,  
> all data will be re-populated during clustering into aws then retire vms in  
> digitalocean one by one. In aws i hv private & public ip while in  
> Digitalocean all public ip. Thanks.
> 
> On Sunday, March 29, 2015 at 3:48:05 PM UTC+8, Mark Walkom wrote:
> 
> > You're building a cluster between your AWS instances and your  
> > DigitalOcean ones, am I understanding this correctly?
> > 
> > On 29 March 2015 at 11:56, Azman Ahmad [lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) wrote:
> > 
> > > unicast.
> > > 
> > > here  
> > > discovery.zen.ping.multicast.enabled: false  
> > > discovery.zen.ping.unicast.hosts : ["10.0.0.187:9300","x.x.x.x:9300","x.x.x.x:9300"]  
> > > \*x.x.x.x = VMs in digitalocean  
> > > #discovery.zen.ping.unicast.hosts : ["10.0.0.187"]  
> > > discovery.zen.ping.timeout: 180s  
> > > discovery.zen.minimum\_master\_nodes: 2
> > > 
> > > just to share the error that i got when i played with yml
> > > 
> > > network.bind\_host: 10.0.0.111  
> > > network.publish\_host: 52.74.94.198  
> > > network.host: 127.0.0.1
> > > 
> > > log :  
> > > detected\_master [I love S & DataStoreVM2] [node1]failed to connect to  
> > > node [node1][....  
> > > [transport] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]},  
> > > publish\_address {inet[/52.74.94.198:9300]}  
> > > [http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]},  
> > > publish\_address {inet[/127.0.0.1:9200]}  
> > > ,,,,DataStoreVM2] failed to reconnect to node [DataSto....
> > > 
> > > Network.bind\_host: 127.0.0.1  
> > > network.publish\_host: 52.74.94.198  
> > > network.host: 10.0.0.111  
> > > Log=  
> > > failed to send join request to master [[I love Siti.... [transport] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9300]},  
> > > publish\_address {inet[/52.74.94.198:9300]  
> > > [http] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9200]},  
> > > publish\_address {inet[/10.0.0.111:9200]
> > > 
> > > network.bind\_host: 127.0.0.1  
> > > network.publish\_host: 10.0.0.111  
> > > network.host: 10.0.0.111  
> > > Log=  
> > > DataStoreVM2] failed to reconnect to node [DataSto....  
> > > bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/  
> > > 10.0.0.111:9300]}  
> > > bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/  
> > > 10.0.0.111:9200]}
> > > 
> > > Network.bind\_host: 127.0.0.1  
> > > network.publish\_host: 52.74.94.198  
> > > network.host: 10.0.0.111  
> > > http.host: 52.74.94.198  
> > > Log =
> > > 
> > > - BindHttpException[Failed to bind to [9200]]  
> > > ChannelException[Failed to bind to: /52.74.94.198:9200]  
> > > BindException[Cannot assign requested address]
> > > 
> > > On Sunday, March 29, 2015 at 5:09:26 AM UTC+8, Mark Walkom wrote:
> > > 
> > > > Are you using multicast or unicast?
> > > > 
> > > > On 28 March 2015 at 21:21, Azman Ahmad [lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) wrote:
> > > > 
> > > > > Both nodes running on AWS. Both sides pingbles and curlable. Had check  
> > > > > resolution in this forum but the case is not similar at all. Badly need  
> > > > > help as project meeting dateline. Please....
> > > > > 
> > > > > yml setting.  
> > > > > network.publish\_host: 52.74.94.198  
> > > > > network.host: 10.0.0.111
> > > > > 
> > > > > etc/hosts  
> > > > > 127.0.0.1 localhost  
> > > > > 10.0.0.246 DataStoreVM1  
> > > > > 10.0.0.111 DataStoreVM2
> > > > > 
> > > > > [2015-03-27 13:12:21,239][WARN][cluster.service]  
> > > > > [DataStoreVM2] failed to connect to node [[DataStoreVM1][  
> > > > > X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:  
> > > > > 9300]]{master=false}]  
> > > > > org.elasticsearch.transport.ConnectTransportException:  
> > > > > [DataStoreVM1][inet[/52.74.93.147: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$  
> > > > > UpdateTask.run(InternalClusterService.java:411)  
> > > > > at org.elasticsearch.common.util.concurrent.  
> > > > > PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(  
> > > > > PrioritizedEsThreadPoolExecutor.java:153)  
> > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > > ThreadPoolExecutor.java:1145)  
> > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > ThreadPoolExecutor.java:615)  
> > > > > at java.lang.Thread.run(Thread.java:745)  
> > > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > > connection timed out: /52.74.93.147: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)  
> > > > > ... 3 more  
> > > > > [2015-03-27 13:12:51,037][WARN][cluster.service]  
> > > > > [DataStoreVM2] failed to reconnect to node [DataStoreVM2][dAjDjc-  
> > > > > 0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false,  
> > > > > master=false}  
> > > > > org.elasticsearch.transport.ConnectTransportException:  
> > > > > [DataStoreVM2][inet[/52.74.94.198: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:1145)  
> > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > ThreadPoolExecutor.java:615)  
> > > > > at java.lang.Thread.run(Thread.java:745)  
> > > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > > connection timed out: /52.74.94.198: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)
> > > > > 
> > > > > ubuntu@ip-10-0-0-111:~$ ifconfig  
> > > > > eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
> > > > > inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
> > > > > inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
> > > > > UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
> > > > > RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
> > > > > TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
> > > > > collisions:0 txqueuelen:1000  
> > > > > RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)
> > > > > 
> > > > > lo Link encap:Local Loopback  
> > > > > inet addr:127.0.0.1 Mask:255.0.0.0  
> > > > > inet6 addr: ::1/128 Scope:Host  
> > > > > UP LOOPBACK RUNNING MTU:65536 Metric:1  
> > > > > RX packets:2304 errors:0 dropped:0 overruns:0 frame:0  
> > > > > TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0  
> > > > > collisions:0 txqueuelen:0  
> > > > > RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)
> > > > > 
> > > > > --  
> > > > > 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/](https://groups.google.com/d/)  
> > > > > msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%  
> > > > > [40googlegroups.com](http://40googlegroups.com)  
> > > > > [https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > > To view this discussion on the web visit  
> > > > [https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com)  
> > > > [https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%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/0afaadfc-36c8-462c-abb6-67310543b4a6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0afaadfc-36c8-462c-abb6-67310543b4a6%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**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:** [March 29, 2015, 8:16pm UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/10 "2015-03-29T20:16:12Z")

</div>

If you are trying to talk from your DO instances on a public IP to your AWS  
instance on a private IP, it's not going to work.

You should really leverage snapshot and restore instead of doing this.

On 30 March 2015 at 02:06, Azman Ahmad [lesdesprado2012@gmail.com](mailto:lesdesprado2012@gmail.com) wrote:

> Additional info, the firewall ports 9200-9400 for public ip in aws  
> purposely is not open to communicate among VMs in aws due to security  
> reason.
> 
> On Sunday, March 29, 2015 at 10:33:30 PM UTC+8, Azman Ahmad wrote:
> 
> > Yes, the plan was to decommision all vms in digitalocean. Before doing  
> > so, all data will be re-populated during clustering into aws then retire  
> > vms in digitalocean one by one. In aws i hv private & public ip while in  
> > Digitalocean all public ip. Thanks.
> > 
> > On Sunday, March 29, 2015 at 3:48:05 PM UTC+8, Mark Walkom wrote:
> > 
> > > You're building a cluster between your AWS instances and your  
> > > DigitalOcean ones, am I understanding this correctly?
> > > 
> > > On 29 March 2015 at 11:56, Azman Ahmad [lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) wrote:
> > > 
> > > > unicast.
> > > > 
> > > > here  
> > > > discovery.zen.ping.multicast.enabled: false  
> > > > discovery.zen.ping.unicast.hosts : ["10.0.0.187:9300","x.x.x.x:9300","x.x.x.x:9300"]  
> > > > \*x.x.x.x = VMs in digitalocean  
> > > > #discovery.zen.ping.unicast.hosts : ["10.0.0.187"]  
> > > > discovery.zen.ping.timeout: 180s  
> > > > discovery.zen.minimum\_master\_nodes: 2
> > > > 
> > > > just to share the error that i got when i played with yml
> > > > 
> > > > network.bind\_host: 10.0.0.111  
> > > > network.publish\_host: 52.74.94.198  
> > > > network.host: 127.0.0.1
> > > > 
> > > > log :  
> > > > detected\_master [I love S & DataStoreVM2] [node1]failed to connect to  
> > > > node [node1][....  
> > > > [transport] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]},  
> > > > publish\_address {inet[/52.74.94.198:9300]}  
> > > > [http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]},  
> > > > publish\_address {inet[/127.0.0.1:9200]}  
> > > > ,,,,DataStoreVM2] failed to reconnect to node [DataSto....
> > > > 
> > > > Network.bind\_host: 127.0.0.1  
> > > > network.publish\_host: 52.74.94.198  
> > > > network.host: 10.0.0.111  
> > > > Log=  
> > > > failed to send join request to master [[I love Siti.... [transport] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9300]},  
> > > > publish\_address {inet[/52.74.94.198:9300]  
> > > > [http] [DataStoreVM2] bound\_address {inet[/127.0.0.1:9200]},  
> > > > publish\_address {inet[/10.0.0.111:9200]
> > > > 
> > > > network.bind\_host: 127.0.0.1  
> > > > network.publish\_host: 10.0.0.111  
> > > > network.host: 10.0.0.111  
> > > > Log=  
> > > > DataStoreVM2] failed to reconnect to node [DataSto....  
> > > > bound\_address {inet[/127.0.0.1:9300]}, publish\_address {inet[/  
> > > > 10.0.0.111:9300]}  
> > > > bound\_address {inet[/127.0.0.1:9200]}, publish\_address {inet[/  
> > > > 10.0.0.111:9200]}
> > > > 
> > > > Network.bind\_host: 127.0.0.1  
> > > > network.publish\_host: 52.74.94.198  
> > > > network.host: 10.0.0.111  
> > > > http.host: 52.74.94.198  
> > > > Log =
> > > > 
> > > > - BindHttpException[Failed to bind to [9200]]  
> > > > ChannelException[Failed to bind to: /52.74.94.198:9200]  
> > > > BindException[Cannot assign requested address]
> > > > 
> > > > On Sunday, March 29, 2015 at 5:09:26 AM UTC+8, Mark Walkom wrote:
> > > > 
> > > > > Are you using multicast or unicast?
> > > > > 
> > > > > On 28 March 2015 at 21:21, Azman Ahmad [lesdesp...@gmail.com](mailto:lesdesp...@gmail.com) wrote:
> > > > > 
> > > > > > Both nodes running on AWS. Both sides pingbles and curlable. Had  
> > > > > > check resolution in this forum but the case is not similar at all. Badly  
> > > > > > need help as project meeting dateline. Please....
> > > > > > 
> > > > > > yml setting.  
> > > > > > network.publish\_host: 52.74.94.198  
> > > > > > network.host: 10.0.0.111
> > > > > > 
> > > > > > etc/hosts  
> > > > > > 127.0.0.1 localhost  
> > > > > > 10.0.0.246 DataStoreVM1  
> > > > > > 10.0.0.111 DataStoreVM2
> > > > > > 
> > > > > > [2015-03-27 13:12:21,239][WARN][cluster.service]  
> > > > > > [DataStoreVM2] failed to connect to node [[DataStoreVM1][  
> > > > > > X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:  
> > > > > > 9300]]{master=false}]  
> > > > > > org.elasticsearch.transport.ConnectTransportException:  
> > > > > > [DataStoreVM1][inet[/52.74.93.147: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$  
> > > > > > UpdateTask.run(InternalClusterService.java:411)  
> > > > > > at org.elasticsearch.common.util.concurrent.  
> > > > > > PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(  
> > > > > > PrioritizedEsThreadPoolExecutor.java:153)  
> > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > > > ThreadPoolExecutor.java:1145)  
> > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > > ThreadPoolExecutor.java:615)  
> > > > > > at java.lang.Thread.run(Thread.java:745)  
> > > > > > Caused by: org.elasticsearch.common.netty.channel.  
> > > > > > ConnectTimeoutException: connection timed out: /52.74.93.147: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)  
> > > > > > ... 3 more  
> > > > > > [2015-03-27 13:12:51,037][WARN][cluster.service]  
> > > > > > [DataStoreVM2] failed to reconnect to node [DataStoreVM2][dAjDjc-  
> > > > > > 0SxGG5JdDundhzw][ip-10-0-0-111][inet[/52.74.94.198:9300]]{data=false,  
> > > > > > master=false}  
> > > > > > org.elasticsearch.transport.ConnectTransportException:  
> > > > > > [DataStoreVM2][inet[/52.74.94.198: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:1145)  
> > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > > ThreadPoolExecutor.java:615)  
> > > > > > at java.lang.Thread.run(Thread.java:745)  
> > > > > > Caused by: org.elasticsearch.common.netty.channel.  
> > > > > > ConnectTimeoutException: connection timed out: /52.74.94.198: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)
> > > > > > 
> > > > > > ubuntu@ip-10-0-0-111:~$ ifconfig  
> > > > > > eth0 Link encap:Ethernet HWaddr 02:db:17:9f:9a:b4  
> > > > > > inet addr:10.0.0.111 Bcast:10.0.0.255 Mask:255.255.255.0  
> > > > > > inet6 addr: fe80::db:17ff:fe9f:9ab4/64 Scope:Link  
> > > > > > UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1  
> > > > > > RX packets:161001 errors:0 dropped:0 overruns:0 frame:0  
> > > > > > TX packets:135696 errors:0 dropped:0 overruns:0 carrier:0  
> > > > > > collisions:0 txqueuelen:1000  
> > > > > > RX bytes:146146281 (146.1 MB) TX bytes:12125096 (12.1 MB)
> > > > > > 
> > > > > > lo Link encap:Local Loopback  
> > > > > > inet addr:127.0.0.1 Mask:255.0.0.0  
> > > > > > inet6 addr: ::1/128 Scope:Host  
> > > > > > UP LOOPBACK RUNNING MTU:65536 Metric:1  
> > > > > > RX packets:2304 errors:0 dropped:0 overruns:0 frame:0  
> > > > > > TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0  
> > > > > > collisions:0 txqueuelen:0  
> > > > > > RX bytes:171445 (171.4 KB) TX bytes:171445 (171.4 KB)
> > > > > > 
> > > > > > --  
> > > > > > 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/](https://groups.google.com/d/)  
> > > > > > msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40goo  
> > > > > > [glegroups.com](http://glegroups.com)  
> > > > > > [https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f13cef71-b3b5-4f17-893f-5edf5ddfd3fa%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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > > > msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%  
> > > > > [40googlegroups.com](http://40googlegroups.com)  
> > > > > [https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae080b66-5570-4aca-9fee-00cc86036afe%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/0afaadfc-36c8-462c-abb6-67310543b4a6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0afaadfc-36c8-462c-abb6-67310543b4a6%40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/0afaadfc-36c8-462c-abb6-67310543b4a6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/0afaadfc-36c8-462c-abb6-67310543b4a6%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\_2XLxze1cB4rB1piZ0Y68Z1TtfVxDJOzO\_C6UuONwfig%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_2XLxze1cB4rB1piZ0Y68Z1TtfVxDJOzO_C6UuONwfig%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![mohdjohari1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@mohdjohari1](https://discuss.elastic.co/u/mohdjohari1)\
**Post date:** [March 29, 2015, 10:56pm UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/11 "2015-03-29T22:56:02Z")

</div>

But then the public IP is mapped with private IP in AWS.

---

<div class="post-metadata">

**Author:** ![mohdjohari1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@mohdjohari1](https://discuss.elastic.co/u/mohdjohari1)\
**Post date:** [March 30, 2015, 3:42pm UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/12 "2015-03-30T15:42:11Z")

</div>

just want to prove something that AWS vm joined and detected the cluster in DO when yml setting in AWS is =  
transport.publish\_host: 52.74.94.198  
network.host: 10.0.0.111  
transport.host: 10.0.0.111

Log=  
] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9300]}, publish\_address {inet[/52.74.94.198:9300]}  
[2015-03-30 15:31:28,911][INFO][discovery] [DataStoreVM2] elasticsearch/Ng9ocvKNQQCQCkdlasQDMA  
[2015-03-30 15:31:58,911][WARN][discovery] [DataStoreVM2] waited for 30s and no initial state was set by the discovery  
[2015-03-30 15:31:58,915][INFO][http] [DataStoreVM2] bound\_address {inet[/10.0.0.111:9200]}, publish  
detected\_master [I love Siti][8MbKP42IT92rHL3FzWJMvQ][lalala.my][inet[/x.x.x.x:9300]]{master=true}, added {[RobotsVM2][RxvCPzIIQjKmNvmKPxiSgQ][ip-10-0-0-187][inet[/52.74.95.71:9300]]{data=false, master=true},[Kayden Kross][Xrv209wsRMOEVA8Z6YN0IA][vm7][inet[/x.x.x.:9300]]{data=false, master=true},[Alexis Texas][csBxrZEqSuCGzxeHYULaZw][earth3][inet[/x.x.x.x:9300]]{data=false, master=false},[Jenaveve Jolie][N4XxwzrZQN6Xw19XJfUZBg][vm10][inet[/x.x.x.x:9300]]{data=false, master=false},[Kagney Linn Carter][Ie76gloGR5WzLHc0NznxPg][vm1][inet[/128.199.123.33:9300]]{data=false, master=false},[Rebecca Linares][NGsxtQJJQMGx9XJ-NH25Nw][vm9][inet[/x.x.x.x:9300]]{data=false, master=false},[Jenna Jameson][w0Hu\_mT2QfK9uQvqWzwKqQ][vm8][inet[/x.x.x.x:9300]]{master=false},[Jenna Presley][kEg-SYHTRvWvyW-3iduaxA][vm6][inet[/x.x.x.x:9300]]{master=false},[DataStoreVM1][X6Teb0UpQ1uCV31tVRCQ6g][ip-10-0-0-246][inet[/52.74.93.147:9300]]{master=false},[I love Siti][8MbKP42IT92rHL3FzWJMvQ][lalala.my][inet[/x.x.x.x:9300]]{master=true},}, reason: zen-disco-receive(from master [[I love Siti][8MbKP42IT92rHL3FzWJMvQ][lalala.my][inet[/x.x.x.x:9300]]{master=true}])  
[2015-03-30 15:35:00,426][WARN][cluster.service] [DataStoreVM2] failed to connect to node [[RobotsVM2][RxvCPzIIQjKmNvmKPxiSgQ][ip-10-0-0-187][inet[/52.74.95.71:9300]]{data=false, master=true}]  
org.elasticsearch.transport.ConnectTransportException: [RobotsVM2][inet[/52.74.95.71: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$UpdateTask.run(InternalClusterService.java:411)  
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:745)  
Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /52.74.95.71: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)

---

<div class="post-metadata">

**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:23am UTC](https://discuss.elastic.co/t/node1-failed-to-reconnect-to-node-node1/22959/13 "2017-07-06T00:23:05Z")

</div>


