# Logstash crashed and spawning new process when tried installing new plugins **URL:** \ **Category:** Logstash\ **Created:** [September 1, 2017, 3:56am UTC](https://discuss.elastic.co/t/logstash-crashed-and-spawning-new-process-when-tried-installing-new-plugins/99077 "2017-09-01T03:56:19Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![arun\_prasath1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arun_prasath1/32/49539_2.png) [@arun\_prasath1](https://discuss.elastic.co/u/arun_prasath1)\ **Post date:** [September 1, 2017, 3:56am UTC](https://discuss.elastic.co/t/logstash-crashed-and-spawning-new-process-when-tried-installing-new-plugins/99077/1 "2017-09-01T03:56:19Z")
I have logstash v5.0.1 running in Redhat Enterprise v6.8. Recently, I tried to install plugin "logstash-output-email" using command-line from Internet using below commands. wget [https://api.rubygems.org/latest\_specs.4.8.gz](https://api.rubygems.org/latest_specs.4.8.gz) And, extracted to logstash bin path and then executed below commands. ./logstash-plugin install logstash-output-email /usr/share/logstash/bin/logstash-plugin install --no-verify logstash-output-email But none of them worked due to proxy and it failed. Then I came to knew that proxy is not enabled due to security reasons. So I reverted the configuration in the output plugin and restarted the logstash service. Then I noted logstash is spawning new process and process ids every few seconds and I see the below error messages appended to the /var/log/logstash-stderr.log file when logstash is running. Why is it still referring the Gem dependencies. It didn't install since there is no internet connectivity. so logstash should be running without issues, right? > Bundler::GemNotFound: Could not find gem 'logstash-output-email (\>= 0) java' in any of the gem sources listed in your Gemfile or installed on this machine. > verify\_gemfile\_dependencies\_are\_found! at /usr/share/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 /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:307 > start at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:199 > resolve at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/resolver.rb:182 > resolve at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:192 > specs at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:132 > specs\_for at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:177 > requested\_specs at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/definition.rb:166 > requested\_specs at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/environment.rb:18 > setup at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler/runtime.rb:13 > setup at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/bundler-1.9.10/lib/bundler.rb:122 > setup! at /usr/share/logstash/lib/bootstrap/bundler.rb:64 > (root) at /usr/share/logstash/lib/bootstrap/environment.rb:64 > Please help me with a solution how I can start the logstash without issues and starting working. Please suggest. ---
**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:** [September 4, 2017, 3:29pm UTC](https://discuss.elastic.co/t/logstash-crashed-and-spawning-new-process-when-tried-installing-new-plugins/99077/2 "2017-09-04T15:29:48Z")
It seems as if the plugin installer has half recorded the aborted install. I suggest that you copy any modifications you may have made to the Logstash config files (those in the config folder, not your input {} filter {} output{} config) and reinstall Logstash and put the saved config back. ---
**Author:** ![Vishal\_Sharma1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishal_sharma1/32/20207_2.png) [@Vishal\_Sharma1](https://discuss.elastic.co/u/Vishal_Sharma1)\ **Post date:** [September 4, 2017, 3:47pm UTC](https://discuss.elastic.co/t/logstash-crashed-and-spawning-new-process-when-tried-installing-new-plugins/99077/3 "2017-09-04T15:47:40Z")
Also check the plugin directory if you can see the files for the plugin.. just remove them ---
**Author:** ![arun\_prasath1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arun_prasath1/32/49539_2.png) [@arun\_prasath1](https://discuss.elastic.co/u/arun_prasath1)\ **Post date:** [September 21, 2017, 6:12pm UTC](https://discuss.elastic.co/t/logstash-crashed-and-spawning-new-process-when-tried-installing-new-plugins/99077/4 "2017-09-21T18:12:17Z")
Vishal @ I have removed the files inside the plugin directory and it worked. ---
**Author:** ![Vishal\_Sharma1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishal_sharma1/32/20207_2.png) [@Vishal\_Sharma1](https://discuss.elastic.co/u/Vishal_Sharma1)\ **Post date:** [September 22, 2017, 4:29am UTC](https://discuss.elastic.co/t/logstash-crashed-and-spawning-new-process-when-tried-installing-new-plugins/99077/5 "2017-09-22T04:29:18Z")
Glad it worked 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 20, 2017, 4:30am UTC](https://discuss.elastic.co/t/logstash-crashed-and-spawning-new-process-when-tried-installing-new-plugins/99077/6 "2017-10-20T04:30:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.