Fully managed cloud. 30-day FREE full featured trial. Start Now
cancel
Showing results for 
Search instead for 
Did you mean: 

Exasol in GitHub Actions Returns SSL_ERROR_SYSCALL Even with SSLCertificate=SSL_VERIFY_NONE

theory
SQL-Fighter

I'm attempting to use the Exasol 7.1 ODBC library to connect to a docker-db container in GitHub actions. I think Exasol is running fine and the client is configured, but I'm getting this error in the build:

# DBI connect('EXAHOST=127.0.0.1;EXAPORT=49153;Driver=Exasol;SSLCertificate=SSL_VERIFY_NONE','sys',...) failed: [EXASOL][EXASolution driver]Error in SSL_connect. SSL error code: 5 = SSL_ERROR_SYSCALL (SQL-HY000) [state was HY000 now 01002]
 
Note the use of`SSLCertificate=SSL_VERIFY_NONE in the connection string. What have I overlooked here? The GitHub action workflow is here, and uses this script to configure the client libraries. TIA!
14 REPLIES 14

exa-MichaelT
Team Exasol
Team Exasol

This looks like a network problem. The error if the certificate is wrong is different. You can double check the connection using EXAplus or some other JDBC application with Exasol JDBC, like Dbeawer.
If you are using a docker container you can also try to establish the connection locally in the container first. 

exa-MathiasHo
Exasol Alumni

Hi @theory, just checking. Did you manage to solve the issue? 

theory
SQL-Fighter

No; I opened this issue with the docker-db repo to see if the maintainers there have any ideas.

theory
SQL-Fighter

I'm using the Exasol ODBC driver with unixODBC, set up in this script. It works fine for Exasol 7, but not 6. When I use the Exasol 6 ODBC I get the network error, which is weird. When I use the Exasol 7.2 ODBC driver I get the TLS error.

theory
SQL-Fighter

Bit of follow-up. Thanks to a comment from @littleK0i on an issue I opened in the exasol/docker-db project I learned that the Exasol 6 images listen on port 8888 instead of 8563. That was just want I needed to know to fix the issue in sqitchers/sqitch@a28daae.