Closed siginigin closed 7 years ago
@siginigin There is a bug with the HTTP_PROXY
which was described in https://github.com/elastic/logstash/issues/6044 this will be fixed in 5.2.0,
In the meantime, have you tried the following?
export http_proxy=http://proxy:port export https_proxy=http://proxy:port And creating a settings.xml file see this comment: https://github.com/elastic/logstash/issues/6044#issuecomment-253854228
This should allow you to install plugins or update them.
Hi ph,
thank you for answer.
Yes, I tried that, same result. But now I don't have problem with installing plugins, they are installed fine according to "Installation successful" after .../logstash-plugin install command. So downloading through proxy works fine. But something goes wrong as the command .../logstash-plugin list fail. I don't know how to continue with investigation, so for now I have to wait for 5.2.0.
Thank you.
Hi,
I have just installed v5.1.2-1 and plugins are installed correctly without any problems. Thank you guys for good job.
Slightly OT: logstash isn't correctly checking the config, this
/usr/share/logstash/bin/logstash --path.settings /etc/logstash/ --verbose --trace --log.level debug -t
says Configuration OK, but config is not OK. As a result, logstash die without saying where is the problem. I had to repair filepaths to geoip and missing patterns and then logstash started. It would be nice if logstash warns about these errors.
I am closing the issue now.
Thank you once again.
@siginigin I'm sorry you had a bad experience with Logstash. The problem you experienced boils down to a miscommunication and/or a misunderstanding of what the -t
flag does.
It is frequently assumed (not just by you) that it tests all potential configuration options for correctness, which I agree, is not an unreasonable thing to infer. The reality is that the -t
flag only does a simple sanity check to ensure that string-type variables are strings, booleans are booleans, integers are integers, etc., and that there are no syntactical mistakes (missing quotes, curly braces, hash-rockets, arrays look good, etc.). It does not validate potential misconfigurations. I think it would be nice to find a way to do this, but when taken as a whole, that will be a rather tall order to fill. Logstash will have to chase paths, network ports, load and test credentials for various services, etc. Every single plugin would have to be updated to do such a thing. Certainly not impossible, but not a matter of only a few lines of code to be changed either. Perhaps at some point this will be added, but for now, the -t
flag is just a syntax checker, not a configuration validator.
Hi all,
I'm unable to install any plugin to logstash due to logstash-core-event-java and logstash-core. I'm fighting with this all december. I'm behind proxy and I tried almost all suggested solutions but none worked.
I was finally able to install all plugins at once using:
But then I'm unable to even list the plugins. Lets look at the debug:
Ok, now it looks like everything went good. But appearances are deceptive...
Logstash is not able to start in this situation, still this error is on the output. Do you guys have some advice what can I do now? Thanx for any help.