-
-
Notifications
You must be signed in to change notification settings - Fork 599
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
ruby command not found #378
Comments
Even if you install ruby and rubygems, you still get issues with the init script because the json gem isn't installed. Init scripts really shouldn't depend on ruby and specific gems being available system wide.
|
I agree completely. When we did the big 1.0 rewrite, we put off fixing this particular issue. But Init scripts are on the next release milestone. Check out #321. |
Thanks. I'll close this issue infavor of #321 |
Hi folks -- could you try the 2.0.0_wip branch of this cookbook, and report back any issues in #321? It has the same init scripts now as the packaged version of ES; it's our goal to release a 2.0.0 version that works with ES 2.0.0. It does have some changes from the current version, but depending on how complex your resource usage is, you may or may not be affected. Thanks! |
If you use a basic install, you will get an error when you start elasticsearch
The init script should be modified so that ruby isn't a dependency, or the documentation should show an example of how to install ruby. (The first being very preferred in my opinion)
The text was updated successfully, but these errors were encountered: