Issue setting up ES on AWS: No route to host

Chris_Carpenter · June 27, 2013, 3:41pm

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu
13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn]
loaded [cloud-aws], sites []
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
{inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn]
exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn]
waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn]
SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address
{inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn]
new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]],
reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn]
recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 6:01pm

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcarpenter@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites []
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Chris_Carpenter · June 27, 2013, 6:07pm

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter <cdcar...@gmail.com <javascript:>>
a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu
13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn]
loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn]
exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn]
waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn]
SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn]
new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]],
reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn]
recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 6:38pm

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcarpenter@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 6:58pm

Forgot to say: just hide values for access and secret

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

Le 27 juin 2013 à 20:38, David Pilato david@pilato.fr a écrit :

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcarpenter@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Chris_Carpenter · June 27, 2013, 6:59pm

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter <cdcar...@gmail.com <javascript:>>
a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu
13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn]
loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn]
exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn]
waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn]
SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn]
new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]],
reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn]
recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn]
{0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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.
For more options, visit 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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 7:16pm

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcarpenter@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Chris_Carpenter · June 27, 2013, 7:19pm

Both formats are correct as per yaml standard. I tried it as you
suggest(and the guide I was following did) and changed to as it is
presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter <cdcar...@gmail.com <javascript:>>
a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu
13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara
Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara
Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing
connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara
Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara
Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara
Rahn] new_master [Tamara
Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason:
zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara
Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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.
For more options, visit 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.
For more options, visit 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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 7:37pm

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcarpenter@gmail.com a écrit :

Both formats are correct as per yaml standard. I tried it as you suggest(and the guide I was following did) and changed to as it is presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Chris_Carpenter · June 27, 2013, 8:11pm

I have created another gist: https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery and
aws on trace.
The second I added because discovery adds a lot of log messages and thought
just having aws on trace would be helpful. So aws.log is just with aws on
trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter <cdcar...@gmail.com <javascript:>>
a écrit :

Both formats are correct as per yaml standard. I tried it as you
suggest(and the guide I was following did) and changed to as it is
presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu
13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara
Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara
Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing
connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara
Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara
Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara
Rahn] new_master [Tamara
Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason:
zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara
Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 8:18pm

Could you double check your security group?
And check that all instances have 9300 ports opened?
Did you open 9200 ports as well?

If so, running curl http://privateipofanothernode:9200/ should give you results.

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

Le 27 juin 2013 à 22:11, Chris Carpenter cdcarpenter@gmail.com a écrit :

I have created another gist: https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery and aws on trace.
The second I added because discovery adds a lot of log messages and thought just having aws on trace would be helpful. So aws.log is just with aws on trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcar...@gmail.com a écrit :

Both formats are correct as per yaml standard. I tried it as you suggest(and the guide I was following did) and changed to as it is presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Chris_Carpenter · June 27, 2013, 8:30pm

That was my thought too after looking at the logs, and double checked the
settings. I did another check when you suggested and used your recommended
method of double checking. I am able to get results from 9200 from another
ubunto box in a different security group. The elasticsearch node is in a
test security group that is completely open. When I am working on new
things I use it to eliminate potential issues with security groups that
would throw me off.

On Thursday, June 27, 2013 3:18:08 PM UTC-5, David Pilato wrote:

Could you double check your security group?
And check that all instances have 9300 ports opened?
Did you open 9200 ports as well?

If so, running curl http://privateipofanothernode:9200/ should give you
results.

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

Le 27 juin 2013 à 22:11, Chris Carpenter <cdcar...@gmail.com <javascript:>>
a écrit :

I have created another gist:
https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery and
aws on trace.
The second I added because discovery adds a lot of log messages and
thought just having aws on trace would be helpful. So aws.log is just with
aws on trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcar...@gmail.com a écrit :

Both formats are correct as per yaml standard. I tried it as you
suggest(and the guide I was following did) and changed to as it is
presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a
écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using
Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara
Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara
Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing
connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara
Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara
Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara
Rahn] new_master [Tamara
Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason:
zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara
Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 9:06pm

Do you have Elasticsearch running on all these nodes?
It seems that you have a huge number of nodes here.

Could you start your tests on a smaller number of nodes?
Also, just for testing purpose, disable ec2 cloud plugin and use unicast, specifying private IP of other nodes and see if your connection works.
If not, that will mean that your network settings are not good.
If it works, it should mean that there is something strange with the ec2 plugin.

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

Le 27 juin 2013 à 22:30, Chris Carpenter cdcarpenter@gmail.com a écrit :

That was my thought too after looking at the logs, and double checked the settings. I did another check when you suggested and used your recommended method of double checking. I am able to get results from 9200 from another ubunto box in a different security group. The elasticsearch node is in a test security group that is completely open. When I am working on new things I use it to eliminate potential issues with security groups that would throw me off.

On Thursday, June 27, 2013 3:18:08 PM UTC-5, David Pilato wrote:

Could you double check your security group?
And check that all instances have 9300 ports opened?
Did you open 9200 ports as well?

If so, running curl http://privateipofanothernode:9200/ should give you results.

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

Le 27 juin 2013 à 22:11, Chris Carpenter cdcar...@gmail.com a écrit :

I have created another gist: https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery and aws on trace.
The second I added because discovery adds a lot of log messages and thought just having aws on trace would be helpful. So aws.log is just with aws on trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcar...@gmail.com a écrit :

Both formats are correct as per yaml standard. I tried it as you suggest(and the guide I was following did) and changed to as it is presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Chris_Carpenter · June 27, 2013, 9:27pm

Only two instances are running elasticsearch right now. One is a graylog2
server attached to our dev environment, and the other is the elasticsearch
node I am working on.

I did not get the error when I setup the server with unicast using
127.0.0.1 for the host.

I have created a gist with two log files from the unicast configuration.
https://gist.github.com/chris-carpenter/5880534

The config is:

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]

On Thursday, June 27, 2013 4:06:29 PM UTC-5, David Pilato wrote:

Do you have Elasticsearch running on all these nodes?
It seems that you have a huge number of nodes here.

Could you start your tests on a smaller number of nodes?
Also, just for testing purpose, disable ec2 cloud plugin and use unicast,
specifying private IP of other nodes and see if your connection works.
If not, that will mean that your network settings are not good.
If it works, it should mean that there is something strange with the ec2
plugin.

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

Le 27 juin 2013 à 22:30, Chris Carpenter <cdcar...@gmail.com <javascript:>>
a écrit :

That was my thought too after looking at the logs, and double checked the
settings. I did another check when you suggested and used your recommended
method of double checking. I am able to get results from 9200 from another
ubunto box in a different security group. The elasticsearch node is in a
test security group that is completely open. When I am working on new
things I use it to eliminate potential issues with security groups that
would throw me off.

On Thursday, June 27, 2013 3:18:08 PM UTC-5, David Pilato wrote:

Could you double check your security group?
And check that all instances have 9300 ports opened?
Did you open 9200 ports as well?

If so, running curl http://privateipofanothernode:9200/ should give you
results.

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

Le 27 juin 2013 à 22:11, Chris Carpenter cdcar...@gmail.com a écrit :

I have created another gist:
https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery and
aws on trace.
The second I added because discovery adds a lot of log messages and
thought just having aws on trace would be helpful. So aws.log is just with
aws on trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcar...@gmail.com a écrit :

Both formats are correct as per yaml standard. I tried it as you
suggest(and the guide I was following did) and changed to as it is
presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a
écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a
écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using
Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara
Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara
Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing
connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara
Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara
Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara
Rahn] new_master [Tamara
Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason:
zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara
Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 9:31pm

I was not saying to use unicast on localhost but using private IP address of the other node (where es is running).
I suggest also that you add tags on your ES nodes and filter nodes by tag when using ec2 plugin. That way, only nodes with ES will try to speak to each other.

Read doc here: GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch

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

Le 27 juin 2013 à 23:27, Chris Carpenter cdcarpenter@gmail.com a écrit :

Only two instances are running elasticsearch right now. One is a graylog2 server attached to our dev environment, and the other is the elasticsearch node I am working on.

I did not get the error when I setup the server with unicast using 127.0.0.1 for the host.

I have created a gist with two log files from the unicast configuration. https://gist.github.com/chris-carpenter/5880534

The config is:

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]

On Thursday, June 27, 2013 4:06:29 PM UTC-5, David Pilato wrote:

Do you have Elasticsearch running on all these nodes?
It seems that you have a huge number of nodes here.

Could you start your tests on a smaller number of nodes?
Also, just for testing purpose, disable ec2 cloud plugin and use unicast, specifying private IP of other nodes and see if your connection works.
If not, that will mean that your network settings are not good.
If it works, it should mean that there is something strange with the ec2 plugin.

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

Le 27 juin 2013 à 22:30, Chris Carpenter cdcar...@gmail.com a écrit :

That was my thought too after looking at the logs, and double checked the settings. I did another check when you suggested and used your recommended method of double checking. I am able to get results from 9200 from another ubunto box in a different security group. The elasticsearch node is in a test security group that is completely open. When I am working on new things I use it to eliminate potential issues with security groups that would throw me off.

On Thursday, June 27, 2013 3:18:08 PM UTC-5, David Pilato wrote:

Could you double check your security group?
And check that all instances have 9300 ports opened?
Did you open 9200 ports as well?

If so, running curl http://privateipofanothernode:9200/ should give you results.

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

Le 27 juin 2013 à 22:11, Chris Carpenter cdcar...@gmail.com a écrit :

I have created another gist: https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery and aws on trace.
The second I added because discovery adds a lot of log messages and thought just having aws on trace would be helpful. So aws.log is just with aws on trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcar...@gmail.com a écrit :

Both formats are correct as per yaml standard. I tried it as you suggest(and the guide I was following did) and changed to as it is presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Chris_Carpenter · June 27, 2013, 9:40pm

I have changed the unicast setup to use the private ip of the instance. It
worked just like when using the home ip. I was also able to access it from
another box with the unicast setup.

On Thursday, June 27, 2013 4:31:43 PM UTC-5, David Pilato wrote:

I was not saying to use unicast on localhost but using private IP address
of the other node (where es is running).
I suggest also that you add tags on your ES nodes and filter nodes by tag
when using ec2 plugin. That way, only nodes with ES will try to speak to
each other.

Read doc here: GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch

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

Le 27 juin 2013 à 23:27, Chris Carpenter <cdcar...@gmail.com <javascript:>>
a écrit :

Only two instances are running elasticsearch right now. One is a graylog2
server attached to our dev environment, and the other is the elasticsearch
node I am working on.

I did not get the error when I setup the server with unicast using
127.0.0.1 for the host.

I have created a gist with two log files from the unicast configuration.
https://gist.github.com/chris-carpenter/5880534

The config is:

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]

On Thursday, June 27, 2013 4:06:29 PM UTC-5, David Pilato wrote:

Do you have Elasticsearch running on all these nodes?
It seems that you have a huge number of nodes here.

Could you start your tests on a smaller number of nodes?
Also, just for testing purpose, disable ec2 cloud plugin and use unicast,
specifying private IP of other nodes and see if your connection works.
If not, that will mean that your network settings are not good.
If it works, it should mean that there is something strange with the ec2
plugin.

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

Le 27 juin 2013 à 22:30, Chris Carpenter cdcar...@gmail.com a écrit :

