# Cant create cluster on ec2

**URL:** <https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434>\
**Category:** Elasticsearch\
**Created:** [January 27, 2014, 5:07pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434 "2014-01-27T17:07:43Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 27, 2014, 5:07pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/1 "2014-01-27T17:07:43Z")

</div>

Hi,

I have two nodes runnging on ec2.

curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
{  
"cluster\_name" : "12345elasticsearch",  
"status" : "green",  
"timed\_out" : false,  
"number\_of\_nodes" : 1,  
"number\_of\_data\_nodes" : 1,  
"active\_primary\_shards" : 0,  
"active\_shards" : 0,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0  
}

So..its fair to say that ec2 clustering did not work given the below  
config. Yes...the aws keys are correct and I have port 9200-9400 open.  
What elasticsearch advertiseres is that all that is needed.

I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu 12.04

cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
discovery.type: ec2

In the logs I see the below:

[2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
[Administrator] [1] failed to connect to  
[#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300]]  
org.elasticsearch.transport.ConnectTransportException:  
[][inet[/10.211.29.210:9300]] connect\_timeout[30s]  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
at  
org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
at  
org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:701)  
Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
connection timed out: /10.239.36.98:9300  
at  
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
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

Thanks

--  
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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 27, 2014, 5:46pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/2 "2014-01-27T17:46:20Z")

</div>

Hi David,

I think you should have nodes running under the same security group. In that case, you don't have to open 9300-9400 ports to public.  
If they don't belong to the same group or if you want to reach them from outside ec2 platform (public IP), then you need to set host\_type to public\_ip.

It sounds like your nodes are trying to connect with private ip here (which is default).

My 2 cents

--  
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
@dadoonet | @elasticsearchfr

Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)) a écrit:

Hi,

I have two nodes runnging on ec2.

curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
{  
"cluster\_name" : "12345elasticsearch",  
"status" : "green",  
"timed\_out" : false,  
"number\_of\_nodes" : 1,  
"number\_of\_data\_nodes" : 1,  
"active\_primary\_shards" : 0,  
"active\_shards" : 0,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0  
}

So..its fair to say that ec2 clustering did not work given the below config. Yes...the aws keys are correct and I have port 9200-9400 open. What elasticsearch advertiseres is that all that is needed.

I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu 12.04

cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
discovery.type: ec2

In the logs I see the below:

[2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast] [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300]]  
org.elasticsearch.transport.ConnectTransportException: [][inet[/10.211.29.210:9300]] connect\_timeout[30s]  
at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:701)  
Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.239.36.98:9300  
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
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

Thanks

--  
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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/etPan.52e69b6c.2901d82.b15f%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.52e69b6c.2901d82.b15f%40MacBook-Air-de-David.local).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 27, 2014, 5:52pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/3 "2014-01-27T17:52:05Z")

</div>

Hi,

I have the same sec group. Just staying that not having ports open is not  
an issue. ES is running on both nodes. Both nodes cant talk. Those fro  
ES..anyu suggestions? Do those from ES follow this group?

thanks

On Tue, Jan 28, 2014 at 1:46 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:

> Hi David,
> 
> I think you should have nodes running under the same security group. In  
> that case, you don't have to open 9300-9400 ports to public.  
> If they don't belong to the same group or if you want to reach them from  
> outside ec2 platform (public IP), then you need to set host\_type to  
> public\_ip.
> 
> It sounds like your nodes are trying to connect with private ip here  
> (which is default).
> 
> My 2 cents
> 
> --  
> _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_  
> @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> 
> Le 27 janvier 2014 at 18:07:48, David Montgomery (  
> [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)) a écrit:
> 
> Hi,
> 
> I have two nodes runnging on ec2.
> 
> curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> {  
> "cluster\_name" : "12345elasticsearch",  
> "status" : "green",  
> "timed\_out" : false,  
> "number\_of\_nodes" : 1,  
> "number\_of\_data\_nodes" : 1,  
> "active\_primary\_shards" : 0,  
> "active\_shards" : 0,  
> "relocating\_shards" : 0,  
> "initializing\_shards" : 0,  
> "unassigned\_shards" : 0  
> }
> 
> So..its fair to say that ec2 clustering did not work given the below  
> config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> What elasticsearch advertiseres is that all that is needed.
> 
> I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu  
> 12.04
> 
> cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> discovery.type: ec2
> 
> In the logs I see the below:
> 
> [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> [Administrator] [1] failed to connect to  
> [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/  
> 10.211.29.210:9300]]  
> org.elasticsearch.transport.ConnectTransportException: [inet[/  
> 10.211.29.210:9300]] connect\_timeout[30s]  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
> at  
> org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
> at  
> org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
> at  
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
> at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(Thread.java:701)  
> Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> connection timed out: /10.239.36.98:9300  
> at  
> org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> 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
> 
> Thanks
> 
> --  
> 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACF%2B8rqw5\_jPrdenE9crYHGZX-7QEtWDKnWhv0M6ch3durjO%2BQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rqw5_jPrdenE9crYHGZX-7QEtWDKnWhv0M6ch3durjO%2BQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 27, 2014, 7:44pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/4 "2014-01-27T19:44:45Z")

</div>

Could you change to TRACE level discovery package?

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 18:52, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) a écrit :

Hi,

I have the same sec group. Just staying that not having ports open is not an issue. ES is running on both nodes. Both nodes cant talk. Those fro ES..anyu suggestions? Do those from ES follow this group?

thanks

> On Tue, Jan 28, 2014 at 1:46 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:  
> Hi David,
> 
> I think you should have nodes running under the same security group. In that case, you don't have to open 9300-9400 ports to public.  
> If they don't belong to the same group or if you want to reach them from outside ec2 platform (public IP), then you need to set host\_type to public\_ip.
> 
> It sounds like your nodes are trying to connect with private ip here (which is default).
> 
> My 2 cents
> 
> --  
> David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
> @dadoonet | @elasticsearchfr
> 
> Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)) a écrit:
> 
> > Hi,
> > 
> > I have two nodes runnging on ec2.
> > 
> > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > {  
> > "cluster\_name" : "12345elasticsearch",  
> > "status" : "green",  
> > "timed\_out" : false,  
> > "number\_of\_nodes" : 1,  
> > "number\_of\_data\_nodes" : 1,  
> > "active\_primary\_shards" : 0,  
> > "active\_shards" : 0,  
> > "relocating\_shards" : 0,  
> > "initializing\_shards" : 0,  
> > "unassigned\_shards" : 0  
> > }
> > 
> > So..its fair to say that ec2 clustering did not work given the below config. Yes...the aws keys are correct and I have port 9200-9400 open. What elasticsearch advertiseres is that all that is needed.
> > 
> > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu 12.04
> > 
> > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > discovery.type: ec2
> > 
> > In the logs I see the below:
> > 
> > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast] [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300]]  
> > org.elasticsearch.transport.ConnectTransportException: [inet[/10.211.29.210:9300]] connect\_timeout[30s]  
> > at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
> > at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
> > at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
> > at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
> > at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > at java.lang.Thread.run(Thread.java:701)  
> > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.239.36.98:9300  
> > at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > 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
> > 
> > Thanks
> > 
> > --  
> > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACF%2B8rqw5\_jPrdenE9crYHGZX-7QEtWDKnWhv0M6ch3durjO%2BQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rqw5_jPrdenE9crYHGZX-7QEtWDKnWhv0M6ch3durjO%2BQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/0FAF15FD-9CCC-40F1-B2E5-26C1CB401EEA%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/0FAF15FD-9CCC-40F1-B2E5-26C1CB401EEA%40pilato.fr).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 27, 2014, 7:47pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/5 "2014-01-27T19:47:10Z")

</div>

Hi,

As an fyi..I can telnet into the other machine. Its only ES that does not  
work despite following the online docs.

If ES aws auto discovery does not work l assuming assume that

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

will work?

Thanks

On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:

> Hi David,
> 
> I think you should have nodes running under the same security group. In  
> that case, you don't have to open 9300-9400 ports to public.  
> If they don't belong to the same group or if you want to reach them from  
> outside ec2 platform (public IP), then you need to set host\_type to  
> public\_ip.
> 
> It sounds like your nodes are trying to connect with private ip here  
> (which is default).
> 
> My 2 cents
> 
> --  
> _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_  
> @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> 
> Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmo...@gmail.com](mailto:davidmo...@gmail.com)\<javascript:\>)  
> a écrit:
> 
> Hi,
> 
> I have two nodes runnging on ec2.
> 
> curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> {  
> "cluster\_name" : "12345elasticsearch",  
> "status" : "green",  
> "timed\_out" : false,  
> "number\_of\_nodes" : 1,  
> "number\_of\_data\_nodes" : 1,  
> "active\_primary\_shards" : 0,  
> "active\_shards" : 0,  
> "relocating\_shards" : 0,  
> "initializing\_shards" : 0,  
> "unassigned\_shards" : 0  
> }
> 
> So..its fair to say that ec2 clustering did not work given the below  
> config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> What elasticsearch advertiseres is that all that is needed.
> 
> I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu  
> 12.04
> 
> cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> discovery.type: ec2
> 
> In the logs I see the below:
> 
> [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> [Administrator] [1] failed to connect to  
> [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/  
> 10.211.29.210:9300]]  
> org.elasticsearch.transport.ConnectTransportException: [inet[/  
> 10.211.29.210:9300]] connect\_timeout[30s]  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
> at  
> org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
> at  
> org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
> at  
> org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
> at  
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
> at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(Thread.java:701)  
> Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> connection timed out: /10.239.36.98:9300  
> at  
> org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> 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
> 
> Thanks
> 
> --  
> 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/ea43ded6-cb4a-45d4-b120-980718476983%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ea43ded6-cb4a-45d4-b120-980718476983%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 27, 2014, 7:53pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/6 "2014-01-27T19:53:50Z")

</div>

I assume that means this in the logging.yml fike?

# discovery

discovery: TRACE

I do have it on...what should I be looking for in the logs?

On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:

> Hi,
> 
> As an fyi..I can telnet into the other machine. Its only ES that does not  
> work despite following the online docs.
> 
> If ES aws auto discovery does not work l assuming assume that  
> [Elastic — The Search AI Company | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.htmlwill) work?
> 
> Thanks
> 
> On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> 
> > Hi David,
> > 
> > I think you should have nodes running under the same security group. In  
> > that case, you don't have to open 9300-9400 ports to public.  
> > If they don't belong to the same group or if you want to reach them from  
> > outside ec2 platform (public IP), then you need to set host\_type to  
> > public\_ip.
> > 
> > It sounds like your nodes are trying to connect with private ip here  
> > (which is default).
> > 
> > My 2 cents
> > 
> > --  
> > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_  
> > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > 
> > Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmo...@gmail.com](mailto:davidmo...@gmail.com))  
> > a écrit:
> > 
> > Hi,
> > 
> > I have two nodes runnging on ec2.
> > 
> > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > {  
> > "cluster\_name" : "12345elasticsearch",  
> > "status" : "green",  
> > "timed\_out" : false,  
> > "number\_of\_nodes" : 1,  
> > "number\_of\_data\_nodes" : 1,  
> > "active\_primary\_shards" : 0,  
> > "active\_shards" : 0,  
> > "relocating\_shards" : 0,  
> > "initializing\_shards" : 0,  
> > "unassigned\_shards" : 0  
> > }
> > 
> > So..its fair to say that ec2 clustering did not work given the below  
> > config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> > What elasticsearch advertiseres is that all that is needed.
> > 
> > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu  
> > 12.04
> > 
> > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > discovery.type: ec2
> > 
> > In the logs I see the below:
> > 
> > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > [Administrator] [1] failed to connect to  
> > [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/  
> > 10.211.29.210:9300]]  
> > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > 10.211.29.210:9300]] connect\_timeout[30s]  
> > at  
> > org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
> > at  
> > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
> > at  
> > org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
> > at  
> > org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
> > at  
> > org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > at  
> > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
> > at  
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > at java.lang.Thread.run(Thread.java:701)  
> > Caused by:  
> > org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection  
> > timed out: /10.239.36.98:9300  
> > at  
> > org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > 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
> > 
> > Thanks
> > 
> > --  
> > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com)  
> > .  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 27, 2014, 7:57pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/7 "2014-01-27T19:57:34Z")

</div>

If this is what you mean my trace in the logs....

```
    at 

```

