Monit issues (template file name, internal issues) about elasticsearch HOT 7 CLOSED

Argh, you're right -- this has slipped me, because we have a customized Monit cookbook which uses *.monitrc (we think it's a better naming). I think we should bend to monit cookbook's will here, though :/

The http_auth issue is again related to our particular setup, where we have a HTTP authentication setup for the Monit web frontend -- this is clearly bad. I'll fix the cookbok to work with the stock Monit recipe!

Glad that the cookbook is useful, thanks! :)

from elasticsearch.

Ryan, check the fix, please -- works locally with Vagrant and stock Monit cookbook.

from elasticsearch.

Also, could you please check the setup with 90ed2a1? It contains a fix for proper installation of the cloud-aws plugin on ES 0.19.

from elasticsearch.

Hi Karel,

Thanks for the rapid turnaround! I won't be able to check things in code until this weekend or Monday, but it looks correct on inspection. I also separately ran into the cloud-aws plugin issue and your fix looks analogous to what I did (sorry, I didn't have a chance to wrap it up in an issue yet). I'll report back for sure when I run it through my staging system.

Thanks again,
Ryan

from elasticsearch.

Hi Ryan, no rush, and thanks!

from elasticsearch.

Updated and deployed. Everything looks good. Thanks Karel!

from elasticsearch.

While investigating Monit issues, pushed 42db58c -- the Monit integration actually has been relying on default template location/filename. Should work now -- added a test to Vagrant as well.

from elasticsearch.