That was my thought too after looking at the logs, and double checked the
settings. I did another check when you suggested and used your recommended
method of double checking. I am able to get results from 9200 from another
ubunto box in a different security group. The elasticsearch node is in a
test security group that is completely open. When I am working on new
things I use it to eliminate potential issues with security groups that
would throw me off.

On Thursday, June 27, 2013 3:18:08 PM UTC-5, David Pilato wrote:

Could you double check your security group?
And check that all instances have 9300 ports opened?
Did you open 9200 ports as well?

If so, running curl http://privateipofanothernode:9200/ should give you
results.

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

Le 27 juin 2013 à 22:11, Chris Carpenter cdcar...@gmail.com a écrit :

I have created another gist:
https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery and
aws on trace.
The second I added because discovery adds a lot of log messages and
thought just having aws on trace would be helpful. So aws.log is just with
aws on trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcar...@gmail.com a écrit :

Both formats are correct as per yaml standard. I tried it as you
suggest(and the guide I was following did) and changed to as it is
presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a
écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a
écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a
écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using
Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara
Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara
Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing
connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara
Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara
Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara
Rahn] new_master [Tamara
Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason:
zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara
Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ]
[Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · June 27, 2013, 9:49pm

So now, try to filter nodes with a tag.

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

Le 27 juin 2013 à 23:40, Chris Carpenter cdcarpenter@gmail.com a écrit :

I have changed the unicast setup to use the private ip of the instance. It worked just like when using the home ip. I was also able to access it from another box with the unicast setup.

On Thursday, June 27, 2013 4:31:43 PM UTC-5, David Pilato wrote:

I was not saying to use unicast on localhost but using private IP address of the other node (where es is running).
I suggest also that you add tags on your ES nodes and filter nodes by tag when using ec2 plugin. That way, only nodes with ES will try to speak to each other.

Read doc here: GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch

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

Le 27 juin 2013 à 23:27, Chris Carpenter cdcar...@gmail.com a écrit :

Only two instances are running elasticsearch right now. One is a graylog2 server attached to our dev environment, and the other is the elasticsearch node I am working on.

I did not get the error when I setup the server with unicast using 127.0.0.1 for the host.

I have created a gist with two log files from the unicast configuration. https://gist.github.com/chris-carpenter/5880534

The config is:

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]

On Thursday, June 27, 2013 4:06:29 PM UTC-5, David Pilato wrote:

Do you have Elasticsearch running on all these nodes?
It seems that you have a huge number of nodes here.

Could you start your tests on a smaller number of nodes?
Also, just for testing purpose, disable ec2 cloud plugin and use unicast, specifying private IP of other nodes and see if your connection works.
If not, that will mean that your network settings are not good.
If it works, it should mean that there is something strange with the ec2 plugin.

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

Le 27 juin 2013 à 22:30, Chris Carpenter cdcar...@gmail.com a écrit :

That was my thought too after looking at the logs, and double checked the settings. I did another check when you suggested and used your recommended method of double checking. I am able to get results from 9200 from another ubunto box in a different security group. The elasticsearch node is in a test security group that is completely open. When I am working on new things I use it to eliminate potential issues with security groups that would throw me off.

On Thursday, June 27, 2013 3:18:08 PM UTC-5, David Pilato wrote:

Could you double check your security group?
And check that all instances have 9300 ports opened?
Did you open 9200 ports as well?

If so, running curl http://privateipofanothernode:9200/ should give you results.

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

Le 27 juin 2013 à 22:11, Chris Carpenter cdcar...@gmail.com a écrit :

I have created another gist: https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery and aws on trace.
The second I added because discovery adds a lot of log messages and thought just having aws on trace would be helpful. So aws.log is just with aws on trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcar...@gmail.com a écrit :

