MSSQL: Error: HikariPool-1 - Connection is not available

Connector Questions & Issues
,
1

Hello we have an issue with the MSSQL connector. We think is due to TLS?

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Debian
  • Memory / Disk: 1TB / 8 GB RAM / 2VCPU
  • Deployment: Docker
  • Airbyte Version: 0.39.13-alpha
  • Source name/version: 0.39.13-alpha
  • Destination name/version: MSSQL
  • Step: Issue happening setting a new source
  • Description: Error setting the source:

Could not connect with provided configuration. Error: HikariPool-1 - Connection is not available, request timed out after 30003ms.

Logs:

2022-06-28 08:21:23 INFO i.a.w.t.TemporalAttemptExecution(get):108 - Docker volume job log path: /tmp/workspace/2a8719d1-228f-47b2-b24d-aa7ce17bb473/0/logs.log
2022-06-28 08:21:23 INFO i.a.w.t.TemporalAttemptExecution(get):113 - Executing worker wrapper. Airbyte version: 0.39.13-alpha
2022-06-28 08:21:23 INFO i.a.c.i.LineGobbler(voidCall):82 - Checking if airbyte/source-mssql:0.4.1 exists…
2022-06-28 08:21:23 INFO i.a.c.i.LineGobbler(voidCall):82 - airbyte/source-mssql:0.4.1 was found locally.
2022-06-28 08:21:23 INFO i.a.w.p.DockerProcessFactory(create):108 - Creating docker job ID: 2a8719d1-228f-47b2-b24d-aa7ce17bb473
2022-06-28 08:21:23 INFO i.a.w.p.DockerProcessFactory(create):163 - Preparing command: docker run --rm --init -i -w /data/2a8719d1-228f-47b2-b24d-aa7ce17bb473/0 --log-driver none --name source-mssql-check-2a8719d1-228f-47b2-b24d-aa7ce17bb473-0-xpomw --network host -v airbyte_workspace:/data -v /tmp/airbyte_local:/local -e WORKER_JOB_ATTEMPT=0 -e WORKER_CONNECTOR_IMAGE=airbyte/source-mssql:0.4.1 -e AIRBYTE_ROLE= -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_VERSION=0.39.13-alpha -e WORKER_JOB_ID=2a8719d1-228f-47b2-b24d-aa7ce17bb473 airbyte/source-mssql:0.4.1 check --config source_config.json
2022-06-28 08:21:24 ERROR i.a.c.i.LineGobbler(voidCall):82 - SLF4J: Class path contains multiple SLF4J bindings.
2022-06-28 08:21:24 ERROR i.a.c.i.LineGobbler(voidCall):82 - SLF4J: Found binding in [jar:file:/airbyte/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2022-06-28 08:21:24 ERROR i.a.c.i.LineGobbler(voidCall):82 - SLF4J: Found binding in [jar:file:/airbyte/lib/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2022-06-28 08:21:24 ERROR i.a.c.i.LineGobbler(voidCall):82 - SLF4J: See SLF4J Error Codes for an explanation.
2022-06-28 08:21:24 ERROR i.a.c.i.LineGobbler(voidCall):82 - SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]

2

Hey @miguelpuiggarcia,
Your logs are not complete, could you attach the full sync logs please?
Could you please also upgrade your source-MSSQL connector to the latest version (0.4.5)?

To troubleshoot this error I would suggest trying to connect to your MSSQL instance from your Airbyte instance with mssql-cli . This is probably a connectivity issue due to networking set up or TLS indeed.

3

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.