You must set ES_CLASSPATH var about elasticsearch HOT 3 CLOSED

I all depends on how you run Elasticsearch. You can't just run elasticsearch -f, since no ES_CLASSPATH is set in that case. You have to use the provided init script or pass the path to the environment file:

ES_INCLUDE=/usr/local/etc/elasticsearch/elasticsearch-env.sh elasticsearch -f

from elasticsearch.

So I added elasticsearch -f to the init script, and then ran sudo ./elasticsearch start. I got the following output, and I assume the last line is not good... :(:

[2013-04-08 17:15:03,988][INFO ][node ] [ip-10-253-41-10.us-west-2.compute.internal] {0.20.5}[1884]: initializing ...
[2013-04-08 17:15:04,008][INFO ][plugins ] [ip-10-253-41-10.us-west-2.compute.internal] loaded [cloud-aws], sites [paramedic]
[2013-04-08 17:15:06,820][WARN ][transport ] [ip-10-253-41-10.us-west-2.compute.internal] Registered two transport handlers for action discovery/zen/fd/masterPing, handlers: org.elasticsearch.discovery.zen.fd.MasterFaultDetection$MasterPingRequestHandler@65107b3f, org.elasticsearch.discovery.zen.fd.MasterFaultDetection$MasterPingRequestHandler@1d0b98ef
[2013-04-08 17:15:06,820][WARN ][transport ] [ip-10-253-41-10.us-west-2.compute.internal] Registered two transport handlers for action discovery/zen/fd/ping, handlers: org.elasticsearch.discovery.zen.fd.NodesFaultDetection$PingRequestHandler@646581ce, org.elasticsearch.discovery.zen.fd.NodesFaultDetection$PingRequestHandler@442d2ee0
[2013-04-08 17:15:06,821][WARN ][transport ] [ip-10-253-41-10.us-west-2.compute.internal] Registered two transport handlers for action discovery/zen/publish, handlers: org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequestHandler@72609717, org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequestHandler@235fa1ab
[2013-04-08 17:15:06,821][WARN ][transport ] [ip-10-253-41-10.us-west-2.compute.internal] Registered two transport handlers for action discovery/zen/join, handlers: org.elasticsearch.discovery.zen.membership.MembershipAction$JoinRequestRequestHandler@5b6ef3b1, org.elasticsearch.discovery.zen.membership.MembershipAction$JoinRequestRequestHandler@5141185c
[2013-04-08 17:15:06,821][WARN ][transport ] [ip-10-253-41-10.us-west-2.compute.internal] Registered two transport handlers for action discovery/zen/join/validate, handlers: org.elasticsearch.discovery.zen.membership.MembershipAction$ValidateJoinRequestRequestHandler@8a669b1, org.elasticsearch.discovery.zen.membership.MembershipAction$ValidateJoinRequestRequestHandler@6564e7e6
[2013-04-08 17:15:06,822][WARN ][transport ] [ip-10-253-41-10.us-west-2.compute.internal] Registered two transport handlers for action discovery/zen/leave, handlers: org.elasticsearch.discovery.zen.membership.MembershipAction$LeaveRequestRequestHandler@43b4e10b, org.elasticsearch.discovery.zen.membership.MembershipAction$LeaveRequestRequestHandler@1822bbe7
[2013-04-08 17:15:06,822][WARN ][transport ] [ip-10-253-41-10.us-west-2.compute.internal] Registered two transport handlers for action discovery/zen/rejoin, handlers: org.elasticsearch.discovery.zen.ZenDiscovery$RejoinClusterRequestHandler@105e4712, org.elasticsearch.discovery.zen.ZenDiscovery$RejoinClusterRequestHandler@1d8bf723
[2013-04-08 17:15:07,491][ERROR][bootstrap ] {0.20.5}: Initialization Failed ...

1. IllegalStateException[This is a proxy used to support circular references involving constructors. The object we're proxying is not constructed yet. Please wait until after injection has completed to use this object.]2) ElasticSearchIllegalArgumentException[No automatic endpoint could be derived from region [us-west-2a]]

from elasticsearch.

So I added elasticsearch -f to the init script, and then ran sudo ./elasticsearch start.

I'm a bit confused by that :) The cookbook comes with an init script (service), and you can use the servicewrapper as well. I'm wondering about what kind of script you use to run elasticsearch.

I got the following output, and I assume the last line is not good... :(

1) ...[No automatic endpoint could be derived from region [us-west-2a]]

Indeed -- it means the discovery can't find an endpoint based on the us-west-2a value. I'm wondering about the configuration you use for AWS -- notice that you can set either a region (cloud.aws.region), which would be something like us-west-2 or the endpoint directly (cloud.aws.ec2.endpoint), which would be something like ec2.us-west-2.amazonaws.com in your case.

from elasticsearch.