# Logstash 2.1 fails to start after logstash-output-elasticsearch update

**URL:** <https://discuss.elastic.co/t/logstash-2-1-fails-to-start-after-logstash-output-elasticsearch-update/38330>\
**Category:** Logstash\
**Created:** [January 4, 2016, 4:09pm UTC](https://discuss.elastic.co/t/logstash-2-1-fails-to-start-after-logstash-output-elasticsearch-update/38330 "2016-01-04T16:09:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![techcheez](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@techcheez](https://discuss.elastic.co/u/techcheez)\
**Post date:** [January 4, 2016, 5:40pm UTC](https://discuss.elastic.co/t/logstash-2-1-fails-to-start-after-logstash-output-elasticsearch-update/38330/3 "2016-01-04T17:40:54Z")

</div>

Digging deeper into the rabbit hole I discovered I needed to specify the path to jruby to run the gem install command. When running the following command I now see missing dependency for manticore v0.5.2.

`env GEM_HOME=/opt/logstash/vendor/bundle/jruby/1.9 /opt/logstash/vendor/jruby/bin/jruby /opt/logstash/vendor/jruby/bin/gem install manticore -v '0.5.2'`

it was missing an xml file that was supposed to be included with ruby-maven 3.3.8.

The following 2 commands got me back up and running with logstash-output-elasticsearch v2.3.1:

`[user@host ~]# env GEM_HOME=/opt/logstash/vendor/bundle/jruby/1.9 /opt/logstash/vendor/jruby/bin/jruby /opt/logstash/vendor/jruby/bin/gem install ruby-maven`

this installed the lastest v.3.3.8 of ruby-maven and then I ran

`[user@host ~]# env GEM_HOME=/opt/logstash/vendor/bundle/jruby/1.9 /opt/logstash/vendor/jruby/bin/jruby /opt/logstash/vendor/jruby/bin/gem install manticore -v '0.5.2'`

after that install completed successfully I was able to restart logstash. Hope this helps!

---

_[View the full topic](https://discuss.elastic.co/t/logstash-2-1-fails-to-start-after-logstash-output-elasticsearch-update/38330)._