Plugin not found


(Pjanzen) #1

Hi,

I am trying to install logstash-filter-elasticsearch plugin using the following command:
JARS_DEBUG=true JARS_VERBOSE=true DEBUG=1 bin/logstash-plugin install logstash-filter-elasticsearch

The error I get is: Errno::ECONNREFUSED: Connection refused - Connection refused

I have set export https_proxy= and I have create a ~/.m2/settings.xml with proxy settings in there.

I am trying to download the file from a different computer without proxy and then I end up with this.

<?xml version="1.0" encoding="UTF-8"?>

NoSuchKeyThe specified key does not exist.downloads/logstash-plugins/logstash-filter-dissect/logstash-filter-dissect-5.2.0.zipCBC3FEE4A0F6D088FYeXTwYavdJ4XvYbnu+JRUIKxEp8Jw+6nI7idQPwnpARvPo+iLxQSVPHq/41f30yj95vWNxqBlU=

Any clues on what to do next?

Thanks,
Paul.


(Magnus Bäck) #2

The documentation suggests setting HTTP_PROXY, not https_proxy.


(Pjanzen) #3

Hi,

changed the setting and there is no difference in the result.

Here is the complete error:

root@esearch9:/usr/share/logstash# export HTTP_PROXY=http://wsus.oss.local:443/
root@esearch9:/usr/share/logstash# JARS_DEBUG=true JARS_VERBOSE=true DEBUG=1 bin/logstash-plugin install logstash-filter-elasticsearch
DEBUG: exec /usr/share/logstash/vendor/jruby/bin/jruby /usr/share/logstash/lib/pluginmanager/main.rb install logstash-filter-elasticsearch
--- loaded jars ---

register ["org.bouncycastle", "bcpkix-jdk15on", "1.54"] - true
register ["org.bouncycastle", "bcprov-jdk15on", "1.54"] - true

Looking if package named: logstash-filter-elasticsearch exists at https://artifacts.elastic.co/downloads/logstash-plugins/logstash-filter-elasticsearch/logstash-filter-elasticsearch-5.2.0.zip
Errno::ECONNREFUSED: Connection refused - Connection refused
initialize at org/jruby/ext/socket/RubyTCPSocket.java:126
open at org/jruby/RubyIO.java:1197
connect at /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:763
timeout at org/jruby/ext/timeout/Timeout.java:98
connect at /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:763
do_start at /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:756
start at /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:745
start at /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:557
start at /usr/share/logstash/lib/pluginmanager/utils/http_client.rb:13
remote_file_exist? at /usr/share/logstash/lib/pluginmanager/utils/http_client.rb:23
get_installer_for at /usr/share/logstash/lib/pluginmanager/pack_fetch_strategy/repository.rb:27
create at /usr/share/logstash/lib/pluginmanager/install_strategy_factory.rb:15
each at org/jruby/RubyArray.java:1613
create at /usr/share/logstash/lib/pluginmanager/install_strategy_factory.rb:14
execute at /usr/share/logstash/lib/pluginmanager/install.rb:30
run at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:67
execute at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/subcommand/execution.rb:11
run at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:67
run at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:132
(root) at /usr/share/logstash/lib/pluginmanager/main.rb:46


(Magnus Bäck) #4

root@esearch9:/usr/share/logstash# export HTTP_PROXY=http://wsus.oss.local:443/

Does it really serve plain HTTP on port 443?


(Pjanzen) #5

Hi,

Yes it does, I can get trough plain and ssl site just fine but is must be something local, I installed a local vm directly connected to internet and I can install the plugin just fine...

(today is not my day)

Paul.


(Pjanzen) #6

So I got a solution for my problem.

So it looks like that logstash-plugin (5.2.0) is ignoring the env setting http_proxy or HTTP_PROXY.
A round of google told me you can set jruby options aswel so I went ahead and made a small adjustment to logstash-plugin and changed the line JRUBY_OPTS and added -J-Dhttp.proxyHost=wsus.oss.local -J-Dhttp.proxyPort=443 and now I can install plugins again.

So is this a bug? should I create a issue on github?

Paul.


(Magnus Bäck) #7

Yes, that's a bug (either in the documentation or the code). Would you mind filing a GitHub issue with your findings?


(system) #8

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