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

If elasticsearch fails to extract, it won't be installed later #221

Closed
unflores opened this issue Jun 19, 2014 · 1 comment
Closed

If elasticsearch fails to extract, it won't be installed later #221

unflores opened this issue Jun 19, 2014 · 1 comment

Comments

@unflores
Copy link

Hello,
During my chef run recently I noticed that using ark, the ES recipe creates the following directory structure:

/usr/local/bin/elasticsearch  -> /usr/local/elasticsearch-x.xx.x/bin/elasticsearch
/usr/local/elasticsearch-x.xx.x/files

After creating the structure, the [unpack /var/chef/cache/elasticsearch.tar.gz] is delayed until later during the chef process. My internet connection is not exactly top and occasionally cuts out before the files are unpacked for in the elasticsearch-x.xx.x directory.

When I rerun the chef command, the ES recipe does not attempt to unpack the elasticsearch.tar.gz file. The problem can be reproduced simply by deleting the files in /usr/local/elasticsearch-x.xx.x/* and re-running the ES recipe.

@martinb3
Copy link
Contributor

martinb3 commented Jul 7, 2015

Hello! We've re-written the cookbook using libraries that expose resources and providers, so you shouldn't see this problem on the newer version; could you verify that for us? Hope this helps! Please re-open as a new issue if you're still seeing it.

@martinb3 martinb3 closed this as completed Jul 7, 2015
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