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
Exception while converting Key #129
Comments
CC @ph |
- Changed the logstash dockerfile to use the tar.gz which is much simpler. - Unfortunately it still doesn't work, I posted: logstash-plugins/logstash-input-beats#129 - For elasticsearch I did a hack for now, but we should consider moving to the tar.gz as well
That's problematic, the last release of the beats input shouldn't contains the PrivateKeyConverter.java. I known whats happening, IIRC the unified build process takes the 5.0 branch to generate the artifact and in our branch the lockfile (which is the source of truth for the version) is set to the See https://github.com/elastic/logstash/blob/5.0/Gemfile.jruby-1.9.lock#L248 |
The B1 internal releases contained an old version of the beats input which didn't work well with the private keys, this PR make sure we use the latest version 3.1.4 in the 5.0 and 5.X branches Fixes: logstash-plugins/logstash-input-beats#129
This will be fixed by elastic/logstash#5925 |
The B1 internal releases contained an old version of the beats input which didn't work well with the private keys, this PR make sure we use the latest version 3.1.4 in the 5.0 and 5.X branches Fixes: logstash-plugins/logstash-input-beats#129
The B1 internal releases contained an old version of the beats input which didn't work well with the private keys, this PR make sure we use the latest version 3.1.4 in the 5.0 and 5.X branches Fixes: logstash-plugins/logstash-input-beats#129 Fixes #5925
We will respin a new beta1, the fix is in master |
- Changed the logstash dockerfile to use the tar.gz which is much simpler. - Unfortunately it still doesn't work, I posted: logstash-plugins/logstash-input-beats#129 - For elasticsearch I did a hack for now, but we should consider moving to the tar.gz as well
I was trying to test the beta1 IRC, but I'm getting an exception on startup:
The certificates are the ones from here which should be created with the right openssl version (I did try to recreate them).
The full debugging output can be found here: https://gist.github.com/tsg/965625a1a2aa6aa6bfed1fa9fd81646c
The text was updated successfully, but these errors were encountered: