-
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
"OpenSSL::SSL::SSLError: Received fatal alert: handshake_failure" in http output #3712
Comments
Related to #3657, we are working on a fix in 1.5.4. stay tuned! |
Thanks a lot for the quick response! |
1.5.4 and 1.4.5 has been released with this fix. |
@suyograo I just installed 1.5.4 for testing, and unfortunately it doesn't fix this issue for me. Is there anything I can do to help get to the bottom of this? More details below. Confirming I've got 1.5.4.
Minimal config with which I can replicate the error:
Logstash debug ouput:
The |
Not sure if this is at all helpful, but I stumbled on the
|
Running into the exact same issue (incidentally, also calling |
@naneau I think this is due to a bug in the HTTP library used: jordansissel/ruby-ftw#31. Not sure it's any help, but if you know some Ruby, it's not actually very hard to write your own HTTP output plugin that just uses Net::HTTP until this gets fixed: https://www.elastic.co/guide/en/logstash/current/_how_to_write_a_logstash_output_plugin.html |
We are switching from ruby-ftw to manticore which should fix that situation, there is a PR in the work waiting for review logstash-plugins/logstash-output-http#19 |
Thinking about just using the exec output with a curl call in it as a temporary fix |
@naneau If you can give a shot with the PR and see if it fixes your issue that would be awesome. |
@ph is there an easy way to do this in an existing logstash install? |
@naneau I think the easiest way would be to clone the repository and build the gem. # need to be run under a jruby environement, you can use rbenv/rvm for that
gem build logstash-output-http.gemspec
# In the logstash installation
bin/plugin install path/to/logstash-output-http.gem
|
@naneau you can also use this logstash-plugins/logstash-output-slack#1, I haven't tested it and it is not released. But it's a specialized plugin for slack. I did not know it existed. |
@ph was using that but it seems to have broken in more recent LS versions. Server didn't have RVM available so haven't been able to test that gem separately either. Using an exec output to do what I want now. I'll see if I can test that PR you mentioned elsewhere later. |
@naneau we just released a new version for |
@ph can confirm, with the updated plugin, this problem no longer occurs. Thanks! |
@naneau thanks for confirming this, I will close this issue. |
+1 I also have same problem. Could I know when this change reflect to stable version? |
@ShinJJang this updated plugin will be part of logstash 2.0 |
@ph Thanks for reply! |
Hi!
I just upgraded from 1.4.1 to 1.5.3 – almost everything works perfectly, except my http output now fails with
OpenSSL::SSL::SSLError: Received fatal alert: handshake_failure
for all events. I tried Google and the IRC channel, but haven't been able to get to the bottom of this. (No idea if this is connected to #3657.)I'm using:
The output config:
The output is trying to connect to hooks.slack.com, but fails. I can connect ok from the host running logstash:
Here's a
--debug
log output:Please let me know if I can provide any other useful information!
The text was updated successfully, but these errors were encountered: