-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logstash alpha4/alpha5/beta1 - Error while installing any plugin on CentOS #5966
Comments
I'd like to stress out that this isn't related to filter translate plugin. Here an example with an attempt to reinstall filter mutate:
|
Probably also a cross-dup with #5777 |
Also as flagged in #5777 (comment) despite all the errors plugin is being installed properly and you can call it from the config. |
@ph can you take a look at this please? |
@suyograo I am looking at it. |
From what I read in the description, I believe you have an air gap system with no direct access to rubygems. There are some known issues in #5906 that we are working to resolve. Also I see that you are using In the meantime, Do you have an http proxy in place? You should be able to setup a Or for some plugin you can download the gem from rubygems and install it with |
Yes, I've used any combo of --local and --no-verify switches I could and I truly have internet-isolated environment. --no-verify seemed to work fine in my case up to alpha2, there is no combo of options that will allow me to install any local gem now.
I've tried this on logstash-filter-translate-3.0.0.gem, but the same error as previously. |
For future use of people looking into this thread: I managed to install local plugins from gem by using http proxy configured in .m2/settings.xml to make a proper connection to ruby gems (as mentioned in other tickets this connections shouldn't be made or required at all and that's gonna be fixed at some point). I guess in current state of things it's not possible to install local gems without any outside connectivity. How to configure proxy: #2851 (comment) |
Fixed in 5.2.0 |
The issue with logstash plugin installation appear to be related to maven and jar-dependencies. This is temporary fix! There is several related issues on github: elastic/logstash#5583 mkristian/ruby-maven#8 elastic/logstash#5072 elastic/logstash#5966
This is very similar to #5581, however proposed solution (update certs) doesn't work for CentOS
The text was updated successfully, but these errors were encountered: