SSL Error when using SSL with TCP output plugin

Hi,

I'm trying to use ssl for tcp output plugin for logstash. The workflow goes to a nginx-proxy ssl termination point for logstash that will forward the logs to a logstash pod that takes in tcp input.
My output part for logstash looks like this:
output {
tcp {
host => "172.20.45.41"
port => 30002
ssl_enable => true
ssl_verify => false
ssl_cacert => "/usr/share/logstash/ca/ca.crt.pem"
ssl_cert => "/usr/share/ssl/client.crt"
ssl_key => "/usr/share/ssl/client.key"
codec => json_lines
}
}
The client.crt and key have been created from the client cert/private key pair in the nginx-proxy server.

Has anyone seen an error like this?
SSL Error {:exception=>#<OpenSSL::SSL::SSLError: Socket closed>, :backtrace=>["org/jruby/ext/openssl/SSLSocket.java:266:in connect'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-tcp-5.0.3/lib/logstash/outputs/tcp.rb:179:inblock in connect'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/try.rb:79:in block in try'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/try.rb:95:inblock in try'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/try.rb:20:in each'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/try.rb:91:intry'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/try.rb:123:in try'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-tcp-5.0.3/lib/logstash/outputs/tcp.rb:174:inconnect'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-tcp-5.0.3/lib/logstash/outputs/tcp.rb:151:in block in register'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-codec-json_lines-3.0.6/lib/logstash/codecs/json_lines.rb:48:inencode'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-tcp-5.0.3/lib/logstash/outputs/tcp.rb:201:in receive'", "/usr/share/logstash/logstash-core/lib/logstash/outputs/base.rb:89:inblock in multi_receive'", "org/jruby/RubyArray.java:1734:in each'", "/usr/share/logstash/logstash-core/lib/logstash/outputs/base.rb:89:inmulti_receive'", "org/logstash/config/ir/compiler/OutputStrategyExt.java:114:in multi_receive'", "org/logstash/config/ir/compiler/AbstractOutputDelegatorExt.java:97:inmulti_receive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:373:in block in output_batch'", "org/jruby/RubyHash.java:1343:ineach'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:372:in output_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:324:inworker_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:286:in `block in start_workers'"]}

Found the cause last week; it was because of the certificate I was using was being revoked by CRL in nginx proxy.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.