# Not able to install logstash-core-event-java gem as its giving me error

**URL:** <https://discuss.elastic.co/t/not-able-to-install-logstash-core-event-java-gem-as-its-giving-me-error/84589>\
**Category:** Logstash\
**Created:** [May 4, 2017, 3:29pm UTC](https://discuss.elastic.co/t/not-able-to-install-logstash-core-event-java-gem-as-its-giving-me-error/84589 "2017-05-04T15:29:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kartikeya\_sharma\_13](https://avatars.discourse-cdn.com/v4/letter/k/c77e96/32.png) [@kartikeya\_sharma\_13](https://discuss.elastic.co/u/kartikeya_sharma_13)\
**Post date:** [May 4, 2017, 3:29pm UTC](https://discuss.elastic.co/t/not-able-to-install-logstash-core-event-java-gem-as-its-giving-me-error/84589/1 "2017-05-04T15:29:54Z")

</div>

Hi All,  
I am not able to install the logstash-core-event-java gem as it is gining me this error

> Bundler::GemNotFound: Could not find gem 'logstash-filter-translate (\>= 0) java' in any of the gem sources listed in your Gemfile or installed on this machine.  
> verify\_gemfile\_dependencies\_are\_found! at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:328  
> each at org/jruby/RubyArray.java:1613  
> verify\_gemfile\_dependencies\_are\_found! at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:307  
> start at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:199  
> resolve at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:182  
> resolve at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:192  
> specs at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:132  
> specs\_for at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:177  
> requested\_specs at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:166  
> requested\_specs at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/environment.rb:18  
> setup at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/runtime.rb:13  
> setup at C:/ELK/logstash/logstash-5.3.1/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler.rb:122  
> setup! at C:/ELK/logstash/logstash-5.3.1/lib/bootstrap/bundler.rb:64  
> (root) at C:\ELK\logstash\logstash-5.3.1\lib\bootstrap\environment.rb:67

And when i tried to install the logstash-plugin install logstash-filter-translate

its giving me this error

> Error Bundler::InstallError, retrying 1/10  
> An error occurred while installing logstash-core-event-java (5.3.1), and Bundler cannot continue.  
> Make sure that `gem install logstash-core-event-java -v '5.3.1'` succeeds before bundling.  
> WARNING: SSLSocket#session= is not supported

---

<div class="post-metadata">

**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\
**Post date:** [May 12, 2017, 9:34am UTC](https://discuss.elastic.co/t/not-able-to-install-logstash-core-event-java-gem-as-its-giving-me-error/84589/2 "2017-05-12T09:34:52Z")

</div>

How did you install Logstash v5.3.1?

This is a very unusual error - does the machine you are trying this on have access to the internet?  
Can you ping [rubygems.org](http://rubygems.org)?

---

<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:** [June 9, 2017, 9:36am UTC](https://discuss.elastic.co/t/not-able-to-install-logstash-core-event-java-gem-as-its-giving-me-error/84589/3 "2017-06-09T09:36:13Z")

</div>

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