org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
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  
[2014-01-27 16:58:49,706][TRACE][discovery.zen.ping.unicast]  
[Administrator] [1] failed to connect to  
[#cloud-i-ef763797-0][aws-elasticsearch-east-development-20140127160434][inet[/10.198.91.74:9300]]  
org.elasticsearch.transport.ConnectTransportException:  
[inet[/10.198.91.74:9300]] connect\_timeout[30s]  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
at  
org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
at  
org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:701)  
Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
connection timed out: /10.239.36.98:9300  
at  
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
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  
[2014-01-27 16:58:49,707][TRACE][discovery.zen.ping.unicast]  
[Administrator] [1] failed to connect to  
[#cloud-i-0598a260-0][aws-elasticsearch-east-development-20140127160434][inet[/10.244.178.236:9300]]  
org.elasticsearch.transport.ConnectTransportException:  
[inet[/10.244.178.236:9300]] connect\_timeout[30s]  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
at  
org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
at  
org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:701)  
Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
connection timed out: /10.239.36.98:9300  
at  
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
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  
[2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
[Administrator] [1] failed to connect to  
[#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300]]  
org.elasticsearch.transport.ConnectTransportException:  
[inet[/10.211.29.210:9300]] connect\_timeout[30s]  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
at  
org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
at  
org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:701)  
Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
connection timed out: /10.239.36.98:9300  
[2014-01-27 17:38:09,856][DEBUG][discovery.zen.ping.unicast] [Lupa] using  
initial hosts , with concurrent\_connects [10]  
[2014-01-27 17:38:09,949][DEBUG][discovery.ec2] [Lupa] using  
ping.timeout [3s], master\_election.filter\_client [true],  
master\_election.filter\_data [false]  
[2014-01-27 17:38:09,950][DEBUG][discovery.zen.elect] [Lupa] using  
minimum\_master\_nodes [-1]  
[2014-01-27 17:38:09,951][DEBUG][discovery.zen.fd] [Lupa] [master]  
uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3]  
[2014-01-27 17:38:09,963][DEBUG][discovery.zen.fd] [Lupa] [node]  
uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3]  
[2014-01-27 17:38:11,361][DEBUG][discovery.ec2] [Lupa] using  
host\_type [PRIVATE\_IP], tags [{}], groups [] with any\_group [true],  
availability\_zones []  
[2014-01-27 17:38:14,205][WARN][gateway.s3] [Lupa] shared  
gateway has been deprecated, please use the (default) local gateway  
[2014-01-27 17:38:14,207][WARN][gateway.s3] [Lupa] shared  
gateway has been deprecated, please use the (default) local gateway  
[2014-01-27 17:39:48,081][INFO][node] [Hurricane]  
version[1.0.0.RC1], pid[21245], build[c6155c5/2014-01-15T17:02:32Z]  
[2014-01-27 17:39:48,081][INFO][node] [Hurricane]  
initializing ...  
[2014-01-27 17:39:48,107][INFO][plugins] [Hurricane]  
loaded [cloud-aws], sites   
[2014-01-27 17:39:52,291][DEBUG][discovery.zen.ping.multicast] [Hurricane]  
using group [224.2.2.4], with port [54328], ttl [3], and address [null]  
[2014-01-27 17:39:52,295][DEBUG][discovery.zen.ping.unicast] [Hurricane]  
using initial hosts , with concurrent\_connects [10]  
[2014-01-27 17:39:52,296][DEBUG][discovery.zen] [Hurricane]  
using ping.timeout [3s], master\_election.filter\_client [true],  
master\_election.filter\_data [false]  
[2014-01-27 17:39:52,297][DEBUG][discovery.zen.elect] [Hurricane]  
using minimum\_master\_nodes [-1]  
[2014-01-27 17:39:52,298][DEBUG][discovery.zen.fd] [Hurricane]  
[master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3]  
[2014-01-27 17:39:52,307][DEBUG][discovery.zen.fd] [Hurricane]  
[node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3]  
[2014-01-27 17:39:54,818][INFO][node] [Hurricane]  
initialized  
[2014-01-27 17:39:54,819][INFO][node] [Hurricane]  
starting ...  
[2014-01-27 17:39:55,248][INFO][transport] [Hurricane]  
bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address  
{inet[/10.208.51.152:9300]}  
[2014-01-27 17:39:55,259][TRACE][discovery] [Hurricane]  
waiting for 30s for the initial state to be set by the discovery  
[2014-01-27 17:39:55,270][TRACE][discovery.zen.ping.multicast] [Hurricane]  
[1] sending ping request  
[2014-01-27 17:39:56,771][TRACE][discovery.zen.ping.multicast] [Hurricane]  
[1] sending ping request  
[2014-01-27 17:39:58,273][TRACE][discovery.zen] [Hurricane]  
full ping responses: {none}  
[2014-01-27 17:39:58,273][DEBUG][discovery.zen] [Hurricane]  
filtered ping responses: (filter\_client[true], filter\_data[false]) {none}  
[2014-01-27 17:39:58,278][INFO][cluster.service] [Hurricane]  
new\_master  
[Hurricane][hFUsfnukS\_GLOxCZwJsVXA][aws-elasticsearch-east-development-20140127160434][inet[/10.208.51.152:9300]],  
reason: zen-d$  
[2014-01-27 17:39:58,308][TRACE][discovery] [Hurricane]  
initial state set from discovery  
[2014-01-27 17:39:58,308][INFO][discovery] [Hurricane]  
mizilaelasticsearch/hFUsfnukS\_GLOxCZwJsVXA  
[2014-01-27 17:39:58,424][INFO][http] [Hurricane]  
bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address  
{inet[/10.208.51.152:9200]}  
[2014-01-27 17:39:58,444][INFO][gateway] [Hurricane]  
recovered [0] indices into cluster\_state  
[2014-01-27 17:39:58,444][INFO][node] [Hurricane]  
started  
[2014-01-27 19:54:52,667][INFO][node] [Hurricane]  
stopping ...  
[2014-01-27 19:54:52,774][INFO][node] [Hurricane]  
stopped  
[2014-01-27 19:54:52,774][INFO][node] [Hurricane]  
closing ...  
[2014-01-27 19:54:52,781][INFO][node] [Hurricane]  
closed  
[2014-01-27 19:54:56,193][INFO][node] [Cerise]  
version[1.0.0.RC1], pid[21694], build[c6155c5/2014-01-15T17:02:32Z]  
[2014-01-27 19:54:56,193][INFO][node] [Cerise]  
initializing ...  
[2014-01-27 19:54:56,208][INFO][plugins] [Cerise] loaded  
[cloud-aws], sites   
[2014-01-27 19:55:01,703][DEBUG][discovery.zen.ping.multicast] [Cerise]  
using group [224.2.2.4], with port [54328], ttl [3], and address [null]  
[2014-01-27 19:55:01,738][DEBUG][discovery.zen.ping.unicast] [Cerise] using  
initial hosts , with concurrent\_connects [10]  
[2014-01-27 19:55:01,739][DEBUG][discovery.zen] [Cerise] using  
ping.timeout [3s], master\_election.filter\_client [true],  
master\_election.filter\_data [false]  
[2014-01-27 19:55:01,740][DEBUG][discovery.zen.elect] [Cerise] using  
minimum\_master\_nodes [-1]  
[2014-01-27 19:55:01,741][DEBUG][discovery.zen.fd] [Cerise]  
[master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3]  
[2014-01-27 19:55:01,752][DEBUG][discovery.zen.fd] [Cerise] [node  
] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3]  
[2014-01-27 19:55:04,736][INFO][node] [Cerise]  
initialized  
[2014-01-27 19:55:04,736][INFO][node] [Cerise]  
starting ...  
[2014-01-27 19:55:04,981][INFO][transport] [Cerise]  
bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address  
{inet[/10.208.51.152:9300]}  
[2014-01-27 19:55:05,003][TRACE][discovery] [Cerise]  
waiting for 30s for the initial state to be set by the discovery  
[2014-01-27 19:55:05,105][TRACE][discovery.zen.ping.multicast] [Cerise] [1]  
sending ping request  
[2014-01-27 19:55:06,608][TRACE][discovery.zen.ping.multicast] [Cerise] [1]  
sending ping request  
[2014-01-27 19:55:08,256][TRACE][discovery.zen] [Cerise] full  
ping responses: {none}  
[2014-01-27 19:55:08,257][DEBUG][discovery.zen] [Cerise]  
filtered ping responses: (filter\_client[true], filter\_data[false]) {none}  
[2014-01-27 19:55:08,262][INFO][cluster.service] [Cerise]  
new\_master  
[Cerise][TOid02a4RMqcyHzEpJEuPg][aws-elasticsearch-east-development-20140127160434][inet[/10.208.51.152:9300]],  
reason: zen-disco-j$  
[2014-01-27 19:55:08,297][TRACE][discovery] [Cerise]  
initial state set from discovery

On Tuesday, January 28, 2014 3:53:50 AM UTC+8, David Montgomery wrote:

> I assume that means this in the logging.yml fike?
> 
> # discovery
> 
> discovery: TRACE
> 
> I do have it on...what should I be looking for in the logs?
> 
> On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:
> 
> > Hi,
> > 
> > As an fyi..I can telnet into the other machine. Its only ES that does  
> > not work despite following the online docs.
> > 
> > If ES aws auto discovery does not work l assuming assume that  
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.htmlwill) work?
> > 
> > Thanks
> > 
> > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > 
> > > Hi David,
> > > 
> > > I think you should have nodes running under the same security group. In  
> > > that case, you don't have to open 9300-9400 ports to public.  
> > > If they don't belong to the same group or if you want to reach them from  
> > > outside ec2 platform (public IP), then you need to set host\_type to  
> > > public\_ip.
> > > 
> > > It sounds like your nodes are trying to connect with private ip here  
> > > (which is default).
> > > 
> > > My 2 cents
> > > 
> > > --  
> > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_  
> > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > 
> > > Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmo...@gmail.com](mailto:davidmo...@gmail.com))  
> > > a écrit:
> > > 
> > > Hi,
> > > 
> > > I have two nodes runnging on ec2.
> > > 
> > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > {  
> > > "cluster\_name" : "12345elasticsearch",  
> > > "status" : "green",  
> > > "timed\_out" : false,  
> > > "number\_of\_nodes" : 1,  
> > > "number\_of\_data\_nodes" : 1,  
> > > "active\_primary\_shards" : 0,  
> > > "active\_shards" : 0,  
> > > "relocating\_shards" : 0,  
> > > "initializing\_shards" : 0,  
> > > "unassigned\_shards" : 0  
> > > }
> > > 
> > > So..its fair to say that ec2 clustering did not work given the below  
> > > config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> > > What elasticsearch advertiseres is that all that is needed.
> > > 
> > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu  
> > > 12.04
> > > 
> > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > discovery.type: ec2
> > > 
> > > In the logs I see the below:
> > > 
> > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > [Administrator] [1] failed to connect to  
> > > [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/  
> > > 10.211.29.210:9300]]  
> > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > at  
> > > org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
> > > at  
> > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
> > > at  
> > > org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
> > > at  
> > > org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
> > > at  
> > > org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:701)  
> > > Caused by:  
> > > org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection  
> > > timed out: /10.239.36.98:9300  
> > > at  
> > > org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > 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
> > > 
> > > Thanks
> > > 
> > > --  
> > > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com)  
> > > .  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/1d2ec8d6-ac20-4961-961e-181c2562cd60%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1d2ec8d6-ac20-4961-961e-181c2562cd60%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 27, 2014, 8:19pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/8 "2014-01-27T20:19:25Z")

</div>

Yes. Could you gist it (and remove first keys / secrets of course)?

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) a écrit :

I assume that means this in the logging.yml fike?

# discovery

discovery: TRACE

I do have it on...what should I be looking for in the logs?

> On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:  
> Hi,
> 
> As an fyi..I can telnet into the other machine. Its only ES that does not work despite following the online docs.
> 
> If ES aws auto discovery does not work l assuming assume that [Elastic — The Search AI Company | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html) will work?
> 
> Thanks
> 
> > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:  
> > Hi David,
> > 
> > I think you should have nodes running under the same security group. In that case, you don't have to open 9300-9400 ports to public.  
> > If they don't belong to the same group or if you want to reach them from outside ec2 platform (public IP), then you need to set host\_type to public\_ip.
> > 
> > It sounds like your nodes are trying to connect with private ip here (which is default).
> > 
> > My 2 cents
> > 
> > --  
> > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
> > @dadoonet | @elasticsearchfr
> > 
> > Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmo...@gmail.com](mailto:davidmo...@gmail.com)) a écrit:
> > 
> > > Hi,
> > > 
> > > I have two nodes runnging on ec2.
> > > 
> > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > {  
> > > "cluster\_name" : "12345elasticsearch",  
> > > "status" : "green",  
> > > "timed\_out" : false,  
> > > "number\_of\_nodes" : 1,  
> > > "number\_of\_data\_nodes" : 1,  
> > > "active\_primary\_shards" : 0,  
> > > "active\_shards" : 0,  
> > > "relocating\_shards" : 0,  
> > > "initializing\_shards" : 0,  
> > > "unassigned\_shards" : 0  
> > > }
> > > 
> > > So..its fair to say that ec2 clustering did not work given the below config. Yes...the aws keys are correct and I have port 9200-9400 open. What elasticsearch advertiseres is that all that is needed.
> > > 
> > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu 12.04
> > > 
> > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > discovery.type: ec2
> > > 
> > > In the logs I see the below:
> > > 
> > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast] [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300]]  
> > > org.elasticsearch.transport.ConnectTransportException: [inet[/10.211.29.210:9300]] connect\_timeout[30s]  
> > > at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
> > > at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
> > > at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
> > > at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
> > > at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
> > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:701)  
> > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.239.36.98:9300  
> > > at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > 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
> > > 
> > > Thanks
> > > 
> > > --  
> > > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/54FB49BA-850A-4A7F-92E3-EAF51F27A3E6%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/54FB49BA-850A-4A7F-92E3-EAF51F27A3E6%40pilato.fr).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 27, 2014, 9:57pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/9 "2014-01-27T21:57:35Z")

</div>

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again given  
that the two machine can talk to each other via telent, in the same region,  
same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto  
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com:9200](http://1.test.com:9200)"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

> Yes. Could you gist it (and remove first keys / secrets of course)?
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 27 janv. 2014 à 20:53, David Montgomery \<[davidmo...@gmail.com](mailto:davidmo...@gmail.com)\<javascript:\>\>  
> a écrit :
> 
> I assume that means this in the logging.yml fike?
> 
> # discovery
> 
> discovery: TRACE
> 
> I do have it on...what should I be looking for in the logs?
> 
> On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:
> 
> > Hi,
> > 
> > As an fyi..I can telnet into the other machine. Its only ES that does  
> > not work despite following the online docs.
> > 
> > If ES aws auto discovery does not work l assuming assume that  
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.htmlwill) work?
> > 
> > Thanks
> > 
> > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > 
> > > Hi David,
> > > 
> > > I think you should have nodes running under the same security group. In  
> > > that case, you don't have to open 9300-9400 ports to public.  
> > > If they don't belong to the same group or if you want to reach them from  
> > > outside ec2 platform (public IP), then you need to set host\_type to  
> > > public\_ip.
> > > 
> > > It sounds like your nodes are trying to connect with private ip here  
> > > (which is default).
> > > 
> > > My 2 cents
> > > 
> > > --  
> > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> > > [http://Elasticsearch.com](http://Elasticsearch.com)_  
> > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > 
> > > Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmo...@gmail.com](mailto:davidmo...@gmail.com))  
> > > a écrit:
> > > 
> > > Hi,
> > > 
> > > I have two nodes runnging on ec2.
> > > 
> > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > {  
> > > "cluster\_name" : "12345elasticsearch",  
> > > "status" : "green",  
> > > "timed\_out" : false,  
> > > "number\_of\_nodes" : 1,  
> > > "number\_of\_data\_nodes" : 1,  
> > > "active\_primary\_shards" : 0,  
> > > "active\_shards" : 0,  
> > > "relocating\_shards" : 0,  
> > > "initializing\_shards" : 0,  
> > > "unassigned\_shards" : 0  
> > > }
> > > 
> > > So..its fair to say that ec2 clustering did not work given the below  
> > > config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> > > What elasticsearch advertiseres is that all that is needed.
> > > 
> > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu  
> > > 12.04
> > > 
> > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > discovery.type: ec2
> > > 
> > > In the logs I see the below:
> > > 
> > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > [Administrator] [1] failed to connect to  
> > > [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/  
> > > 10.211.29.210:9300]]  
> > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > at  
> > > org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
> > > at  
> > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
> > > at  
> > > org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
> > > at  
> > > org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
> > > at  
> > > org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(Thread.java:701)  
> > > Caused by:  
> > > org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection  
> > > timed out: /10.239.36.98:9300  
> > > at  
> > > org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > 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
> > > 
> > > Thanks
> > > 
> > > --  
> > > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com)  
> > > .  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > 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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com)  
> > > .  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 27, 2014, 10:25pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/10 "2014-01-27T22:25:50Z")

