Error sql server to elasticsearch TLS10

I am trying to communicate with sqlserver with logstash,
I used : java version "11.0.14" 2022-01-18 LTS
Myfile.conf

input {

jdbc 

jdbc_driver_library => "C:\Users\Lenovo\Desktop\ELK\logstash-8.1.0\logstash-core\lib\jars\mssql-jdbc-10.2.1.jre8.jar"
#Placed my mssql-jdbc-7.4.1.jre8 JRE file in logstash ..\logstash-core\lib\jars\

jdbc_driver_class => "com.microsoft.sqlserver.jdbc.SQLServerDriver"

jdbc_connection_string => "jdbc:sqlserver://localhost:1433;databaseName=sales;integratedSecurity=true;"

jdbc_user => "DESKTOP-72D32P6\Lenovo"

statement => "SELECT * FROM Janvier"
}

}

output {
  stdout  { }
}

i get this error when i execute logstash -f sql.conf
[2022-06-15T10:04:50,181][WARN ][logstash.inputs.jdbc ][main][e19f080911532a0b3a2b7a97c8a03964c2d0dd49cbfd57c4dec8d41439afebcf] Exception when executing JDBC query {:exception=>Sequel::DatabaseConnectionError, :message=>"Java::ComMicrosoftSqlserverJdbc::SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:08c85704-17c9-4355-83fd-abdef1e01cf9", :cause=>"com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:08c85704-17c9-4355-83fd-abdef1e01cf9"}

TLSv1 and TLSv1.1 are disabled by Java by default. The settings are in java.security.

Look for the disabled algorithm TLSv1 in java.security and remove it. If using a container, mount your custom java.security file to that file location inside the container to replace it.

1 Like

yes it worked thank you.
but i have a new error


knowing that my .conf file looks like this.

input {

jdbc 

jdbc_driver_library =>"C:\Users\Lenovo\Desktop\ELK\logstash-8.1.0\logstash-core\lib\jars\msi-mssql-jdbc-2.0.3.jar"
#Placed my mssql-jdbc-7.4.1.jre8 JRE file in logstash ..\logstash-core\lib\jars\

jdbc_driver_class => "com.microsoft.sqlserver.jdbc.SQLServerDriver"

jdbc_connection_string => "jdbc:sqlserver://localhost:1433;databaseName=sales;integratedSecurity=false;"

jdbc_user => "DESKTOP-72D32P6\Lenovo"

statement => "SELECT * FROM Janvier"
}

}

output {
  stdout  { }
}

Sorry, I don't know how to read that error message. It is a screenshot, so I cannot copy-and-paste the error text into Google search or Google translate. Screenshots are good, but a copy of the error text is ideal to accompany the screenshot.

sorry, I thought it was clearer but I wouldn't do it again ,

.logstash.java_pipeline.inputworker(C:/Users/Lenovo/Desktop/ELK/logstash-8.1.0/logstash-core/lib/logstash/java_pipeline.rb:409)", "C_3a_.Users.Lenovo.Desktop.ELK.logstash_minus_8_dot_1_dot_0.logstash_minus_core.lib.logstash.java_pipeline.start_input(C:/Users/Lenovo/Desktop/ELK/logstash-8.1.0/logstash-core/lib/logstash/java_pipeline.rb:400)", "org.jruby.RubyProc.call(org/jruby/RubyProc.java:318)", "java.lang.Thread.run(java/lang/Thread.java:829)"]}
[2022-06-15T18:04:48,240][WARN ][logstash.inputs.jdbc     ][main][e19f080911532a0b3a2b7a97c8a03964c2d0dd49cbfd57c4dec8d41439afebcf] Exception when executing JDBC query {:exception=>Sequel::DatabaseConnectionError, :message=>"Java::ComMicrosoftSqlserverJdbc::SQLServerException: Échec de l'ouverture de session de l'utilisateur ''. ClientConnectionId:d49e4a16-7daf-4d95-8969-38f7bf4ab427", :cause=>"com.microsoft.sqlserver.jdbc.SQLServerException: Échec de l'ouverture de session de l'utilisateur ''. ClientConnectionId:d49e4a16-7daf-4d95-8969-38f7bf4ab427"}
[2022-06-15T18:04:48,787][INFO ][logstash.javapipeline    ][main] Pipeline terminated {"pipeline.id"=>"main"}
[2022-06-15T18:04:49,041][INFO ][logstash.pipelinesregistry] Removed pipeline from registry successfully {:pipeline_id=>:main}
[2022-06-15T18:04:49,112][INFO ][logstash.runner          ] Logstash shut down.

Check the SQL server logs. The reason for the login failure is not returned to the client, for security reasons, but is logged on the server side.

1 Like

Capture d’écran 2022-06-15 053307
how can i visualize the SQL server logs. thanks

That is an SQL Server question which I cannot answer. You could check the documentation here.

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