Cloud-aws not working 0.20.1 and 0.19.12?

Elastic Stack Elasticsearch
1

All,

I previously had 0.19.11 (not sure exact version of 19) installed and
working with the aws-plugin for EC2 discovery. I have re-installed into a
new AMI and regardless of which 0.19.12 and 0.20.1 if I put
"discovery.type: ec2" into the config file neither version will start, but
with that line commented out Elasticsearch will start.

My problem is that I don't know where to begin troubleshooting, not much is
entered into the logs even though I configured logging.yml with "debug" for
as much as I could. The only thing I see in the elasticsearch log is [INFO
] plugins ] [ec2-hostname] loaded [], sites [cloud-aws], after that
nothing.

How do I go about tracking down whether this is an issue with my EC2 setup
or AMI (security groups, or some other setting I am not aware of) or
something wrong with the plugin?

Thank you for any suggestions or help offered.

p.s. I know the security keys are correct since I am using them to execute
ec2-* commands.

--

2

I have more data, I copied the command line (from ps output) and ran it on
the cli.

/usr/lib/jvm/java-7-openjdk-amd64//bin/java -Xms10g -Xmx10g -Xss256k
-Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
-XX:+HeapDumpOnOutOfMemoryError -Delasticsearch
-Des.pidfile=/var/run/elasticsearch.pid
-Des.path.home=/usr/share/elasticsearch -cp
:/usr/share/elasticsearch/lib/elasticsearch-0.20.1.jar:/usr/share/elasticsearch/lib/:/usr/share/elasticsearch/lib/sigar/
-Des.default.config=/etc/elasticsearch/elasticsearch.yml
-Des.default.path.home=/usr/share/elasticsearch
-Des.default.path.logs=/var/log/elasticsearch
-Des.default.path.data=/var/lib/elasticsearch
-Des.default.path.work=/tmp/elasticsearch
-Des.default.path.conf=/etc/elasticsearch
org.elasticsearch.bootstrap.Elasticsearch
{0.20.1}: Initialization Failed ...

  • NoClassSettingsException[Failed to load class setting [discovery.type]
    with value [ec2]]
    ClassNotFoundException[ec2]

Hope that helps.

On Friday, December 28, 2012 1:41:19 PM UTC-5, Brian Schrock wrote:

All,

I previously had 0.19.11 (not sure exact version of 19) installed and
working with the aws-plugin for EC2 discovery. I have re-installed into a
new AMI and regardless of which 0.19.12 and 0.20.1 if I put
"discovery.type: ec2" into the config file neither version will start, but
with that line commented out Elasticsearch will start.

My problem is that I don't know where to begin troubleshooting, not much
is entered into the logs even though I configured logging.yml with "debug"
for as much as I could. The only thing I see in the elasticsearch log is
[INFO ] plugins ] [ec2-hostname] loaded , sites [cloud-aws], after
that nothing.

How do I go about tracking down whether this is an issue with my EC2 setup
or AMI (security groups, or some other setting I am not aware of) or
something wrong with the plugin?

Thank you for any suggestions or help offered.

p.s. I know the security keys are correct since I am using them to execute
ec2-* commands.

--

3

I figured it out, I had installed the plugin with the command "bin/plugin
install elasticsearch/elasticsearch-cloud-aws" and that installed the
source files, but if I ran the command from the github page "bin/plugin
-install elasticsearch/elasticsearch-cloud-aws/1.10.0" the jar files got
installed.

I guess chalk it up to me being stupid, sorry to bother everyone.

On Friday, December 28, 2012 1:41:19 PM UTC-5, Brian Schrock wrote:

All,

I previously had 0.19.11 (not sure exact version of 19) installed and
working with the aws-plugin for EC2 discovery. I have re-installed into a
new AMI and regardless of which 0.19.12 and 0.20.1 if I put
"discovery.type: ec2" into the config file neither version will start, but
with that line commented out Elasticsearch will start.

My problem is that I don't know where to begin troubleshooting, not much
is entered into the logs even though I configured logging.yml with "debug"
for as much as I could. The only thing I see in the elasticsearch log is
[INFO ] plugins ] [ec2-hostname] loaded , sites [cloud-aws], after
that nothing.

How do I go about tracking down whether this is an issue with my EC2 setup
or AMI (security groups, or some other setting I am not aware of) or
something wrong with the plugin?

Thank you for any suggestions or help offered.

p.s. I know the security keys are correct since I am using them to execute
ec2-* commands.

--

4

It's not you, the feature having the source installed without being noticed
when a binary plugin install is expected, is not obvious to many of us - I
wasted a whole day testing plugin installs because of this once.

Jörg

On Friday, December 28, 2012 9:50:08 PM UTC+1, Brian Schrock wrote:

I figured it out, I had installed the plugin with the command "bin/plugin
install elasticsearch/elasticsearch-cloud-aws" and that installed the
source files, but if I ran the command from the github page "bin/plugin
-install elasticsearch/elasticsearch-cloud-aws/1.10.0" the jar files got
installed.

I guess chalk it up to me being stupid, sorry to bother everyone.

On Friday, December 28, 2012 1:41:19 PM UTC-5, Brian Schrock wrote:

All,

I previously had 0.19.11 (not sure exact version of 19) installed and
working with the aws-plugin for EC2 discovery. I have re-installed into a
new AMI and regardless of which 0.19.12 and 0.20.1 if I put
"discovery.type: ec2" into the config file neither version will start, but
with that line commented out Elasticsearch will start.

My problem is that I don't know where to begin troubleshooting, not much
is entered into the logs even though I configured logging.yml with "debug"
for as much as I could. The only thing I see in the elasticsearch log is
[INFO ] plugins ] [ec2-hostname] loaded , sites [cloud-aws], after
that nothing.

How do I go about tracking down whether this is an issue with my EC2
setup or AMI (security groups, or some other setting I am not aware of) or
something wrong with the plugin?

Thank you for any suggestions or help offered.

p.s. I know the security keys are correct since I am using them to
execute ec2-* commands.

--

5

Agreed, its annoying. We actually now detect if you install a plugin with "java" source files from "master" in github, and fail the plugin installation (in 0.20.2). The idea for this feature is to allow to install site plugins easily from their respective github repos.

On Dec 29, 2012, at 3:58 PM, Jörg Prante joergprante@gmail.com wrote:

It's not you, the feature having the source installed without being noticed when a binary plugin install is expected, is not obvious to many of us - I wasted a whole day testing plugin installs because of this once.

Jörg

On Friday, December 28, 2012 9:50:08 PM UTC+1, Brian Schrock wrote:
I figured it out, I had installed the plugin with the command "bin/plugin install elasticsearch/elasticsearch-cloud-aws" and that installed the source files, but if I ran the command from the github page "bin/plugin -install elasticsearch/elasticsearch-cloud-aws/1.10.0" the jar files got installed.

I guess chalk it up to me being stupid, sorry to bother everyone.

On Friday, December 28, 2012 1:41:19 PM UTC-5, Brian Schrock wrote:
All,

I previously had 0.19.11 (not sure exact version of 19) installed and working with the aws-plugin for EC2 discovery. I have re-installed into a new AMI and regardless of which 0.19.12 and 0.20.1 if I put "discovery.type: ec2" into the config file neither version will start, but with that line commented out Elasticsearch will start.

My problem is that I don't know where to begin troubleshooting, not much is entered into the logs even though I configured logging.yml with "debug" for as much as I could. The only thing I see in the elasticsearch log is [INFO ] plugins ] [ec2-hostname] loaded , sites [cloud-aws], after that nothing.

How do I go about tracking down whether this is an issue with my EC2 setup or AMI (security groups, or some other setting I am not aware of) or something wrong with the plugin?

Thank you for any suggestions or help offered.

p.s. I know the security keys are correct since I am using them to execute ec2-* commands.

--

--