</div>

Is it a known problem? Not yet. That's the reason I'm asking for logs. I would like to understand what is happening here. So full logs on both nodes would help.

The way you set unicast is fine to me. But please, could you share with me (even through Direct mail) your elasticsearch.yml file and your logs in TRACE level?  
You can replace your credentials settings with XXXXXXXX. Please don't change anything else. I'd like to reproduce your case.

Thanks!

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) a écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again given that the two machine can talk to each other via telent, in the same region, same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com:9200](http://1.test.com:9200)"]

Thanks

> On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:  
> Yes. Could you gist it (and remove first keys / secrets of course)?
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 27 janv. 2014 à 20:53, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a écrit :
> 
> I assume that means this in the logging.yml fike?
> 
> # discovery
> 
> discovery: TRACE
> 
> I do have it on...what should I be looking for in the logs?
> 
> > On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:  
> > Hi,
> > 
> > As an fyi..I can telnet into the other machine. Its only ES that does not work despite following the online docs.
> > 
> > If ES aws auto discovery does not work l assuming assume that [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html) will work?
> > 
> > Thanks
> > 
> > > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:  
> > > Hi David,
> > > 
> > > I think you should have nodes running under the same security group. In that case, you don't have to open 9300-9400 ports to public.  
> > > If they don't belong to the same group or if you want to reach them from outside ec2 platform (public IP), then you need to set host\_type to public\_ip.
> > > 
> > > It sounds like your nodes are trying to connect with private ip here (which is default).
> > > 
> > > My 2 cents
> > > 
> > > --  
> > > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
> > > @dadoonet | @elasticsearchfr
> > > 
> > > Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmo...@gmail.com](mailto:davidmo...@gmail.com)) a écrit:
> > > 
> > > > Hi,
> > > > 
> > > > I have two nodes runnging on ec2.
> > > > 
> > > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > > {  
> > > > "cluster\_name" : "12345elasticsearch",  
> > > > "status" : "green",  
> > > > "timed\_out" : false,  
> > > > "number\_of\_nodes" : 1,  
> > > > "number\_of\_data\_nodes" : 1,  
> > > > "active\_primary\_shards" : 0,  
> > > > "active\_shards" : 0,  
> > > > "relocating\_shards" : 0,  
> > > > "initializing\_shards" : 0,  
> > > > "unassigned\_shards" : 0  
> > > > }
> > > > 
> > > > So..its fair to say that ec2 clustering did not work given the below config. Yes...the aws keys are correct and I have port 9200-9400 open. What elasticsearch advertiseres is that all that is needed.
> > > > 
> > > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu 12.04
> > > > 
> > > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > > discovery.type: ec2
> > > > 
> > > > In the logs I see the below:
> > > > 
> > > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast] [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300]]  
> > > > org.elasticsearch.transport.ConnectTransportException: [inet[/10.211.29.210:9300]] connect\_timeout[30s]  
> > > > at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676)  
> > > > at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636)  
> > > > at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603)  
> > > > at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)  
> > > > at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)  
> > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > > > at java.lang.Thread.run(Thread.java:701)  
> > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.239.36.98:9300  
> > > > at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > > 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
> > > > 
> > > > Thanks
> > > > 
> > > > --  
> > > > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com).  
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> 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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 27, 2014, 10:40pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/11 "2014-01-27T22:40:10Z")

</div>

sure..let me the logs together and will post two files ..one log file for  
each of the servers.

Thanks

On Tue, Jan 28, 2014 at 6:25 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:

> Is it a known problem? Not yet. That's the reason I'm asking for logs. I  
> would like to understand what is happening here. So full logs on both nodes  
> would help.
> 
> The way you set unicast is fine to me. But please, could you share with me  
> (even through Direct mail) your elasticsearch.yml file and your logs in  
> TRACE level?  
> You can replace your credentials settings with XXXXXXXX. Please don't  
> change anything else. I'd like to reproduce your case.
> 
> Thanks!
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 27 janv. 2014 à 22:57, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) a  
> écrit :
> 
> I have to say..it this a know problem?
> 
> I removed the keys.
> 
> So.. should the servers still cluster? Well....its not.........again  
> given that the two machine can talk to each other via telent, in the same  
> region, same sec group restarted services etc....no go......no cluster
> 
> So....how do I manually configure nodes? I have given up on auto  
> discover. Clearly does now work for me.
> 
> Is the below an example?
> 
> discovery.zen.ping.multicast.enabled: false  
> discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com:9200](http://1.test.com:9200)"]
> 
> Thanks
> 
> On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:
> 
> > Yes. Could you gist it (and remove first keys / secrets of course)?
> > 
> > --  
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 27 janv. 2014 à 20:53, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a  
> > écrit :
> > 
> > I assume that means this in the logging.yml fike?
> > 
> > # discovery
> > 
> > discovery: TRACE
> > 
> > I do have it on...what should I be looking for in the logs?
> > 
> > On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:
> > 
> > > Hi,
> > > 
> > > As an fyi..I can telnet into the other machine. Its only ES that does  
> > > not work despite following the online docs.
> > > 
> > > If ES aws auto discovery does not work l assuming assume that  
> > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/)  
> > > reference/current/modules-discovery-zen.html will work?
> > > 
> > > Thanks
> > > 
> > > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > > 
> > > > Hi David,
> > > > 
> > > > I think you should have nodes running under the same security group. In  
> > > > that case, you don't have to open 9300-9400 ports to public.  
> > > > If they don't belong to the same group or if you want to reach them  
> > > > from outside ec2 platform (public IP), then you need to set host\_type  
> > > > to public\_ip.
> > > > 
> > > > It sounds like your nodes are trying to connect with private ip here  
> > > > (which is default).
> > > > 
> > > > My 2 cents
> > > > 
> > > > --  
> > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> > > > [http://Elasticsearch.com](http://Elasticsearch.com)_  
> > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > > 
> > > > Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmo...@gmail.com](mailto:davidmo...@gmail.com))  
> > > > a écrit:
> > > > 
> > > > Hi,
> > > > 
> > > > I have two nodes runnging on ec2.
> > > > 
> > > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > > {  
> > > > "cluster\_name" : "12345elasticsearch",  
> > > > "status" : "green",  
> > > > "timed\_out" : false,  
> > > > "number\_of\_nodes" : 1,  
> > > > "number\_of\_data\_nodes" : 1,  
> > > > "active\_primary\_shards" : 0,  
> > > > "active\_shards" : 0,  
> > > > "relocating\_shards" : 0,  
> > > > "initializing\_shards" : 0,  
> > > > "unassigned\_shards" : 0  
> > > > }
> > > > 
> > > > So..its fair to say that ec2 clustering did not work given the below  
> > > > config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> > > > What elasticsearch advertiseres is that all that is needed.
> > > > 
> > > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu  
> > > > 12.04
> > > > 
> > > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > > discovery.type: ec2
> > > > 
> > > > In the logs I see the below:
> > > > 
> > > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > > [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-  
> > > > elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300  
> > > > ]]  
> > > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > connectToChannelsLight(NettyTransport.java:676)  
> > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > connectToNode(NettyTransport.java:636)  
> > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > connectToNodeLight(NettyTransport.java:603)  
> > > > at org.elasticsearch.transport.TransportService.  
> > > > connectToNodeLight(TransportService.java:133)  
> > > > at org.elasticsearch.discovery.zen.ping.unicast.  
> > > > UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > ThreadPoolExecutor.java:1146)  
> > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > ThreadPoolExecutor.java:615)  
> > > > at java.lang.Thread.run(Thread.java:701)  
> > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > connection timed out: /10.239.36.98:9300  
> > > > at org.elasticsearch.common.netty.channel.socket.nio.  
> > > > NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > > 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
> > > > 
> > > > Thanks
> > > > 
> > > > --  
> > > > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%  
> > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > 
> > > > --  
> > > > 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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%  
> > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> 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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe).  
> To unsubscribe from this group and all its topics, 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/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACF%2B8rojiupZM9zYongESZzMV8GEn7SNHjTYij%2B9oS%3DA0xz3SA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rojiupZM9zYongESZzMV8GEn7SNHjTYij%2B9oS%3DA0xz3SA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 29, 2014, 9:56pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/12 "2014-01-29T21:56:45Z")

</div>

Hi,

Details

1. both servers are sing the same sec group  
2 all ports between 9200 and 9300 are open 0.0.0.0/0
2. ec2 instacances in us-east region
3. Did a fresh boot on 2 servers both servers are running. Both are not  
talking
4. Attached are the logs for both servers and the common elasticsearch.yml  
file
5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with  
elasticsearch-cloud-aws/2.0.0.RC1  
/usr/share/elasticsearch/plugins/cloud-aws  
ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls  
aws-java-sdk-1.3.32.jar commons-codec-1.4.jar commons-logging-1.1.1.jar  
elasticsearch-cloud-aws-2.0.0.RC1.jar httpclient-4.1.1.jar  
httpcore-4.1.jar

data\_bag("my\_data\_bag")  
db = data\_bag\_item("my\_data\_bag", "my")  
AWS\_ACCESS\_KEY\_ID = db[node.chef\_environment]['aws']['AWS\_ACCESS\_KEY\_ID']  
AWS\_SECRET\_ACCESS\_KEY =  
db[node.chef\_environment]['aws']['AWS\_SECRET\_ACCESS\_KEY']

