# Plugin install on ubuntu fails **URL:** \ **Category:** Logstash\ **Created:** [December 25, 2016, 12:22am UTC](https://discuss.elastic.co/t/plugin-install-on-ubuntu-fails/69951 "2016-12-25T00:22:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mcgrews3](https://avatars.discourse-cdn.com/v4/letter/m/edb3f5/32.png) [@mcgrews3](https://discuss.elastic.co/u/mcgrews3)\ **Post date:** [December 25, 2016, 12:22am UTC](https://discuss.elastic.co/t/plugin-install-on-ubuntu-fails/69951/1 "2016-12-25T00:22:27Z")
logstash version 5.1.1 I have gone through the documentation and installed logstash on ubuntu 14.04 twice - both times repeating the error. I have also reproduced the issue on my OS X mac-book-pro. It's also worth noting that I am using a web proxy on all these systems. I need to install logstash-filter-alter. When I try to do this I get an SSL error and the installation fails. ``` WARNING: SSLSocket#session= is not supported ``` I saw another thread with a similar issue; except in my case the installation retries 10 times and then fails. > Next when I try to run logstash-plugin program again I get error messages about not being able to find the gem: ``` logstash-plugin install logstash-filter-alter Bundler::GemNotFound: Could not find gem 'logstash-filter-alter (>= 0) java' in any of the gem sources listed in your Gemfile or installed on this machine. verify_gemfile_dependencies_are_found! at /Users/jdmcgrew/Development/logstash/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 /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:307 start at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:199 resolve at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:182 resolve at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:192 specs at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:132 specs_for at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:177 requested_specs at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:166 requested_specs at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/environment.rb:18 setup at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/runtime.rb:13 setup at /Users/jdmcgrew/Development/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler.rb:122 setup! at /Users/jdmcgrew/Development/logstash/lib/bootstrap/bundler.rb:64 (root) at /Users/jdmcgrew/Development/logstash/lib/pluginmanager/main.rb:9 ``` Here are my setup steps for ubuntu: ``` 1. bash profile setup with proxy info 2. sudo -E add-apt-repository ppa:webupd8team/java 3. sudo apt-get update 4. sudo -E apt-get install oracle-java8-installer 5. wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add - 6. sudo apt-get install apt-transport-https 7. echo "deb https://artifacts.elastic.co/packages/5.x/apt stable main" | sudo tee -a /etc/apt/sources.list.d/elastic-5.x.list 8. sudo apt-get update && sudo apt-get install logstash 9. cd /usr/share/logstash 10. vi bin/logstash-plugin -- add to JRUBY_OPTS = -J-Dhttp.proxyHost=-J-Dhttp.proxyPort= -J-Dhttps.proxyHost= -J-Dhttps.proxyPort= 11. sudo bin/logstash-plugin install logstash-filter-alter ``` ---
**Author:** ![mcgrews3](https://avatars.discourse-cdn.com/v4/letter/m/edb3f5/32.png) [@mcgrews3](https://discuss.elastic.co/u/mcgrews3)\ **Post date:** [December 27, 2016, 2:29am UTC](https://discuss.elastic.co/t/plugin-install-on-ubuntu-fails/69951/2 "2016-12-27T02:29:46Z")
Here is the command and error message when trying to install the logstash-fitler-alter plugin. ``` jdmcgrew-mac01:logstash jdmcgrew$ ./bin/logstash-plugin install logstash-filter-alter Validating logstash-filter-alter Installing logstash-filter-alter Error Bundler::InstallError, retrying 1/10 An error occurred while installing logstash-core-event-java (5.0.2), and Bundler cannot continue. Make sure that `gem install logstash-core-event-java -v '5.0.2'` succeeds before bundling. WARNING: SSLSocket#session= is not supported Error Bundler::InstallError, retrying 2/10 An error occurred while installing logstash-core-event-java (5.0.2), and Bundler cannot continue. Make sure that `gem install logstash-core-event-java -v '5.0.2'` succeeds before bundling. WARNING: SSLSocket#session= is not supported Error Bundler::InstallError, retrying 3/10 An error occurred while installing logstash-core-event-java (5.0.2), and Bundler cannot continue. Make sure that `gem install logstash-core-event-java -v '5.0.2'` succeeds before bundling. WARNING: SSLSocket#session= is not supported Too many retries, aborting, caused by Bundler::InstallError ERROR: Installation Aborted, message: An error occurred while installing logstash-core-event-java (5.0.2), and Bundler cannot continue. Make sure that `gem install logstash-core-event-java -v '5.0.2'` succeeds before bundling. ``` ---
**Author:** ![mcgrews3](https://avatars.discourse-cdn.com/v4/letter/m/edb3f5/32.png) [@mcgrews3](https://discuss.elastic.co/u/mcgrews3)\ **Post date:** [December 27, 2016, 3:16am UTC](https://discuss.elastic.co/t/plugin-install-on-ubuntu-fails/69951/3 "2016-12-27T03:16:13Z")
I reverted to the 2.x release of logstash and was able to install plugins without issue. Guess the 5.x releases are not stable yet.... ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 24, 2017, 3:16am UTC](https://discuss.elastic.co/t/plugin-install-on-ubuntu-fails/69951/4 "2017-01-24T03:16:17Z")
Closed on January 24, 2017, 3:16am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.