Both formats are correct as per yaml standard. I tried it as you suggest(and the guide I was following did) and changed to as it is presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara Rahn] new_master [Tamara Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason: zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Chris_Carpenter · June 27, 2013, 9:52pm

Thank you for pointing out the tag filter, I hadn't gotten to the point in
the walkthrough where it explained how to do that yet. I reinstalled the
cloud-aws plugin and added the tag filtering, and the error message bout
"No path to host" has gone away. Still not entirely certain of the exact
cause, but at least know I can continue with my spike.

Thank you for your patience and assistance I greatly appreciate it.

On Thursday, June 27, 2013 4:40:20 PM UTC-5, Chris Carpenter wrote:

I have changed the unicast setup to use the private ip of the instance. It
worked just like when using the home ip. I was also able to access it from
another box with the unicast setup.

On Thursday, June 27, 2013 4:31:43 PM UTC-5, David Pilato wrote:

I was not saying to use unicast on localhost but using private IP address
of the other node (where es is running).
I suggest also that you add tags on your ES nodes and filter nodes by tag
when using ec2 plugin. That way, only nodes with ES will try to speak to
each other.

Read doc here: GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch

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

Le 27 juin 2013 à 23:27, Chris Carpenter cdcar...@gmail.com a écrit :

Only two instances are running elasticsearch right now. One is a graylog2
server attached to our dev environment, and the other is the elasticsearch
node I am working on.

I did not get the error when I setup the server with unicast using
127.0.0.1 for the host.

I have created a gist with two log files from the unicast configuration.
https://gist.github.com/chris-carpenter/5880534

The config is:

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]

On Thursday, June 27, 2013 4:06:29 PM UTC-5, David Pilato wrote:

Do you have Elasticsearch running on all these nodes?
It seems that you have a huge number of nodes here.

Could you start your tests on a smaller number of nodes?
Also, just for testing purpose, disable ec2 cloud plugin and use
unicast, specifying private IP of other nodes and see if your connection
works.
If not, that will mean that your network settings are not good.
If it works, it should mean that there is something strange with the ec2
plugin.

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

Le 27 juin 2013 à 22:30, Chris Carpenter cdcar...@gmail.com a écrit :

That was my thought too after looking at the logs, and double checked
the settings. I did another check when you suggested and used your
recommended method of double checking. I am able to get results from 9200
from another ubunto box in a different security group. The elasticsearch
node is in a test security group that is completely open. When I am working
on new things I use it to eliminate potential issues with security groups
that would throw me off.

On Thursday, June 27, 2013 3:18:08 PM UTC-5, David Pilato wrote:

Could you double check your security group?
And check that all instances have 9300 ports opened?
Did you open 9200 ports as well?

If so, running curl http://privateipofanothernode:9200/ should give
you results.

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

Le 27 juin 2013 à 22:11, Chris Carpenter cdcar...@gmail.com a écrit :

I have created another gist:
https://gist.github.com/chris-carpenter/5879939

This has two log files the first discoveryAws.log has both discovery
and aws on trace.
The second I added because discovery adds a lot of log messages and
thought just having aws on trace would be helpful. So aws.log is just with
aws on trace.

Thank you for the help,
Chris

On Thursday, June 27, 2013 2:37:07 PM UTC-5, David Pilato wrote:

Could you change log level for cloud to TRACE?

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

Le 27 juin 2013 à 21:19, Chris Carpenter cdcar...@gmail.com a
écrit :

Both formats are correct as per yaml standard. I tried it as you
suggest(and the guide I was following did) and changed to as it is
presently out of desperation. Both formats had the same behavior.

On Thursday, June 27, 2013 2:16:21 PM UTC-5, David Pilato wrote:

I added a comment there.

Not sure it helps.

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

Le 27 juin 2013 à 20:59, Chris Carpenter cdcar...@gmail.com a
écrit :

https://gist.github.com/chris-carpenter/5879328

On Thursday, June 27, 2013 1:38:51 PM UTC-5, David Pilato wrote:

Yeah but i want to see the original file. Not an extract.
Could you gist it?

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