version = '1.0.0.RC1'  
remote\_file  
"#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb" do  
source "  
[https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#{version}.deb](https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#%7Bversion%7D.deb)  
"  
action :create\_if\_missing  
end

dpkg\_package  
"#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb" do  
action :install  
end  
bash "add\_aws" do  
cwd "/usr/share/elasticsearch"  
code \<\<-EOH  
git clone [GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-aws.git)  
/usr/share/elasticsearch/bin/plugin -install  
elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1  
EOH  
not\_if {File.exists?("/usr/share/elasticsearch/elasticsearch-cloud-aws")}  
end

service "elasticsearch" do  
supports :restart =\> true, :start =\> true, :stop =\> true  
action [:enable, :start]  
end

template "/etc/elasticsearch/logging.yml" do  
path "/etc/elasticsearch/logging.yml"  
source "logging.yml.erb"  
owner "root"  
group "root"  
mode "0755"  
notifies :restart, resources(:service =\> "elasticsearch")  
end

template "/etc/elasticsearch/elasticsearch.yml" do  
path "/etc/elasticsearch/elasticsearch.yml"  
source "elasticsearch.yml.erb"  
owner "root"  
group "root"  
mode "0755"  
variables :AWS\_ACCESS\_KEY\_ID =\> "#{AWS\_ACCESS\_KEY\_ID}",  
:AWS\_SECRET\_ACCESS\_KEY =\> "#{AWS\_SECRET\_ACCESS\_KEY}", :region =\> "us-east-1"  
notifies :restart, resources(:service =\> "elasticsearch")  
end

On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery \<[davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)

> wrote:

> sure..let me the logs together and will post two files ..one log file for  
> each of the servers.
> 
> Thanks
> 
> On Tue, Jan 28, 2014 at 6:25 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:
> 
> > Is it a known problem? Not yet. That's the reason I'm asking for logs. I  
> > would like to understand what is happening here. So full logs on both nodes  
> > would help.
> > 
> > The way you set unicast is fine to me. But please, could you share with  
> > me (even through Direct mail) your elasticsearch.yml file and your logs in  
> > TRACE level?  
> > You can replace your credentials settings with XXXXXXXX. Please don't  
> > change anything else. I'd like to reproduce your case.
> > 
> > Thanks!
> > 
> > --  
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 27 janv. 2014 à 22:57, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) a  
> > écrit :
> > 
> > I have to say..it this a know problem?
> > 
> > I removed the keys.
> > 
> > So.. should the servers still cluster? Well....its not.........again  
> > given that the two machine can talk to each other via telent, in the same  
> > region, same sec group restarted services etc....no go......no cluster
> > 
> > So....how do I manually configure nodes? I have given up on auto  
> > discover. Clearly does now work for me.
> > 
> > Is the below an example?
> > 
> > discovery.zen.ping.multicast.enabled: false  
> > discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com:9200](http://1.test.com:9200)"]
> > 
> > Thanks
> > 
> > On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:
> > 
> > > Yes. Could you gist it (and remove first keys / secrets of course)?
> > > 
> > > --  
> > > David 😉  
> > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > 
> > > Le 27 janv. 2014 à 20:53, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a  
> > > écrit :
> > > 
> > > I assume that means this in the logging.yml fike?
> > > 
> > > # discovery
> > > 
> > > discovery: TRACE
> > > 
> > > I do have it on...what should I be looking for in the logs?
> > > 
> > > On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:
> > > 
> > > > Hi,
> > > > 
> > > > As an fyi..I can telnet into the other machine. Its only ES that does  
> > > > not work despite following the online docs.
> > > > 
> > > > If ES aws auto discovery does not work l assuming assume that  
> > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/)  
> > > > reference/current/modules-discovery-zen.html will work?
> > > > 
> > > > Thanks
> > > > 
> > > > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > > > 
> > > > > Hi David,
> > > > > 
> > > > > I think you should have nodes running under the same security group.  
> > > > > In that case, you don't have to open 9300-9400 ports to public.  
> > > > > If they don't belong to the same group or if you want to reach them  
> > > > > from outside ec2 platform (public IP), then you need to set host\_type  
> > > > > to public\_ip.
> > > > > 
> > > > > It sounds like your nodes are trying to connect with private ip here  
> > > > > (which is default).
> > > > > 
> > > > > My 2 cents
> > > > > 
> > > > > --  
> > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_  
> > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > > > 
> > > > > Le 27 janvier 2014 at 18:07:48, David Montgomery ([davidmo...@gmail.com](mailto:davidmo...@gmail.com))  
> > > > > a écrit:
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > I have two nodes runnging on ec2.
> > > > > 
> > > > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > > > {  
> > > > > "cluster\_name" : "12345elasticsearch",  
> > > > > "status" : "green",  
> > > > > "timed\_out" : false,  
> > > > > "number\_of\_nodes" : 1,  
> > > > > "number\_of\_data\_nodes" : 1,  
> > > > > "active\_primary\_shards" : 0,  
> > > > > "active\_shards" : 0,  
> > > > > "relocating\_shards" : 0,  
> > > > > "initializing\_shards" : 0,  
> > > > > "unassigned\_shards" : 0  
> > > > > }
> > > > > 
> > > > > So..its fair to say that ec2 clustering did not work given the below  
> > > > > config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> > > > > What elasticsearch advertiseres is that all that is needed.
> > > > > 
> > > > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu  
> > > > > 12.04
> > > > > 
> > > > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > > > discovery.type: ec2
> > > > > 
> > > > > In the logs I see the below:
> > > > > 
> > > > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > > > [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-  
> > > > > elasticsearch-east-development-20140127160434][inet[/  
> > > > > 10.211.29.210:9300]]  
> > > > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > connectToChannelsLight(NettyTransport.java:676)  
> > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > connectToNode(NettyTransport.java:636)  
> > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > connectToNodeLight(NettyTransport.java:603)  
> > > > > at org.elasticsearch.transport.TransportService.  
> > > > > connectToNodeLight(TransportService.java:133)  
> > > > > at org.elasticsearch.discovery.zen.ping.unicast.  
> > > > > UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > > ThreadPoolExecutor.java:1146)  
> > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > ThreadPoolExecutor.java:615)  
> > > > > at java.lang.Thread.run(Thread.java:701)  
> > > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > > connection timed out: /10.239.36.98:9300  
> > > > > at org.elasticsearch.common.netty.channel.socket.nio.  
> > > > > NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > > > 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
> > > > > 
> > > > > Thanks
> > > > > 
> > > > > --  
> > > > > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%  
> > > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > 
> > > > > --  
> > > > > 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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%  
> > > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > 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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com)  
> > .  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to a topic in the  
> > Google Groups "elasticsearch" group.  
> > To unsubscribe from this topic, visit  
> > [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe).  
> > To unsubscribe from this group and all its topics, 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/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr)  
> > .
> > 
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [January 30, 2014, 4:20pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/13 "2014-01-30T16:20:29Z")

</div>

Did you override your network.host configuration parameter by any chance?

--  
Ivan

On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery \<[davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)

> wrote:

> Hi,
> 
> Details
> 
> 1. both servers are sing the same sec group  
> 2 all ports between 9200 and 9300 are open 0.0.0.0/0
> 2. ec2 instacances in us-east region
> 3. Did a fresh boot on 2 servers both servers are running. Both are not  
> talking
> 4. Attached are the logs for both servers and the common elasticsearch.yml  
> file
> 5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with  
> elasticsearch-cloud-aws/2.0.0.RC1  
> /usr/share/elasticsearch/plugins/cloud-aws  
> ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls  
> aws-java-sdk-1.3.32.jar commons-codec-1.4.jar commons-logging-1.1.1.jar  
> elasticsearch-cloud-aws-2.0.0.RC1.jar httpclient-4.1.1.jar  
> httpcore-4.1.jar
> 
> data\_bag("my\_data\_bag")  
> db = data\_bag\_item("my\_data\_bag", "my")  
> AWS\_ACCESS\_KEY\_ID = db[node.chef\_environment]['aws']['AWS\_ACCESS\_KEY\_ID']  
> AWS\_SECRET\_ACCESS\_KEY =  
> db[node.chef\_environment]['aws']['AWS\_SECRET\_ACCESS\_KEY']
> 
> version = '1.0.0.RC1'  
> remote\_file  
> "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb" do  
> source "  
> [https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#{version}.deb](https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#%7Bversion%7D.deb)  
> "  
> action :create\_if\_missing  
> end
> 
> dpkg\_package  
> "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb" do  
> action :install  
> end  
> bash "add\_aws" do  
> cwd "/usr/share/elasticsearch"  
> code \<\<-EOH  
> git clone [GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-aws.git)  
> /usr/share/elasticsearch/bin/plugin -install  
> elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1  
> EOH  
> not\_if {File.exists?("/usr/share/elasticsearch/elasticsearch-cloud-aws")}  
> end
> 
> service "elasticsearch" do  
> supports :restart =\> true, :start =\> true, :stop =\> true  
> action [:enable, :start]  
> end
> 
> template "/etc/elasticsearch/logging.yml" do  
> path "/etc/elasticsearch/logging.yml"  
> source "logging.yml.erb"  
> owner "root"  
> group "root"  
> mode "0755"  
> notifies :restart, resources(:service =\> "elasticsearch")  
> end
> 
> template "/etc/elasticsearch/elasticsearch.yml" do  
> path "/etc/elasticsearch/elasticsearch.yml"  
> source "elasticsearch.yml.erb"  
> owner "root"  
> group "root"  
> mode "0755"  
> variables :AWS\_ACCESS\_KEY\_ID =\> "#{AWS\_ACCESS\_KEY\_ID}",  
> :AWS\_SECRET\_ACCESS\_KEY =\> "#{AWS\_SECRET\_ACCESS\_KEY}", :region =\> "us-east-1"  
> notifies :restart, resources(:service =\> "elasticsearch")  
> end
> 
> On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery \<  
> [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)\> wrote:
> 
> > sure..let me the logs together and will post two files ..one log file for  
> > each of the servers.
> > 
> > Thanks
> > 
> > On Tue, Jan 28, 2014 at 6:25 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:
> > 
> > > Is it a known problem? Not yet. That's the reason I'm asking for logs. I  
> > > would like to understand what is happening here. So full logs on both nodes  
> > > would help.
> > > 
> > > The way you set unicast is fine to me. But please, could you share with  
> > > me (even through Direct mail) your elasticsearch.yml file and your logs in  
> > > TRACE level?  
> > > You can replace your credentials settings with XXXXXXXX. Please don't  
> > > change anything else. I'd like to reproduce your case.
> > > 
> > > Thanks!
> > > 
> > > --  
> > > David 😉  
> > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > 
> > > Le 27 janv. 2014 à 22:57, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)  
> > > a écrit :
> > > 
> > > I have to say..it this a know problem?
> > > 
> > > I removed the keys.
> > > 
> > > So.. should the servers still cluster? Well....its not.........again  
> > > given that the two machine can talk to each other via telent, in the same  
> > > region, same sec group restarted services etc....no go......no cluster
> > > 
> > > So....how do I manually configure nodes? I have given up on auto  
> > > discover. Clearly does now work for me.
> > > 
> > > Is the below an example?
> > > 
> > > discovery.zen.ping.multicast.enabled: false  
> > > discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com:9200](http://1.test.com:9200)"]
> > > 
> > > Thanks
> > > 
> > > On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:
> > > 
> > > > Yes. Could you gist it (and remove first keys / secrets of course)?
> > > > 
> > > > --  
> > > > David 😉  
> > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > 
> > > > Le 27 janv. 2014 à 20:53, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a  
> > > > écrit :
> > > > 
> > > > I assume that means this in the logging.yml fike?
> > > > 
> > > > # discovery
> > > > 
> > > > discovery: TRACE
> > > > 
> > > > I do have it on...what should I be looking for in the logs?
> > > > 
> > > > On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:
> > > > 
> > > > > Hi,
> > > > > 
> > > > > As an fyi..I can telnet into the other machine. Its only ES that does  
> > > > > not work despite following the online docs.
> > > > > 
> > > > > If ES aws auto discovery does not work l assuming assume that  
> > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/)  
> > > > > reference/current/modules-discovery-zen.html will work?
> > > > > 
> > > > > Thanks
> > > > > 
> > > > > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > > > > 
> > > > > > Hi David,
> > > > > > 
> > > > > > I think you should have nodes running under the same security group.  
> > > > > > In that case, you don't have to open 9300-9400 ports to public.  
> > > > > > If they don't belong to the same group or if you want to reach them  
> > > > > > from outside ec2 platform (public IP), then you need to set host\_type  
> > > > > > to public\_ip.
> > > > > > 
> > > > > > It sounds like your nodes are trying to connect with private ip here  
> > > > > > (which is default).
> > > > > > 
> > > > > > My 2 cents
> > > > > > 
> > > > > > --  
> > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> > > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_  
> > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > > > > 
> > > > > > Le 27 janvier 2014 at 18:07:48, David Montgomery (  
> > > > > > [davidmo...@gmail.com](mailto:davidmo...@gmail.com)) a écrit:
> > > > > > 
> > > > > > Hi,
> > > > > > 
> > > > > > I have two nodes runnging on ec2.
> > > > > > 
> > > > > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > > > > {  
> > > > > > "cluster\_name" : "12345elasticsearch",  
> > > > > > "status" : "green",  
> > > > > > "timed\_out" : false,  
> > > > > > "number\_of\_nodes" : 1,  
> > > > > > "number\_of\_data\_nodes" : 1,  
> > > > > > "active\_primary\_shards" : 0,  
> > > > > > "active\_shards" : 0,  
> > > > > > "relocating\_shards" : 0,  
> > > > > > "initializing\_shards" : 0,  
> > > > > > "unassigned\_shards" : 0  
> > > > > > }
> > > > > > 
> > > > > > So..its fair to say that ec2 clustering did not work given the below  
> > > > > > config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> > > > > > What elasticsearch advertiseres is that all that is needed.
> > > > > > 
> > > > > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on  
> > > > > > ubuntu 12.04
> > > > > > 
> > > > > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > > > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > > > > discovery.type: ec2
> > > > > > 
> > > > > > In the logs I see the below:
> > > > > > 
> > > > > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > > > > [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-  
> > > > > > elasticsearch-east-development-20140127160434][inet[/  
> > > > > > 10.211.29.210:9300]]  
> > > > > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > > > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > connectToChannelsLight(NettyTransport.java:676)  
> > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > connectToNode(NettyTransport.java:636)  
> > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > connectToNodeLight(NettyTransport.java:603)  
> > > > > > at org.elasticsearch.transport.TransportService.  
> > > > > > connectToNodeLight(TransportService.java:133)  
> > > > > > at org.elasticsearch.discovery.zen.ping.unicast.  
> > > > > > UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > > > ThreadPoolExecutor.java:1146)  
> > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > > ThreadPoolExecutor.java:615)  
> > > > > > at java.lang.Thread.run(Thread.java:701)  
> > > > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > > > connection timed out: /10.239.36.98:9300  
> > > > > > at org.elasticsearch.common.netty.channel.socket.nio.  
> > > > > > NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > > > > 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
> > > > > > 
> > > > > > Thanks
> > > > > > 
> > > > > > --  
> > > > > > 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%  
> > > > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > 
> > > > > > --  
> > > > > > 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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%  
> > > > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > 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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com)  
> > > .  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > You received this message because you are subscribed to a topic in the  
> > > Google Groups "elasticsearch" group.  
> > > To unsubscribe from this topic, visit  
> > > [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe).  
> > > To unsubscribe from this group and all its topics, 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/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr)  
> > > .
> > > 
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> 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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CALY%3DcQDHsDjF0AGUAoC3rLz\_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDHsDjF0AGUAoC3rLz_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [January 31, 2014, 8:46pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/14 "2014-01-31T20:46:07Z")

</div>

Hi,

In chef I used -N flag which changes the host name when using chef-client.  
I removed the flag and built again. No difference. I have two nodes  
running. Both have the name cluster name, ports are 100% wide open...and  
wow..ES cant talk despite both running in the same region.

So...ES...any suggestions?

root@ip-10-238-131-236:/var/log/elasticsearch# hostname  
ip-10-238-131-236

