Startup fails after installing plugin

[brandonhilkert]

I added the plugin and can see it being loaded here:

discovery.type: ec2
discovery.ec2.groups: elasticsearch

I didn't add our access_keys and everything b/c the README said we didn't need to with the latest version.

The log has a bunch of lines like this:

[2013-08-09 15:05:27,432][WARN ][transport                ] [Elasticsearch-01] Registered two transport handlers for action discovery/zen/fd/ping, handlers: org.elasticsearch.discovery.zen.fd.NodesFaultDetection$PingRequestHandler@32c5f9fe, org.elasticsearch.discovery.zen.fd.NodesFaultDetection$PingRequestHandler@36ddc581
[2013-08-09 15:05:27,432][WARN ][transport                ] [Elasticsearch-01] Registered two transport handlers for action discovery/zen/publish, handlers: org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequestHandler@639facbc, org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequestHandler@19d1b44b
[2013-08-09 15:05:27,432][WARN ][transport                ] [Elasticsearch-01] Registered two transport handlers for action discovery/zen/join, handlers: org.elasticsearch.discovery.zen.membership.MembershipAction$JoinRequestRequestHandler@8059dbd, org.elasticsearch.discovery.zen.membership.MembershipAction$JoinRequestRequestHandler@1693b52b
[2013-08-09 15:05:27,432][WARN ][transport                ] [Elasticsearch-01] Registered two transport handlers for action discovery/zen/join/validate, handlers: org.elasticsearch.discovery.zen.membership.MembershipAction$ValidateJoinRequestRequestHandler@28b6e768, org.elasticsearch.discovery.zen.membership.MembershipAction$ValidateJoinRequestRequestHandler@3b5b25a1
[2013-08-09 15:05:27,432][WARN ][transport                ] [Elasticsearch-01] Registered two transport handlers for action discovery/zen/leave, handlers: org.elasticsearch.discovery.zen.membership.MembershipAction$LeaveRequestRequestHandler@1271ba, org.elasticsearch.discovery.zen.membership.MembershipAction$LeaveRequestRequestHandler@5d038b78
[2013-08-09 15:05:27,432][WARN ][transport                ] [Elasticsearch-01] Registered two transport handlers for action discovery/zen/rejoin, handlers: org.elasticsearch.discovery.zen.ZenDiscovery$RejoinClusterRequestHandler@3ae86a5f, org.elasticsearch.discovery.zen.ZenDiscovery$RejoinClusterRequestHandler@13b9a2fd

If I remove:

discovery.type: ec2

The es process starts up just fine. Am I missing something? I can't seem to find an relevant errors for why the process wouldn't be starting.

[brandonhilkert]

ubuntu@dom-E1:/var/log/elasticsearch$ sudo service elasticsearch status
 * ElasticSearch Server is not running, but pid file exists.

[dadoonet]

Hey @brandonhilkert,

What version of ES are you using and which plugin version?
Is it a new installation or a migration concern?

Thanks

[brandonhilkert]

new installation

ES: 0.90.3
plugin: 1.13.0

[dadoonet]

Could you test with ES 0.90.2 / plugin 1.12.0 to see if it's a regression?

[brandonhilkert]

Yes, 0.90.2 works with 1.12 with the same config files.

[dadoonet]

Argh! Thanks for the test. Working on it.
Will update the issue.

[dadoonet]

Sounds like its a side effect of #32
Going to revert that change.

[brandonhilkert]

Gotcha. Are previous versions of the plugin compatible with 0.90.3? Just trying to get something working with the latest ES.

[dadoonet]

No. Just wait for some minutes. I'm currently releasing the new version 1.14.0.

[brandonhilkert]

Ok. No problem. Thanks!

[ejain]

Same problem here; will test 1.14.0 as soon as it is available.

[dadoonet]

@brandonhilkert Could you test bin/plugin --install elasticsearch/elasticsearch-cloud-aws/1.14.0? Not public yet. Just want to double check before real release and announcing.

[brandonhilkert]

works!

[dadoonet]

Cool. Thanks!

[brandonhilkert]

Thanks again for the speedy response! Got our cluster up and running because of it.

[ejain]

Works for me, too, thanks!