# Installing marvel 2.4.0 via chef

**URL:** <https://discuss.elastic.co/t/installing-marvel-2-4-0-via-chef/66150>\
**Category:** Elasticsearch\
**Created:** [November 15, 2016, 6:49pm UTC](https://discuss.elastic.co/t/installing-marvel-2-4-0-via-chef/66150 "2016-11-15T18:49:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pshroads](https://avatars.discourse-cdn.com/v4/letter/p/a88e57/32.png) [@pshroads](https://discuss.elastic.co/u/pshroads)\
**Post date:** [November 15, 2016, 6:49pm UTC](https://discuss.elastic.co/t/installing-marvel-2-4-0-via-chef/66150/1 "2016-11-15T18:49:14Z")

</div>

We install elasticsearch via chef. Now that (as of 2.4) marvel is installed as a kibana plugin instead of an elasticsearch plugin I am running in to an issue.

```
<pseudo code>If this is a marvel node</pseudo code>
include_recipe 'kibana'
execute 'install_marvel' do
command '/usr/local/kibana-4.6.1/bin/kibana plugin --install marvel --url <path_to_tar_file>
end

```

The problem is that after the initial run every subsequent chef-client run fails with the error that the marvel plugin has already been installed. Is there a better way to go about this?

Thanks

Patrick

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 13, 2016, 6:49pm UTC](https://discuss.elastic.co/t/installing-marvel-2-4-0-via-chef/66150/2 "2016-12-13T18:49:40Z")

</div>

Closed on December 13, 2016, 6:49pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.