Setting up YugabyteDB as destination

Hi, I am setting up YugabyteDB as source, but the connection cannot be estabished. This is the error I’m getting.

2023-03-17 14:01:33 INFO i.a.w.p.DockerProcessFactory(create):130 - Creating docker container = destination-yugabytedb-check-6bc42e07-15f1-45fe-b43a-d9717200adb6-0-uexlh with resources io.airbyte.config.ResourceRequirements@1f65b8be[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=] and allowedHosts null
2023-03-17 14:01:33 INFO i.a.w.p.DockerProcessFactory(create):175 - Preparing command: docker run --rm --init -i -w /data/6bc42e07-15f1-45fe-b43a-d9717200adb6/0 --log-driver none --name destination-yugabytedb-check-6bc42e07-15f1-45fe-b43a-d9717200adb6-0-uexlh --network host -v airbyte_workspace:/data -v /tmp/airbyte_local:/local -e DEPLOYMENT_MODE=OSS -e STRICT_COMPARISON_NORMALIZATION_WORKSPACES= -e WORKER_CONNECTOR_IMAGE=airbyte/destination-yugabytedb:0.1.0 -e AUTO_DETECT_SCHEMA=true -e LAUNCHDARKLY_KEY= -e SOCAT_KUBE_CPU_REQUEST=0.1 -e STRICT_COMPARISON_NORMALIZATION_TAG=strict_comparison2 -e SOCAT_KUBE_CPU_LIMIT=2.0 -e USE_STREAM_CAPABLE_STATE=true -e FIELD_SELECTION_WORKSPACES= -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE= -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e FEATURE_FLAG_CLIENT= -e AIRBYTE_VERSION=0.42.0 -e WORKER_JOB_ID=6bc42e07-15f1-45fe-b43a-d9717200adb6 airbyte/destination-yugabytedb:0.1.0 check --config source_config.json
2023-03-17 14:01:33 INFO i.a.w.i.VersionedAirbyteStreamFactory(create):107 - Reading messages from protocol version 0.2.0
2023-03-17 14:01:34 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - starting destination: class io.airbyte.integrations.destination.yugabytedb.YugabytedbDestination
2023-03-17 14:01:34 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - integration args: {check=null, config=source_config.json}
2023-03-17 14:01:34 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - Running integration: io.airbyte.integrations.destination.yugabytedb.YugabytedbDestination
2023-03-17 14:01:34 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - Command: CHECK
2023-03-17 14:01:34 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - Integration config: IntegrationConfig{command=CHECK, configPath='source_config.json', catalogPath='null', statePath='null'}
2023-03-17 14:01:34 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):165 - Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2023-03-17 14:01:34 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):165 - Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2023-03-17 14:01:34 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - HikariPool-1 - Starting...
2023-03-17 14:01:34 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - HikariPool-1 - Start completed.
2023-03-17 14:02:35 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - HikariPool-1 - Shutdown initiated...
2023-03-17 14:02:36 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - HikariPool-1 - Shutdown completed.
2023-03-17 14:02:36 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - Completed integration: io.airbyte.integrations.destination.yugabytedb.YugabytedbDestination
2023-03-17 14:02:36 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - completed destination: class io.airbyte.integrations.destination.yugabytedb.YugabytedbDestination
2023-03-17 14:02:36 INFO i.a.w.g.DefaultCheckConnectionWorker(run):120 - Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@556cbef3[status=failed,message=State code: 08001; Message: The connection attempt failed.]
2023-03-17 14:02:36 INFO i.a.w.t.TemporalAttemptExecution(get):169 - Stopping cancellation check scheduling...
2023-03-17 14:02:36 INFO i.a.c.i.LineGobbler(voidCall):149 - 
2023-03-17 14:02:36 INFO i.a.c.i.LineGobbler(voidCall):149 - ----- END CHECK -----
2023-03-17 14:02:36 INFO i.a.c.i.LineGobbler(voidCall):149 - 

Please help me resolve this error. Thanks.

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

Hi! Could you please give me bit more info:

  1. Airbyte version
  2. Connector versions
  3. Any sync logs

Thanks!