Le 27 juin 2013 à 20:07, Chris Carpenter cdcar...@gmail.com a
écrit :

Sorry if I wasn't clear this is the contents of my elasticsearch.yml

cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

On Thursday, June 27, 2013 1:01:56 PM UTC-5, David Pilato wrote:

Could you share your config file?
Are you using elasticsearch.yml?

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

Le 27 juin 2013 à 17:41, Chris Carpenter cdcar...@gmail.com a
écrit :

I am trying to setup a Elasticsearch instance in AWS. I am using
Ubuntu 13.04, Elasticsearch 0.90.2, and cloud-aws 1.12.0.

My config:
cluster.name: SometaroLoggin
path.conf: /opt/elasticsearch/config
path.data: /media/data/elasticsearch/data
path.work: /media/data/elasticsearch/work
path.logs: /media/logs/elasticsearch/logs
path.plugins: /opt/elasticsearch/plugins
bootstrap.mlockall: true
discovery.type: ec2
cloud.aws.access_key: -----
cloud.aws.secret_key: -----
cloud.aws.region: ap-northeast

My console output:
[2013-06-27 15:33:30,516][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initializing ...
[2013-06-27 15:33:30,536][INFO ][plugins ] [Tamara
Rahn] loaded [cloud-aws], sites
[2013-06-27 15:33:33,801][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: initialized
[2013-06-27 15:33:33,802][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: starting ...
[2013-06-27 15:33:33,966][INFO ][transport ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.120.61.89:9300]}
[2013-06-27 15:33:38,082][WARN ][transport.netty ] [Tamara
Rahn] exception caught on transport layer [[id: 0x1490ef6d]], closing
connection
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
[2013-06-27 15:34:03,973][WARN ][discovery ] [Tamara
Rahn] waited for 30s and no initial state was set by the discovery
[2013-06-27 15:34:03,973][INFO ][discovery ] [Tamara
Rahn] SometaroLoggin/zrT7vF4fQRCJwPWdMNXGlg
[2013-06-27 15:34:03,980][INFO ][http ] [Tamara
Rahn] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.120.61.89:9200]}
[2013-06-27 15:34:03,981][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: started
[2013-06-27 15:34:08,189][INFO ][cluster.service ] [Tamara
Rahn] new_master [Tamara
Rahn][zrT7vF4fQRCJwPWdMNXGlg][inet[/10.120.61.89:9300]], reason:
zen-disco-join (elected_as_master)
[2013-06-27 15:34:08,273][INFO ][gateway ] [Tamara
Rahn] recovered [0] indices into cluster_state
^C[2013-06-27 15:36:38,628][INFO ][node ]
[Tamara Rahn] {0.90.2}[5369]: stopping ...
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: stopped
[2013-06-27 15:36:38,650][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closing ...
[2013-06-27 15:36:38,680][INFO ][node ] [Tamara
Rahn] {0.90.2}[5369]: closed

My command:
sudo bin/elasticsearch -f

I was following the guidehttp://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ on
how to setup an EC2 ES making modifications as necessary to meet my
different needs. In addition to the stack trace, the discovery.ec2 message
never happened. Any ideas?

--
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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

Topic		Replies	Views
No route to host error with new ES cluster Elasticsearch	4	15776	July 5, 2017
Elasticsearch, docker and iptables Elasticsearch	2	2887	July 5, 2017
Elasticsearch version 7.2 and version 6.8.1-- network.host: 0.0.0.0 is getting failed Elasticsearch	1	698	August 22, 2019
Elasticsearch 2.0 aws-cloud network issue Elasticsearch	11	2143	July 5, 2017
Please help me Install Elasticsearch in EC2 Elasticsearch	1	156	October 5, 2023

Issue setting up ES on AWS: No route to host

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

I was following the guide on how to setup an EC2 ES making modifications as necessary to meet my different needs. In addition to the stack trace, the discovery.ec2 message never happened. Any ideas?

Related topics