root@ip-10-238-131-236:/var/log/elasticsearch# curl -XGET '  
[http://127.0.0.1:9200/\_cluster/health?pretty=true](http://127.0.0.1:9200/_cluster/health?pretty=true)'  
{  
"cluster\_name" : "mizilaelasticsearch",  
"status" : "green",  
"timed\_out" : false,  
"number\_of\_nodes" : 1,  
"number\_of\_data\_nodes" : 1,  
"active\_primary\_shards" : 0,  
"active\_shards" : 0,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0  
}

On Fri, Jan 31, 2014 at 12:20 AM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote:

> Did you override your network.host configuration parameter by any chance?
> 
> --  
> Ivan
> 
> On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery \<  
> [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)\> wrote:
> 
> > Hi,
> > 
> > Details
> > 
> > 1. both servers are sing the same sec group  
> > 2 all ports between 9200 and 9300 are open 0.0.0.0/0
> > 2. ec2 instacances in us-east region
> > 3. Did a fresh boot on 2 servers both servers are running. Both are not  
> > talking
> > 4. Attached are the logs for both servers and the common  
> > elasticsearch.yml file
> > 5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with  
> > elasticsearch-cloud-aws/2.0.0.RC1  
> > /usr/share/elasticsearch/plugins/cloud-aws  
> > ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls  
> > aws-java-sdk-1.3.32.jar commons-codec-1.4.jar  
> > commons-logging-1.1.1.jar elasticsearch-cloud-aws-2.0.0.RC1.jar  
> > httpclient-4.1.1.jar httpcore-4.1.jar
> > 
> > data\_bag("my\_data\_bag")  
> > db = data\_bag\_item("my\_data\_bag", "my")  
> > AWS\_ACCESS\_KEY\_ID = db[node.chef\_environment]['aws']['AWS\_ACCESS\_KEY\_ID']  
> > AWS\_SECRET\_ACCESS\_KEY =  
> > db[node.chef\_environment]['aws']['AWS\_SECRET\_ACCESS\_KEY']
> > 
> > version = '1.0.0.RC1'  
> > remote\_file  
> > "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb" do  
> > source "  
> > [https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#{version}.deb](https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#%7Bversion%7D.deb)  
> > "  
> > action :create\_if\_missing  
> > end
> > 
> > dpkg\_package  
> > "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb" do  
> > action :install  
> > end  
> > bash "add\_aws" do  
> > cwd "/usr/share/elasticsearch"  
> > code \<\<-EOH  
> > git clone  
> > [GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-aws.git)  
> > /usr/share/elasticsearch/bin/plugin -install  
> > elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1  
> > EOH  
> > not\_if  
> > {File.exists?("/usr/share/elasticsearch/elasticsearch-cloud-aws")}  
> > end
> > 
> > service "elasticsearch" do  
> > supports :restart =\> true, :start =\> true, :stop =\> true  
> > action [:enable, :start]  
> > end
> > 
> > template "/etc/elasticsearch/logging.yml" do  
> > path "/etc/elasticsearch/logging.yml"  
> > source "logging.yml.erb"  
> > owner "root"  
> > group "root"  
> > mode "0755"  
> > notifies :restart, resources(:service =\> "elasticsearch")  
> > end
> > 
> > template "/etc/elasticsearch/elasticsearch.yml" do  
> > path "/etc/elasticsearch/elasticsearch.yml"  
> > source "elasticsearch.yml.erb"  
> > owner "root"  
> > group "root"  
> > mode "0755"  
> > variables :AWS\_ACCESS\_KEY\_ID =\> "#{AWS\_ACCESS\_KEY\_ID}",  
> > :AWS\_SECRET\_ACCESS\_KEY =\> "#{AWS\_SECRET\_ACCESS\_KEY}", :region =\> "us-east-1"  
> > notifies :restart, resources(:service =\> "elasticsearch")  
> > end
> > 
> > On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery \<  
> > [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)\> wrote:
> > 
> > > sure..let me the logs together and will post two files ..one log file  
> > > for each of the servers.
> > > 
> > > Thanks
> > > 
> > > On Tue, Jan 28, 2014 at 6:25 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:
> > > 
> > > > Is it a known problem? Not yet. That's the reason I'm asking for logs.  
> > > > I would like to understand what is happening here. So full logs on both  
> > > > nodes would help.
> > > > 
> > > > The way you set unicast is fine to me. But please, could you share with  
> > > > me (even through Direct mail) your elasticsearch.yml file and your logs in  
> > > > TRACE level?  
> > > > You can replace your credentials settings with XXXXXXXX. Please don't  
> > > > change anything else. I'd like to reproduce your case.
> > > > 
> > > > Thanks!
> > > > 
> > > > --  
> > > > David 😉  
> > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > 
> > > > Le 27 janv. 2014 à 22:57, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)  
> > > > a écrit :
> > > > 
> > > > I have to say..it this a know problem?
> > > > 
> > > > I removed the keys.
> > > > 
> > > > So.. should the servers still cluster? Well....its not.........again  
> > > > given that the two machine can talk to each other via telent, in the same  
> > > > region, same sec group restarted services etc....no go......no cluster
> > > > 
> > > > So....how do I manually configure nodes? I have given up on auto  
> > > > discover. Clearly does now work for me.
> > > > 
> > > > Is the below an example?
> > > > 
> > > > discovery.zen.ping.multicast.enabled: false  
> > > > discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com](http://1.test.com)  
> > > > :9200"]
> > > > 
> > > > Thanks
> > > > 
> > > > On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:
> > > > 
> > > > > Yes. Could you gist it (and remove first keys / secrets of course)?
> > > > > 
> > > > > --  
> > > > > David 😉  
> > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > > 
> > > > > Le 27 janv. 2014 à 20:53, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a  
> > > > > écrit :
> > > > > 
> > > > > I assume that means this in the logging.yml fike?
> > > > > 
> > > > > # discovery
> > > > > 
> > > > > discovery: TRACE
> > > > > 
> > > > > I do have it on...what should I be looking for in the logs?
> > > > > 
> > > > > On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:
> > > > > 
> > > > > > Hi,
> > > > > > 
> > > > > > As an fyi..I can telnet into the other machine. Its only ES that  
> > > > > > does not work despite following the online docs.
> > > > > > 
> > > > > > If ES aws auto discovery does not work l assuming assume that  
> > > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/)  
> > > > > > reference/current/modules-discovery-zen.html will work?
> > > > > > 
> > > > > > Thanks
> > > > > > 
> > > > > > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > > > > > 
> > > > > > > Hi David,
> > > > > > > 
> > > > > > > I think you should have nodes running under the same security group.  
> > > > > > > In that case, you don't have to open 9300-9400 ports to public.  
> > > > > > > If they don't belong to the same group or if you want to reach them  
> > > > > > > from outside ec2 platform (public IP), then you need to set host\_type  
> > > > > > > to public\_ip.
> > > > > > > 
> > > > > > > It sounds like your nodes are trying to connect with private ip here  
> > > > > > > (which is default).
> > > > > > > 
> > > > > > > My 2 cents
> > > > > > > 
> > > > > > > --  
> > > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> > > > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_  
> > > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > > > > > 
> > > > > > > Le 27 janvier 2014 at 18:07:48, David Montgomery (  
> > > > > > > [davidmo...@gmail.com](mailto:davidmo...@gmail.com)) a écrit:
> > > > > > > 
> > > > > > > Hi,
> > > > > > > 
> > > > > > > I have two nodes runnging on ec2.
> > > > > > > 
> > > > > > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > > > > > {  
> > > > > > > "cluster\_name" : "12345elasticsearch",  
> > > > > > > "status" : "green",  
> > > > > > > "timed\_out" : false,  
> > > > > > > "number\_of\_nodes" : 1,  
> > > > > > > "number\_of\_data\_nodes" : 1,  
> > > > > > > "active\_primary\_shards" : 0,  
> > > > > > > "active\_shards" : 0,  
> > > > > > > "relocating\_shards" : 0,  
> > > > > > > "initializing\_shards" : 0,  
> > > > > > > "unassigned\_shards" : 0  
> > > > > > > }
> > > > > > > 
> > > > > > > So..its fair to say that ec2 clustering did not work given the below  
> > > > > > > config. Yes...the aws keys are correct and I have port 9200-9400 open.  
> > > > > > > What elasticsearch advertiseres is that all that is needed.
> > > > > > > 
> > > > > > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on  
> > > > > > > ubuntu 12.04
> > > > > > > 
> > > > > > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > > > > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > > > > > discovery.type: ec2
> > > > > > > 
> > > > > > > In the logs I see the below:
> > > > > > > 
> > > > > > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > > > > > [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-  
> > > > > > > elasticsearch-east-development-20140127160434][inet[/  
> > > > > > > 10.211.29.210:9300]]  
> > > > > > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > > > > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > connectToChannelsLight(NettyTransport.java:676)  
> > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > connectToNode(NettyTransport.java:636)  
> > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > connectToNodeLight(NettyTransport.java:603)  
> > > > > > > at org.elasticsearch.transport.TransportService.  
> > > > > > > connectToNodeLight(TransportService.java:133)  
> > > > > > > at org.elasticsearch.discovery.zen.ping.unicast.  
> > > > > > > UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > > > > ThreadPoolExecutor.java:1146)  
> > > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > > > ThreadPoolExecutor.java:615)  
> > > > > > > at java.lang.Thread.run(Thread.java:701)  
> > > > > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > > > > connection timed out: /10.239.36.98:9300  
> > > > > > > at org.elasticsearch.common.netty.channel.socket.nio.  
> > > > > > > NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > > > > > 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
> > > > > > > 
> > > > > > > Thanks
> > > > > > > 
> > > > > > > --  
> > > > > > > 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/ec028f53-](https://groups.google.com/d/msgid/elasticsearch/ec028f53-)  
> > > > > > > c6b2-48e1-b714-a6f1ac7ae1cd%[40googlegroups.com](http://40googlegroups.com).  
> > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > > 
> > > > > > > --  
> > > > > > > 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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%  
> > > > > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > 
> > > > --  
> > > > 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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com)  
> > > > .  
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to a topic in the  
> > > > Google Groups "elasticsearch" group.  
> > > > To unsubscribe from this topic, visit  
> > > > [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe)  
> > > > .  
> > > > To unsubscribe from this group and all its topics, 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/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr)  
> > > > .
> > > > 
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > 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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com)  
> > .
> > 
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe).  
> To unsubscribe from this group and all its topics, 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/CALY%3DcQDHsDjF0AGUAoC3rLz\_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDHsDjF0AGUAoC3rLz_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACF%2B8rrWR0AgKk%2B%3DZkR-g3b9EEW\_H-V4m-THh%2B50ct-gfqEb\_g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rrWR0AgKk%2B%3DZkR-g3b9EEW_H-V4m-THh%2B50ct-gfqEb_g%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Jonathan\_Goodwin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonathan_goodwin/32/1832_2.png) [@Jonathan\_Goodwin](https://discuss.elastic.co/u/Jonathan_Goodwin)\
**Post date:** [February 2, 2014, 2:10am UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/15 "2014-02-02T02:10:45Z")

</div>

Hello David and David,

I took a look at the logs / configs posted and mine are mostly similar  
(though i'm not using any rivers) and I'm having the same issue.  
I've tested on 0.90.9 and 0.90.7, I hadn't tried the 1.0.0RC yet because  
the logstash website suggested I stick to 0.90.9  
If you need any more logs / config samples I'd be happy to provide those.

Best,  
JG

On Friday, January 31, 2014 3:46:07 PM UTC-5, David Montgomery wrote:

> Hi,
> 
> In chef I used -N flag which changes the host name when using  
> chef-client. I removed the flag and built again. No difference. I have  
> two nodes running. Both have the name cluster name, ports are 100% wide  
> open...and wow..ES cant talk despite both running in the same region.
> 
> So...ES...any suggestions?
> 
> root@ip-10-238-131-236:/var/log/elasticsearch# hostname  
> ip-10-238-131-236
> 
> root@ip-10-238-131-236:/var/log/elasticsearch# curl -XGET '  
> [http://127.0.0.1:9200/\_cluster/health?pretty=true](http://127.0.0.1:9200/_cluster/health?pretty=true)'  
> {  
> "cluster\_name" : "mizilaelasticsearch",  
> "status" : "green",  
> "timed\_out" : false,  
> "number\_of\_nodes" : 1,  
> "number\_of\_data\_nodes" : 1,  
> "active\_primary\_shards" : 0,  
> "active\_shards" : 0,  
> "relocating\_shards" : 0,  
> "initializing\_shards" : 0,  
> "unassigned\_shards" : 0  
> }
> 
> On Fri, Jan 31, 2014 at 12:20 AM, Ivan Brusic \<[iv...@brusic.com](mailto:iv...@brusic.com)\<javascript:\>
> 
> > wrote:
> 
> > Did you override your network.host configuration parameter by any chance?
> > 
> > --  
> > Ivan
> > 
> > On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery \<[davidmo...@gmail.com](mailto:davidmo...@gmail.com)\<javascript:\>
> > 
> > > wrote:
> > 
> > > Hi,
> > > 
> > > Details
> > > 
> > > 1. both servers are sing the same sec group  
> > > 2 all ports between 9200 and 9300 are open 0.0.0.0/0
> > > 2. ec2 instacances in us-east region
> > > 3. Did a fresh boot on 2 servers both servers are running. Both are not  
> > > talking
> > > 4. Attached are the logs for both servers and the common  
> > > elasticsearch.yml file
> > > 5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with  
> > > elasticsearch-cloud-aws/2.0.0.RC1  
> > > /usr/share/elasticsearch/plugins/cloud-aws  
> > > ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls  
> > > aws-java-sdk-1.3.32.jar commons-codec-1.4.jar  
> > > commons-logging-1.1.1.jar elasticsearch-cloud-aws-2.0.0.RC1.jar  
> > > httpclient-4.1.1.jar httpcore-4.1.jar
> > > 
> > > data\_bag("my\_data\_bag")  
> > > db = data\_bag\_item("my\_data\_bag", "my")  
> > > AWS\_ACCESS\_KEY\_ID = db[node.chef\_environment]['aws']['AWS\_ACCESS\_KEY\_ID']  
> > > AWS\_SECRET\_ACCESS\_KEY =  
> > > db[node.chef\_environment]['aws']['AWS\_SECRET\_ACCESS\_KEY']
> > > 
> > > version = '1.0.0.RC1'  
> > > remote\_file  
> > > "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb" do  
> > > source "  
> > > [https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#{version}.deb](https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#%7Bversion%7D.deb)  
> > > "  
> > > action :create\_if\_missing  
> > > end
> > > 
> > > dpkg\_package  
> > > "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb" do  
> > > action :install  
> > > end  
> > > bash "add\_aws" do  
> > > cwd "/usr/share/elasticsearch"  
> > > code \<\<-EOH  
> > > git clone  
> > > [GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-aws.git)  
> > > /usr/share/elasticsearch/bin/plugin -install  
> > > elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1  
> > > EOH  
> > > not\_if  
> > > {File.exists?("/usr/share/elasticsearch/elasticsearch-cloud-aws")}  
> > > end
> > > 
> > > service "elasticsearch" do  
> > > supports :restart =\> true, :start =\> true, :stop =\> true  
> > > action [:enable, :start]  
> > > end
> > > 
> > > template "/etc/elasticsearch/logging.yml" do  
> > > path "/etc/elasticsearch/logging.yml"  
> > > source "logging.yml.erb"  
> > > owner "root"  
> > > group "root"  
> > > mode "0755"  
> > > notifies :restart, resources(:service =\> "elasticsearch")  
> > > end
> > > 
> > > template "/etc/elasticsearch/elasticsearch.yml" do  
> > > path "/etc/elasticsearch/elasticsearch.yml"  
> > > source "elasticsearch.yml.erb"  
> > > owner "root"  
> > > group "root"  
> > > mode "0755"  
> > > variables :AWS\_ACCESS\_KEY\_ID =\> "#{AWS\_ACCESS\_KEY\_ID}",  
> > > :AWS\_SECRET\_ACCESS\_KEY =\> "#{AWS\_SECRET\_ACCESS\_KEY}", :region =\> "us-east-1"  
> > > notifies :restart, resources(:service =\> "elasticsearch")  
> > > end
> > > 
> > > On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery \<[davidmo...@gmail.com](mailto:davidmo...@gmail.com)\<javascript:\>
> > > 
> > > > wrote:
> > > 
> > > > sure..let me the logs together and will post two files ..one log file  
> > > > for each of the servers.
> > > > 
> > > > Thanks
> > > > 
> > > > On Tue, Jan 28, 2014 at 6:25 AM, David Pilato \<[da...@pilato.fr](mailto:da...@pilato.fr)\<javascript:\>
> > > > 
> > > > > wrote:
> > > > 
> > > > > Is it a known problem? Not yet. That's the reason I'm asking for logs.  
> > > > > I would like to understand what is happening here. So full logs on both  
> > > > > nodes would help.
> > > > > 
> > > > > The way you set unicast is fine to me. But please, could you share  
> > > > > with me (even through Direct mail) your elasticsearch.yml file and your  
> > > > > logs in TRACE level?  
> > > > > You can replace your credentials settings with XXXXXXXX. Please don't  
> > > > > change anything else. I'd like to reproduce your case.
> > > > > 
> > > > > Thanks!
> > > > > 
> > > > > --  
> > > > > David 😉  
> > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > > 
> > > > > Le 27 janv. 2014 à 22:57, David Montgomery \<[davidmo...@gmail.com](mailto:davidmo...@gmail.com)\<javascript:\>\>  
> > > > > a écrit :
> > > > > 
> > > > > I have to say..it this a know problem?
> > > > > 
> > > > > I removed the keys.
> > > > > 
> > > > > So.. should the servers still cluster? Well....its not.........again  
> > > > > given that the two machine can talk to each other via telent, in the same  
> > > > > region, same sec group restarted services etc....no go......no cluster
> > > > > 
> > > > > So....how do I manually configure nodes? I have given up on auto  
> > > > > discover. Clearly does now work for me.
> > > > > 
> > > > > Is the below an example?
> > > > > 
> > > > > discovery.zen.ping.multicast.enabled: false  
> > > > > discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com](http://1.test.com)  
> > > > > :9200"]
> > > > > 
> > > > > Thanks
> > > > > 
> > > > > On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:
> > > > > 
> > > > > > Yes. Could you gist it (and remove first keys / secrets of course)?
> > > > > > 
> > > > > > --  
> > > > > > David 😉  
> > > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > > > 
> > > > > > Le 27 janv. 2014 à 20:53, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a  
> > > > > > écrit :
> > > > > > 
> > > > > > I assume that means this in the logging.yml fike?
> > > > > > 
> > > > > > # discovery
> > > > > > 
> > > > > > discovery: TRACE
> > > > > > 
> > > > > > I do have it on...what should I be looking for in the logs?
> > > > > > 
> > > > > > On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:
> > > > > > 
> > > > > > > Hi,
> > > > > > > 
> > > > > > > As an fyi..I can telnet into the other machine. Its only ES that  
> > > > > > > does not work despite following the online docs.
> > > > > > > 
> > > > > > > If ES aws auto discovery does not work l assuming assume that  
> > > > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/)  
> > > > > > > reference/current/modules-discovery-zen.html will work?
> > > > > > > 
> > > > > > > Thanks
> > > > > > > 
> > > > > > > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > > > > > > 
> > > > > > > > Hi David,
> > > > > > > > 
> > > > > > > > I think you should have nodes running under the same security  
> > > > > > > > group. In that case, you don't have to open 9300-9400 ports to public.  
> > > > > > > > If they don't belong to the same group or if you want to reach them  
> > > > > > > > from outside ec2 platform (public IP), then you need to set host\_type  
> > > > > > > > to public\_ip.
> > > > > > > > 
> > > > > > > > It sounds like your nodes are trying to connect with private ip  
> > > > > > > > here (which is default).
> > > > > > > > 
> > > > > > > > My 2 cents
> > > > > > > > 
> > > > > > > > --  
> > > > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> > > > > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_  
> > > > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > > > > > > 
> > > > > > > > Le 27 janvier 2014 at 18:07:48, David Montgomery (  
> > > > > > > > [davidmo...@gmail.com](mailto:davidmo...@gmail.com)) a écrit:
> > > > > > > > 
> > > > > > > > Hi,
> > > > > > > > 
> > > > > > > > I have two nodes runnging on ec2.
> > > > > > > > 
> > > > > > > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > > > > > > {  
> > > > > > > > "cluster\_name" : "12345elasticsearch",  
> > > > > > > > "status" : "green",  
> > > > > > > > "timed\_out" : false,  
> > > > > > > > "number\_of\_nodes" : 1,  
> > > > > > > > "number\_of\_data\_nodes" : 1,  
> > > > > > > > "active\_primary\_shards" : 0,  
> > > > > > > > "active\_shards" : 0,  
> > > > > > > > "relocating\_shards" : 0,  
> > > > > > > > "initializing\_shards" : 0,  
> > > > > > > > "unassigned\_shards" : 0  
> > > > > > > > }
> > > > > > > > 
> > > > > > > > So..its fair to say that ec2 clustering did not work given the  
> > > > > > > > below config. Yes...the aws keys are correct and I have port 9200-9400  
> > > > > > > > open. What elasticsearch advertiseres is that all that is needed.
> > > > > > > > 
> > > > > > > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on  
> > > > > > > > ubuntu 12.04
> > > > > > > > 
> > > > > > > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > > > > > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > > > > > > discovery.type: ec2
> > > > > > > > 
> > > > > > > > In the logs I see the below:
> > > > > > > > 
> > > > > > > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > > > > > > [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-  
> > > > > > > > elasticsearch-east-development-20140127160434][inet[/  
> > > > > > > > 10.211.29.210:9300]]  
> > > > > > > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > > > > > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > connectToChannelsLight(NettyTransport.java:676)  
> > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > connectToNode(NettyTransport.java:636)  
> > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > connectToNodeLight(NettyTransport.java:603)  
> > > > > > > > at org.elasticsearch.transport.TransportService.  
> > > > > > > > connectToNodeLight(TransportService.java:133)  
> > > > > > > > at org.elasticsearch.discovery.zen.ping.unicast.  
> > > > > > > > UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > > > > > ThreadPoolExecutor.java:1146)  
> > > > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > > > > ThreadPoolExecutor.java:615)  
> > > > > > > > at java.lang.Thread.run(Thread.java:701)  
> > > > > > > > Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException:  
> > > > > > > > connection timed out: /10.239.36.98:9300  
> > > > > > > > at org.elasticsearch.common.netty.channel.socket.nio.  
> > > > > > > > NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > > > > > > 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
> > > > > > > > 
> > > > > > > > Thanks
> > > > > > > > 
> > > > > > > > --  
> > > > > > > > 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/ec028f53-](https://groups.google.com/d/msgid/elasticsearch/ec028f53-)  
> > > > > > > > c6b2-48e1-b714-a6f1ac7ae1cd%[40googlegroups.com](http://40googlegroups.com).  
> > > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > > > 
> > > > > > > > --  
> > > > > > > > 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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%  
> > > > > > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > 
> > > > > --  
> > > > > 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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com)  
> > > > > .  
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > 
> > > > > --  
> > > > > You received this message because you are subscribed to a topic in the  
> > > > > Google Groups "elasticsearch" group.  
> > > > > To unsubscribe from this topic, visit  
> > > > > [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe)  
> > > > > .  
> > > > > To unsubscribe from this group and all its topics, 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/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr)  
> > > > > .
> > > > > 
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > 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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com)  
> > > .
> > > 
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to a topic in the  
> > Google Groups "elasticsearch" group.  
> > To unsubscribe from this topic, visit  
> > [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe).  
> > To unsubscribe from this group and all its topics, 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/CALY%3DcQDHsDjF0AGUAoC3rLz\_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDHsDjF0AGUAoC3rLz_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com)  
> > .
> > 
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/a48fe555-0b95-4281-ba9e-351b21f4a9e9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a48fe555-0b95-4281-ba9e-351b21f4a9e9%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [February 3, 2014, 10:51pm UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/16 "2014-02-03T22:51:02Z")

</div>

Hi Jonathan

Just be clear...you could not cluster? I wili try the lastest stable  
release cuase I am giving up on 1.0.0RC.

Thanks

On Sun, Feb 2, 2014 at 10:10 AM, Jonathan Goodwin \<  
[jonathanwgoodwin@gmail.com](mailto:jonathanwgoodwin@gmail.com)\> wrote:

> Hello David and David,
> 
> I took a look at the logs / configs posted and mine are mostly similar  
> (though i'm not using any rivers) and I'm having the same issue.  
> I've tested on 0.90.9 and 0.90.7, I hadn't tried the 1.0.0RC yet because  
> the logstash website suggested I stick to 0.90.9  
> If you need any more logs / config samples I'd be happy to provide those.
> 
> Best,  
> JG
> 
> On Friday, January 31, 2014 3:46:07 PM UTC-5, David Montgomery wrote:
> 
> > Hi,
> > 
> > In chef I used -N flag which changes the host name when using  
> > chef-client. I removed the flag and built again. No difference. I have  
> > two nodes running. Both have the name cluster name, ports are 100% wide  
> > open...and wow..ES cant talk despite both running in the same region.
> > 
> > So...ES...any suggestions?
> > 
> > root@ip-10-238-131-236:/var/log/elasticsearch# hostname  
> > ip-10-238-131-236
> > 
> > root@ip-10-238-131-236:/var/log/elasticsearch# curl -XGET '  
> > [http://127.0.0.1:9200/\_cluster/health?pretty=true](http://127.0.0.1:9200/_cluster/health?pretty=true)'  
> > {  
> > "cluster\_name" : "mizilaelasticsearch",  
> > "status" : "green",  
> > "timed\_out" : false,  
> > "number\_of\_nodes" : 1,  
> > "number\_of\_data\_nodes" : 1,  
> > "active\_primary\_shards" : 0,  
> > "active\_shards" : 0,  
> > "relocating\_shards" : 0,  
> > "initializing\_shards" : 0,  
> > "unassigned\_shards" : 0  
> > }
> > 
> > On Fri, Jan 31, 2014 at 12:20 AM, Ivan Brusic [iv...@brusic.com](mailto:iv...@brusic.com) wrote:
> > 
> > > Did you override your network.host configuration parameter by any chance?
> > > 
> > > --  
> > > Ivan
> > > 
> > > On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com)wrote:
> > > 
> > > > Hi,
> > > > 
> > > > Details
> > > > 
> > > > 1. both servers are sing the same sec group  
> > > > 2 all ports between 9200 and 9300 are open 0.0.0.0/0
> > > > 2. ec2 instacances in us-east region
> > > > 3. Did a fresh boot on 2 servers both servers are running. Both are  
> > > > not talking
> > > > 4. Attached are the logs for both servers and the common  
> > > > elasticsearch.yml file
> > > > 5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with  
> > > > elasticsearch-cloud-aws/2.0.0.RC1  
> > > > /usr/share/elasticsearch/plugins/cloud-aws  
> > > > ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls  
> > > > aws-java-sdk-1.3.32.jar commons-codec-1.4.jar  
> > > > commons-logging-1.1.1.jar elasticsearch-cloud-aws-2.0.0.RC1.jar  
> > > > httpclient-4.1.1.jar httpcore-4.1.jar
> > > > 
> > > > data\_bag("my\_data\_bag")  
> > > > db = data\_bag\_item("my\_data\_bag", "my")  
> > > > AWS\_ACCESS\_KEY\_ID = db[node.chef\_environment]['  
> > > > aws']['AWS\_ACCESS\_KEY\_ID']  
> > > > AWS\_SECRET\_ACCESS\_KEY = db[node.chef\_environment]['  
> > > > aws']['AWS\_SECRET\_ACCESS\_KEY']
> > > > 
> > > > version = '1.0.0.RC1'  
> > > > remote\_file "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb"  
> > > > do  
> > > > source "[https://download.elasticsearch.org/](https://download.elasticsearch.org/)  
> > > > elasticsearch/elasticsearch/elasticsearch-#{version}.deb"  
> > > > action :create\_if\_missing  
> > > > end
> > > > 
> > > > dpkg\_package "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb"  
> > > > do  
> > > > action :install  
> > > > end  
> > > > bash "add\_aws" do  
> > > > cwd "/usr/share/elasticsearch"  
> > > > code \<\<-EOH  
> > > > git clone [https://github.com/elasticsearch/elasticsearch-](https://github.com/elasticsearch/elasticsearch-)  
> > > > cloud-aws.git  
> > > > /usr/share/elasticsearch/bin/plugin -install  
> > > > elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1  
> > > > EOH  
> > > > not\_if {File.exists?("/usr/share/elasticsearch/elasticsearch-  
> > > > cloud-aws")}  
> > > > end
> > > > 
> > > > service "elasticsearch" do  
> > > > supports :restart =\> true, :start =\> true, :stop =\> true  
> > > > action [:enable, :start]  
> > > > end
> > > > 
> > > > template "/etc/elasticsearch/logging.yml" do  
> > > > path "/etc/elasticsearch/logging.yml"  
> > > > source "logging.yml.erb"  
> > > > owner "root"  
> > > > group "root"  
> > > > mode "0755"  
> > > > notifies :restart, resources(:service =\> "elasticsearch")  
> > > > end
> > > > 
> > > > template "/etc/elasticsearch/elasticsearch.yml" do  
> > > > path "/etc/elasticsearch/elasticsearch.yml"  
> > > > source "elasticsearch.yml.erb"  
> > > > owner "root"  
> > > > group "root"  
> > > > mode "0755"  
> > > > variables :AWS\_ACCESS\_KEY\_ID =\> "#{AWS\_ACCESS\_KEY\_ID}",  
> > > > :AWS\_SECRET\_ACCESS\_KEY =\> "#{AWS\_SECRET\_ACCESS\_KEY}", :region =\> "us-east-1"  
> > > > notifies :restart, resources(:service =\> "elasticsearch")  
> > > > end
> > > > 
> > > > On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery \<[davidmo...@gmail.com](mailto:davidmo...@gmail.com)
> > > > 
> > > > > wrote:
> > > > 
> > > > > sure..let me the logs together and will post two files ..one log file  
> > > > > for each of the servers.
> > > > > 
> > > > > Thanks
> > > > > 
> > > > > On Tue, Jan 28, 2014 at 6:25 AM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote:
> > > > > 
> > > > > > Is it a known problem? Not yet. That's the reason I'm asking for  
> > > > > > logs. I would like to understand what is happening here. So full logs on  
> > > > > > both nodes would help.
> > > > > > 
> > > > > > The way you set unicast is fine to me. But please, could you share  
> > > > > > with me (even through Direct mail) your elasticsearch.yml file and your  
> > > > > > logs in TRACE level?  
> > > > > > You can replace your credentials settings with XXXXXXXX. Please don't  
> > > > > > change anything else. I'd like to reproduce your case.
> > > > > > 
> > > > > > Thanks!
> > > > > > 
> > > > > > --  
> > > > > > David 😉  
> > > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > > > 
> > > > > > Le 27 janv. 2014 à 22:57, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a  
> > > > > > écrit :
> > > > > > 
> > > > > > I have to say..it this a know problem?
> > > > > > 
> > > > > > I removed the keys.
> > > > > > 
> > > > > > So.. should the servers still cluster? Well....its not.........again  
> > > > > > given that the two machine can talk to each other via telent, in the same  
> > > > > > region, same sec group restarted services etc....no go......no cluster
> > > > > > 
> > > > > > So....how do I manually configure nodes? I have given up on auto  
> > > > > > discover. Clearly does now work for me.
> > > > > > 
> > > > > > Is the below an example?
> > > > > > 
> > > > > > discovery.zen.ping.multicast.enabled: false  
> > > > > > discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com](http://1.test.com)  
> > > > > > :9200"]
> > > > > > 
> > > > > > Thanks
> > > > > > 
> > > > > > On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:
> > > > > > 
> > > > > > > Yes. Could you gist it (and remove first keys / secrets of course)?
> > > > > > > 
> > > > > > > --  
> > > > > > > David 😉  
> > > > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > > > > 
> > > > > > > Le 27 janv. 2014 à 20:53, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a  
> > > > > > > écrit :
> > > > > > > 
> > > > > > > I assume that means this in the logging.yml fike?
> > > > > > > 
> > > > > > > # discovery
> > > > > > > 
> > > > > > > discovery: TRACE
> > > > > > > 
> > > > > > > I do have it on...what should I be looking for in the logs?
> > > > > > > 
> > > > > > > On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery  
> > > > > > > wrote:
> > > > > > > 
> > > > > > > > Hi,
> > > > > > > > 
> > > > > > > > As an fyi..I can telnet into the other machine. Its only ES that  
> > > > > > > > does not work despite following the online docs.
> > > > > > > > 
> > > > > > > > If ES aws auto discovery does not work l assuming assume that  
> > > > > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/referenc)  
> > > > > > > > e/current/modules-discovery-zen.html will work?
> > > > > > > > 
> > > > > > > > Thanks
> > > > > > > > 
> > > > > > > > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > > > > > > > 
> > > > > > > > > Hi David,
> > > > > > > > > 
> > > > > > > > > I think you should have nodes running under the same security  
> > > > > > > > > group. In that case, you don't have to open 9300-9400 ports to public.  
> > > > > > > > > If they don't belong to the same group or if you want to reach  
> > > > > > > > > them from outside ec2 platform (public IP), then you need to set host\_type  
> > > > > > > > > to public\_ip.
> > > > > > > > > 
> > > > > > > > > It sounds like your nodes are trying to connect with private ip  
> > > > > > > > > here (which is default).
> > > > > > > > > 
> > > > > > > > > My 2 cents
> > > > > > > > > 
> > > > > > > > > --  
> > > > > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> > > > > > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_  
> > > > > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > > > > > > > 
> > > > > > > > > Le 27 janvier 2014 at 18:07:48, David Montgomery (  
> > > > > > > > > [davidmo...@gmail.com](mailto:davidmo...@gmail.com)) a écrit:
> > > > > > > > > 
> > > > > > > > > Hi,
> > > > > > > > > 
> > > > > > > > > I have two nodes runnging on ec2.
> > > > > > > > > 
> > > > > > > > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > > > > > > > {  
> > > > > > > > > "cluster\_name" : "12345elasticsearch",  
> > > > > > > > > "status" : "green",  
> > > > > > > > > "timed\_out" : false,  
> > > > > > > > > "number\_of\_nodes" : 1,  
> > > > > > > > > "number\_of\_data\_nodes" : 1,  
> > > > > > > > > "active\_primary\_shards" : 0,  
> > > > > > > > > "active\_shards" : 0,  
> > > > > > > > > "relocating\_shards" : 0,  
> > > > > > > > > "initializing\_shards" : 0,  
> > > > > > > > > "unassigned\_shards" : 0  
> > > > > > > > > }
> > > > > > > > > 
> > > > > > > > > So..its fair to say that ec2 clustering did not work given the  
> > > > > > > > > below config. Yes...the aws keys are correct and I have port 9200-9400  
> > > > > > > > > open. What elasticsearch advertiseres is that all that is needed.
> > > > > > > > > 
> > > > > > > > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on  
> > > > > > > > > ubuntu 12.04
> > > > > > > > > 
> > > > > > > > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > > > > > > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > > > > > > > discovery.type: ec2
> > > > > > > > > 
> > > > > > > > > In the logs I see the below:
> > > > > > > > > 
> > > > > > > > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > > > > > > > [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-  
> > > > > > > > > elasticsearch-east-development-20140127160434][inet[/10.211.  
> > > > > > > > > 29.210:9300]]  
> > > > > > > > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > > > > > > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > > connectToChannelsLight(NettyTransport.java:676)  
> > > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > > connectToNode(NettyTransport.java:636)  
> > > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > > connectToNodeLight(NettyTransport.java:603)  
> > > > > > > > > at org.elasticsearch.transport.TransportService.  
> > > > > > > > > connectToNodeLight(TransportService.java:133)  
> > > > > > > > > at org.elasticsearch.discovery.zen.ping.unicast.  
> > > > > > > > > UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > > > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > > > > > > ThreadPoolExecutor.java:1146)  
> > > > > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > > > > > ThreadPoolExecutor.java:615)  
> > > > > > > > > at java.lang.Thread.run(Thread.java:701)  
> > > > > > > > > Caused by: org.elasticsearch.common.netty.channel.  
> > > > > > > > > ConnectTimeoutException: connection timed out: /10.239.36.98:9300  
> > > > > > > > > at org.elasticsearch.common.netty.channel.socket.nio.  
> > > > > > > > > NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > > > > > > > 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
> > > > > > > > > 
> > > > > > > > > Thanks
> > > > > > > > > 
> > > > > > > > > --  
> > > > > > > > > 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/ec028f53-c6b](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b)  
> > > > > > > > > 2-48e1-b714-a6f1ac7ae1cd%[40googlegroups.com](http://40googlegroups.com).  
> > > > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > > > > 
> > > > > > > > > --  
> > > > > > > > > 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/4d1c068a-3e9](https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9)  
> > > > > > > > > c-4731-84e2-62eeeb63fa81%[40googlegroups.com](http://40googlegroups.com).  
> > > > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > 
> > > > > > --  
> > > > > > 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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%  
> > > > > > [40googlegroups.com](http://40googlegroups.com).  
> > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > 
> > > > > > --  
> > > > > > You received this message because you are subscribed to a topic in  
> > > > > > the Google Groups "elasticsearch" group.  
> > > > > > To unsubscribe from this topic, visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > > > > topic/elasticsearch/PDDOu42M9Mc/unsubscribe.  
> > > > > > To unsubscribe from this group and all its topics, 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/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%[40pilato.fr](http://40pilato.fr).
> > > > > > 
> > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > 
> > > > --  
> > > > 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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%  
> > > > 2B7WDJrbgjPWJBV2ijFQ%[40mail.gmail.com](http://40mail.gmail.com).
> > > > 
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > You received this message because you are subscribed to a topic in the  
> > > Google Groups "elasticsearch" group.  
> > > To unsubscribe from this topic, visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > topic/elasticsearch/PDDOu42M9Mc/unsubscribe.  
> > > To unsubscribe from this group and all its topics, 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/CALY%3DcQDHsDjF0AGUAoC3rLz\_  
> > > y5eGvFPtDEooRj0xP87mRjxurg%[40mail.gmail.com](http://40mail.gmail.com).
> > > 
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to a topic in the  
> > Google Groups "elasticsearch" group.  
> > To unsubscribe from this topic, visit  
> > [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe).  
> > To unsubscribe from this group and all its topics, 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/a48fe555-0b95-4281-ba9e-351b21f4a9e9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a48fe555-0b95-4281-ba9e-351b21f4a9e9%40googlegroups.com)  
> > .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACF%2B8rqhd%2BRx7Ku41iGukxYFD%2B-xoPvMyFW-%2Bw%3DLdQuzDTctJA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rqhd%2BRx7Ku41iGukxYFD%2B-xoPvMyFW-%2Bw%3DLdQuzDTctJA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [February 4, 2014, 12:26am UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/17 "2014-02-04T00:26:51Z")

</div>

Just tried 0.90.11. Same issue. I have two running nodes on ec2..and  
wow...they cant talk.

On Tue, Feb 4, 2014 at 6:51 AM, David Montgomery  
[davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)wrote:

> Hi Jonathan
> 
> Just be clear...you could not cluster? I wili try the lastest stable  
> release cuase I am giving up on 1.0.0RC.
> 
> Thanks
> 
> On Sun, Feb 2, 2014 at 10:10 AM, Jonathan Goodwin \<  
> [jonathanwgoodwin@gmail.com](mailto:jonathanwgoodwin@gmail.com)\> wrote:
> 
> > Hello David and David,
> > 
> > I took a look at the logs / configs posted and mine are mostly similar  
> > (though i'm not using any rivers) and I'm having the same issue.  
> > I've tested on 0.90.9 and 0.90.7, I hadn't tried the 1.0.0RC yet because  
> > the logstash website suggested I stick to 0.90.9  
> > If you need any more logs / config samples I'd be happy to provide those.
> > 
> > Best,  
> > JG
> > 
> > On Friday, January 31, 2014 3:46:07 PM UTC-5, David Montgomery wrote:
> > 
> > > Hi,
> > > 
> > > In chef I used -N flag which changes the host name when using  
> > > chef-client. I removed the flag and built again. No difference. I have  
> > > two nodes running. Both have the name cluster name, ports are 100% wide  
> > > open...and wow..ES cant talk despite both running in the same region.
> > > 
> > > So...ES...any suggestions?
> > > 
> > > root@ip-10-238-131-236:/var/log/elasticsearch# hostname  
> > > ip-10-238-131-236
> > > 
> > > root@ip-10-238-131-236:/var/log/elasticsearch# curl -XGET '  
> > > [http://127.0.0.1:9200/\_cluster/health?pretty=true](http://127.0.0.1:9200/_cluster/health?pretty=true)'  
> > > {  
> > > "cluster\_name" : "mizilaelasticsearch",  
> > > "status" : "green",  
> > > "timed\_out" : false,  
> > > "number\_of\_nodes" : 1,  
> > > "number\_of\_data\_nodes" : 1,  
> > > "active\_primary\_shards" : 0,  
> > > "active\_shards" : 0,  
> > > "relocating\_shards" : 0,  
> > > "initializing\_shards" : 0,  
> > > "unassigned\_shards" : 0  
> > > }
> > > 
> > > On Fri, Jan 31, 2014 at 12:20 AM, Ivan Brusic [iv...@brusic.com](mailto:iv...@brusic.com) wrote:
> > > 
> > > > Did you override your network.host configuration parameter by any  
> > > > chance?
> > > > 
> > > > --  
> > > > Ivan
> > > > 
> > > > On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery \<[davidmo...@gmail.com](mailto:davidmo...@gmail.com)
> > > > 
> > > > > wrote:
> > > > 
> > > > > Hi,
> > > > > 
> > > > > Details
> > > > > 
> > > > > 1. both servers are sing the same sec group  
> > > > > 2 all ports between 9200 and 9300 are open 0.0.0.0/0
> > > > > 2. ec2 instacances in us-east region
> > > > > 3. Did a fresh boot on 2 servers both servers are running. Both are  
> > > > > not talking
> > > > > 4. Attached are the logs for both servers and the common  
> > > > > elasticsearch.yml file
> > > > > 5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with  
> > > > > elasticsearch-cloud-aws/2.0.0.RC1  
> > > > > /usr/share/elasticsearch/plugins/cloud-aws  
> > > > > ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls  
> > > > > aws-java-sdk-1.3.32.jar commons-codec-1.4.jar  
> > > > > commons-logging-1.1.1.jar elasticsearch-cloud-aws-2.0.0.RC1.jar  
> > > > > httpclient-4.1.1.jar httpcore-4.1.jar
> > > > > 
> > > > > data\_bag("my\_data\_bag")  
> > > > > db = data\_bag\_item("my\_data\_bag", "my")  
> > > > > AWS\_ACCESS\_KEY\_ID = db[node.chef\_environment]['  
> > > > > aws']['AWS\_ACCESS\_KEY\_ID']  
> > > > > AWS\_SECRET\_ACCESS\_KEY = db[node.chef\_environment]['  
> > > > > aws']['AWS\_SECRET\_ACCESS\_KEY']
> > > > > 
> > > > > version = '1.0.0.RC1'  
> > > > > remote\_file "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb"  
> > > > > do  
> > > > > source "[https://download.elasticsearch.org/](https://download.elasticsearch.org/)  
> > > > > elasticsearch/elasticsearch/elasticsearch-#{version}.deb"  
> > > > > action :create\_if\_missing  
> > > > > end
> > > > > 
> > > > > dpkg\_package "#{Chef::Config[:file\_cache\_path]}/elasticsearch-#{version}.deb"  
> > > > > do  
> > > > > action :install  
> > > > > end  
> > > > > bash "add\_aws" do  
> > > > > cwd "/usr/share/elasticsearch"  
> > > > > code \<\<-EOH  
> > > > > git clone [https://github.com/elasticsearch/elasticsearch-](https://github.com/elasticsearch/elasticsearch-)  
> > > > > cloud-aws.git  
> > > > > /usr/share/elasticsearch/bin/plugin -install  
> > > > > elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1  
> > > > > EOH  
> > > > > not\_if {File.exists?("/usr/share/elasticsearch/elasticsearch-  
> > > > > cloud-aws")}  
> > > > > end
> > > > > 
> > > > > service "elasticsearch" do  
> > > > > supports :restart =\> true, :start =\> true, :stop =\> true  
> > > > > action [:enable, :start]  
> > > > > end
> > > > > 
> > > > > template "/etc/elasticsearch/logging.yml" do  
> > > > > path "/etc/elasticsearch/logging.yml"  
> > > > > source "logging.yml.erb"  
> > > > > owner "root"  
> > > > > group "root"  
> > > > > mode "0755"  
> > > > > notifies :restart, resources(:service =\> "elasticsearch")  
> > > > > end
> > > > > 
> > > > > template "/etc/elasticsearch/elasticsearch.yml" do  
> > > > > path "/etc/elasticsearch/elasticsearch.yml"  
> > > > > source "elasticsearch.yml.erb"  
> > > > > owner "root"  
> > > > > group "root"  
> > > > > mode "0755"  
> > > > > variables :AWS\_ACCESS\_KEY\_ID =\> "#{AWS\_ACCESS\_KEY\_ID}",  
> > > > > :AWS\_SECRET\_ACCESS\_KEY =\> "#{AWS\_SECRET\_ACCESS\_KEY}", :region =\> "us-east-1"  
> > > > > notifies :restart, resources(:service =\> "elasticsearch")  
> > > > > end
> > > > > 
> > > > > On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery \<  
> > > > > [davidmo...@gmail.com](mailto:davidmo...@gmail.com)\> wrote:
> > > > > 
> > > > > > sure..let me the logs together and will post two files ..one log file  
> > > > > > for each of the servers.
> > > > > > 
> > > > > > Thanks
> > > > > > 
> > > > > > On Tue, Jan 28, 2014 at 6:25 AM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr)wrote:
> > > > > > 
> > > > > > > Is it a known problem? Not yet. That's the reason I'm asking for  
> > > > > > > logs. I would like to understand what is happening here. So full logs on  
> > > > > > > both nodes would help.
> > > > > > > 
> > > > > > > The way you set unicast is fine to me. But please, could you share  
> > > > > > > with me (even through Direct mail) your elasticsearch.yml file and your  
> > > > > > > logs in TRACE level?  
> > > > > > > You can replace your credentials settings with XXXXXXXX. Please  
> > > > > > > don't change anything else. I'd like to reproduce your case.
> > > > > > > 
> > > > > > > Thanks!
> > > > > > > 
> > > > > > > --  
> > > > > > > David 😉  
> > > > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > > > > 
> > > > > > > Le 27 janv. 2014 à 22:57, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com) a  
> > > > > > > écrit :
> > > > > > > 
> > > > > > > I have to say..it this a know problem?
> > > > > > > 
> > > > > > > I removed the keys.
> > > > > > > 
> > > > > > > So.. should the servers still cluster? Well....its  
> > > > > > > not.........again given that the two machine can talk to each other via  
> > > > > > > telent, in the same region, same sec group restarted services etc....no  
> > > > > > > go......no cluster
> > > > > > > 
> > > > > > > So....how do I manually configure nodes? I have given up on auto  
> > > > > > > discover. Clearly does now work for me.
> > > > > > > 
> > > > > > > Is the below an example?
> > > > > > > 
> > > > > > > discovery.zen.ping.multicast.enabled: false  
> > > > > > > discovery.zen.ping.unicast.hosts: ["[0.test.com:9200](http://0.test.com:9200)", "[1.test.com](http://1.test.com)  
> > > > > > > :9200"]
> > > > > > > 
> > > > > > > Thanks
> > > > > > > 
> > > > > > > On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:
> > > > > > > 
> > > > > > > > Yes. Could you gist it (and remove first keys / secrets of course)?
> > > > > > > > 
> > > > > > > > --  
> > > > > > > > David 😉  
> > > > > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > > > > > 
> > > > > > > > Le 27 janv. 2014 à 20:53, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com)  
> > > > > > > > a écrit :
> > > > > > > > 
> > > > > > > > I assume that means this in the logging.yml fike?
> > > > > > > > 
> > > > > > > > # discovery
> > > > > > > > 
> > > > > > > > discovery: TRACE
> > > > > > > > 
> > > > > > > > I do have it on...what should I be looking for in the logs?
> > > > > > > > 
> > > > > > > > On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery  
> > > > > > > > wrote:
> > > > > > > > 
> > > > > > > > > Hi,
> > > > > > > > > 
> > > > > > > > > As an fyi..I can telnet into the other machine. Its only ES that  
> > > > > > > > > does not work despite following the online docs.
> > > > > > > > > 
> > > > > > > > > If ES aws auto discovery does not work l assuming assume that  
> > > > > > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/referenc)  
> > > > > > > > > e/current/modules-discovery-zen.html will work?
> > > > > > > > > 
> > > > > > > > > Thanks
> > > > > > > > > 
> > > > > > > > > On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
> > > > > > > > > 
> > > > > > > > > > Hi David,
> > > > > > > > > > 
> > > > > > > > > > I think you should have nodes running under the same security  
> > > > > > > > > > group. In that case, you don't have to open 9300-9400 ports to public.  
> > > > > > > > > > If they don't belong to the same group or if you want to reach  
> > > > > > > > > > them from outside ec2 platform (public IP), then you need to set host\_type  
> > > > > > > > > > to public\_ip.
> > > > > > > > > > 
> > > > > > > > > > It sounds like your nodes are trying to connect with private ip  
> > > > > > > > > > here (which is default).
> > > > > > > > > > 
> > > > > > > > > > My 2 cents
> > > > > > > > > > 
> > > > > > > > > > --  
> > > > > > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> > > > > > > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_  
> > > > > > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> > > > > > > > > > 
> > > > > > > > > > Le 27 janvier 2014 at 18:07:48, David Montgomery (  
> > > > > > > > > > [davidmo...@gmail.com](mailto:davidmo...@gmail.com)) a écrit:
> > > > > > > > > > 
> > > > > > > > > > Hi,
> > > > > > > > > > 
> > > > > > > > > > I have two nodes runnging on ec2.
> > > > > > > > > > 
> > > > > > > > > > curl -X GET [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
> > > > > > > > > > {  
> > > > > > > > > > "cluster\_name" : "12345elasticsearch",  
> > > > > > > > > > "status" : "green",  
> > > > > > > > > > "timed\_out" : false,  
> > > > > > > > > > "number\_of\_nodes" : 1,  
> > > > > > > > > > "number\_of\_data\_nodes" : 1,  
> > > > > > > > > > "active\_primary\_shards" : 0,  
> > > > > > > > > > "active\_shards" : 0,  
> > > > > > > > > > "relocating\_shards" : 0,  
> > > > > > > > > > "initializing\_shards" : 0,  
> > > > > > > > > > "unassigned\_shards" : 0  
> > > > > > > > > > }
> > > > > > > > > > 
> > > > > > > > > > So..its fair to say that ec2 clustering did not work given the  
> > > > > > > > > > below config. Yes...the aws keys are correct and I have port 9200-9400  
> > > > > > > > > > open. What elasticsearch advertiseres is that all that is needed.
> > > > > > > > > > 
> > > > > > > > > > I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on  
> > > > > > > > > > ubuntu 12.04
> > > > > > > > > > 
> > > > > > > > > > cloud.aws.access\_key: \<%=@AWS\_ACCESS\_KEY\_ID%\>  
> > > > > > > > > > cloud.aws.secret\_key: \<%=@AWS\_SECRET\_ACCESS\_KEY%\>  
> > > > > > > > > > discovery.type: ec2
> > > > > > > > > > 
> > > > > > > > > > In the logs I see the below:
> > > > > > > > > > 
> > > > > > > > > > [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast]  
> > > > > > > > > > [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-  
> > > > > > > > > > elasticsearch-east-development-20140127160434][inet[/10.211.  
> > > > > > > > > > 29.210:9300]]  
> > > > > > > > > > org.elasticsearch.transport.ConnectTransportException: [inet[/  
> > > > > > > > > > 10.211.29.210:9300]] connect\_timeout[30s]  
> > > > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > > > connectToChannelsLight(NettyTransport.java:676)  
> > > > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > > > connectToNode(NettyTransport.java:636)  
> > > > > > > > > > at org.elasticsearch.transport.netty.NettyTransport.  
> > > > > > > > > > connectToNodeLight(NettyTransport.java:603)  
> > > > > > > > > > at org.elasticsearch.transport.TransportService.  
> > > > > > > > > > connectToNodeLight(TransportService.java:133)  
> > > > > > > > > > at org.elasticsearch.discovery.zen.ping.unicast.  
> > > > > > > > > > UnicastZenPing$3.run(UnicastZenPing.java:278)  
> > > > > > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(  
> > > > > > > > > > ThreadPoolExecutor.java:1146)  
> > > > > > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(  
> > > > > > > > > > ThreadPoolExecutor.java:615)  
> > > > > > > > > > at java.lang.Thread.run(Thread.java:701)  
> > > > > > > > > > Caused by: org.elasticsearch.common.netty.channel.  
> > > > > > > > > > ConnectTimeoutException: connection timed out: /10.239.36.98:9300  
> > > > > > > > > > at org.elasticsearch.common.netty.channel.socket.nio.  
> > > > > > > > > > NioClientBoss.processConnectTimeout(NioClientBoss.java:137)  
> > > > > > > > > > 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
> > > > > > > > > > 
> > > > > > > > > > Thanks
> > > > > > > > > > 
> > > > > > > > > > --  
> > > > > > > > > > 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/ec028f53-c6b](https://groups.google.com/d/msgid/elasticsearch/ec028f53-c6b)  
> > > > > > > > > > 2-48e1-b714-a6f1ac7ae1cd%[40googlegroups.com](http://40googlegroups.com).  
> > > > > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > > > > > 
> > > > > > > > > > --  
> > > > > > > > > > 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/4d1c068a-3e9](https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9)  
> > > > > > > > > > c-4731-84e2-62eeeb63fa81%[40googlegroups.com](http://40googlegroups.com).  
> > > > > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > > 
> > > > > > > --  
> > > > > > > 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/2bdefbe0-](https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-)  
> > > > > > > 3ab4-4b85-b473-8b502b812d5b%[40googlegroups.com](http://40googlegroups.com).  
> > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > > > 
> > > > > > > --  
> > > > > > > You received this message because you are subscribed to a topic in  
> > > > > > > the Google Groups "elasticsearch" group.  
> > > > > > > To unsubscribe from this topic, visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > > > > > topic/elasticsearch/PDDOu42M9Mc/unsubscribe.  
> > > > > > > To unsubscribe from this group and all its topics, 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/2804A7F6-](https://groups.google.com/d/msgid/elasticsearch/2804A7F6-)  
> > > > > > > B2B8-4C23-B273-B7B7E0F805E0%[40pilato.fr](http://40pilato.fr).
> > > > > > > 
> > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > > 
> > > > > --  
> > > > > 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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%  
> > > > > 2B7WDJrbgjPWJBV2ijFQ%[40mail.gmail.com](http://40mail.gmail.com).
> > > > > 
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to a topic in the  
> > > > Google Groups "elasticsearch" group.  
> > > > To unsubscribe from this topic, visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > > topic/elasticsearch/PDDOu42M9Mc/unsubscribe.  
> > > > To unsubscribe from this group and all its topics, 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/CALY%3DcQDHsDjF0AGUAoC3rLz\_  
> > > > y5eGvFPtDEooRj0xP87mRjxurg%[40mail.gmail.com](http://40mail.gmail.com).
> > > > 
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > You received this message because you are subscribed to a topic in the  
> > > Google Groups "elasticsearch" group.  
> > > To unsubscribe from this topic, visit  
> > > [https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe).  
> > > To unsubscribe from this group and all its topics, 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/a48fe555-0b95-4281-ba9e-351b21f4a9e9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a48fe555-0b95-4281-ba9e-351b21f4a9e9%40googlegroups.com)  
> > > .
> > 
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACF%2B8ro6cwQ1pw6nbMo3ciX85q7Gen5s%2BS%2B1THuebiM130dihQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8ro6cwQ1pw6nbMo3ciX85q7Gen5s%2BS%2B1THuebiM130dihQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 1:52am UTC](https://discuss.elastic.co/t/cant-create-cluster-on-ec2/15434/18 "2017-07-06T01:52:57Z")

</div>