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

Document bare minimum configuration for default recipe #87

Closed
mattupstate opened this Issue Apr 23, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@mattupstate

mattupstate commented Apr 23, 2013

I would, perhaps unfairly, assume that the default recipe without any attribute configuration should install and configure elasticsearch as a system service. I've been trying to get this working on a Vagrant VM (precise64 box). The VM is provisioned without error but elasticsearch is not running, nor will it run. Attempts to start the service always fail without any decent error messages.

Judging from the Vagrant file provided by the cookbook, there is a lot of configuration going on in order to get elasticsearch running properly. However, I can't distill from this file what exactly is the bare minimum to get a VM up and running.

@karmi

This comment has been minimized.

Show comment
Hide comment
@karmi

karmi Apr 23, 2013

Member

If it's a Vagrant virtual box, you need to set mlockall to false. Also, you can use the bundled Vagrant integration and just 'vagrant up'.

On Tuesday, 23. April 2013 at 21:42, Matt Wright wrote:

I would, perhaps unfairly, assume that the default recipe without any attribute configuration should install and configure elasticsearch as a system service. I've been trying to get this working on a Vagrant VM (precise64 box). The VM is provisioned without error but elasticsearch is not running, nor will it run. Attempts to start the service always fail without any decent error messages.
Judging from the Vagrant file provided by the cookbook, there is a lot of configuration going on in order to get elasticsearch running properly. However, I can't distill from this file what exactly is the bare minimum to get a VM up and running.


Reply to this email directly or view it on GitHub (#87).

Member

karmi commented Apr 23, 2013

If it's a Vagrant virtual box, you need to set mlockall to false. Also, you can use the bundled Vagrant integration and just 'vagrant up'.

On Tuesday, 23. April 2013 at 21:42, Matt Wright wrote:

I would, perhaps unfairly, assume that the default recipe without any attribute configuration should install and configure elasticsearch as a system service. I've been trying to get this working on a Vagrant VM (precise64 box). The VM is provisioned without error but elasticsearch is not running, nor will it run. Attempts to start the service always fail without any decent error messages.
Judging from the Vagrant file provided by the cookbook, there is a lot of configuration going on in order to get elasticsearch running properly. However, I can't distill from this file what exactly is the bare minimum to get a VM up and running.


Reply to this email directly or view it on GitHub (#87).

@mattupstate

This comment has been minimized.

Show comment
Hide comment
@mattupstate

mattupstate Apr 23, 2013

mlockall did the trick. Thanks for the tip.

mattupstate commented Apr 23, 2013

mlockall did the trick. Thanks for the tip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment