undefined method `write_nonblock' for OpenSSL::SSL::SSLSocket #19
Comments
|
Sorry for lazy question, but is it really worked with jruby-openssl 0.7.4? It could be from excon's update I think. Can you try this with jruby-openssl 0.7.4 again? That said, jruby-openssl + 1.9 does not support *_nonblock properly yet... |
|
The excon gem version did not change. I am using the newest version of excon and I can reproduce this problem by only swapping the jruby-openssl version. |
|
Just a little bump here-- I can confirm that downgrading from 0.7.6.1 to 0.7.4 fixes issues from this thread: excon/excon#106 |
|
@pehrlich +1 |
|
+1 |
|
Tested on version 0.7.7. The problem is still there. |
|
+1 |
ukinau
added a commit
to ukinau/fluent-plugin-elasticsearch
that referenced
this issue
Mar 22, 2020
Description of http_backend_excon_nonblock: - If http_backend_excon_nonblock is true, Farday create Excon instance with nonblocking option which perform http request in nonblocking fassion - If http_backend_excon_nonblock is false, Fardday create Excon instance with blocking option which perform http request in blocking fassion Special Note about http_backend_excon_nonblock: If user use jRuby, you need to consider to configure http_backend_excon_nonblock=false. Since you may experince some issue. - excon/excon#106 - jruby/jruby-ossl#19 But if user is not using jRuby, you'd better to configure http_backend_excon_nonblock=true to prvent fluent-plugine-elasticsearch from stucking Background: The older version of v1.0.0(latest as of 23 March 2020) in Fardday(https://github.com/lostisland/farada), When we use excon(https://github.com/excon/excon) as a adapter for https, Faraday force to configure Excon to disable nonblock due to following jRuby specific problem - excon/excon#106 - jruby/jruby-ossl#19 That's why currently when fluent-plugin-elasticsearch plugin connect to Elastic Search, If it use http, Farday generate Excon instance with nonblocking=true(default of Excon), but in the case of https, Farady generate Excon instance with nonblocking=falase This actually cause the problem making Farday HTTP Client stuck when SSL Server(Elastic Search in current context) stuck during SSL Handshake since Excon SSLSocket can not respecting to timeout, and rely on timeout of SSL::SSLSocket in Ruby Standard Library which have exaclty process-hang problem. That's why sometimes flusth_thread of fluent-plugin-elasticsearch got stuck when Elastic Search had something problem during SSL Session handling. Root cause of this problem is actually implementation of SSL::SSLSocket in Ruby Standard Library(https://redmine.ruby-lang.org/issues/15729), so better to fix Ruby side but it will take a time, and require ruby version up, so better to provide the way to perform workaround.
Merged
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I upgraded from jruby-openssl 0.7.4 to 0.7.6.1 I started getting this error when trying to do file uploads to amazon s3 using the fog gem:
https://gist.github.com/1694196
The text was updated successfully, but these errors were encountered: