Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ES not starting when setting version to 1.5.2 or 1.6.0 #325

Closed
Paul424 opened this issue Jun 20, 2015 · 2 comments
Closed

ES not starting when setting version to 1.5.2 or 1.6.0 #325

Paul424 opened this issue Jun 20, 2015 · 2 comments

Comments

@Paul424
Copy link

Paul424 commented Jun 20, 2015

I'm using version 0.3.13 of the cookbook.

When providing no version attribute in the role version 0.90.12 is installed which is started and running fine. However since i need a feature that is not supported by 0.90.x i set the version attribute in the role to a newer version. I tried 1.5.2 and 1.6.0.

default_attributes(
"elasticsearch" => {
"version" => "1.5.2",

Problem is that although the version is downloaded and installed the service does not start. Also manually it does not start, when stopping the service it reports PID file found but no matching process running.

Can i fix this? Or what version are supported by the cookbook?

@Paul424
Copy link
Author

Paul424 commented Jun 20, 2015

I got the issue fixed.

First i read other issue's about customizing/attributes using a wrapper cookbook. That did not work; or actually it was even unclear to me how this should work....

Then i found an exception in the ES log; since 1.6.0 was in fact installed it just failed to start. Exception was:

[2015-06-20 21:17:18,586][ERROR][bootstrap ] Exception
org.elasticsearch.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: org/elasticsearch/ElasticSearchIllegalArgumentException

After googling around i got a tip to upgrade the aws-cloud plugin. I manually removed the old/incompatible version and then i could start the service.

Just for clarity: i could could install version 1.6.0 by just overriding the version attribute in the roles/index.rb.

Paul

@martinb3
Copy link
Contributor

Hi Paul, I'm not sure it would be safe to upgrade all plugins in all cases. In any case, in the development branch of the cookbook, we are creating a new directory for each install, which would contain only plugins for that version. I think it would probably have avoided the issue you encountered. If you feel like there's something else that could be done, please let us know & I'll re-open this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants