Is this your first time deploying Airbyte: Yes OS Version / Instance: t3.medium Memory / Disk: - Deployment: Kubernetes Airbyte Version: 0.29.21-alpha Source name/version: - Destination name/version: Redshift 0.3.14 Step: Have entered input (database hose, port, username ...) on setup destination page & clicked the

Setup destination

button. The process

Testing connection

is running Description: I am trying to setup Redshift destination. The cluster IP is whitelisted for Redshift access. The

Testing connection

process keeps running for 10 mins (maybe more) and then stops with this message.

There are no logs that are printed.

Side question - How do I checks logs? the kubectl logs command does not give enough information

Hey Kriti, you can check the log by looking at the worker pod. The job pods stream their logs to the worker pod where it’s centrally reported

if you log the worker pod while running the test job (clicking on set up destination), you should be able to see the error that happens

👍 trying that. Can you tell me where the logs are persisted? I assume somewhere on minio

if you have the default setup, it would be on minio

we support GCS and S3 if you wish to customise it

Good to know about GCS & S3. Right now, I have default setup. Do you know where on Minio? Approx location?

There should be a minio pod in the deployment and it should contain a single bucket with the same name as the

S3_LOG_BUCKET

env variable. I don’t have the instruction to acesss minio off the top of my head but if you google if you should get it

alternatively, I think if you go to the UI and download the scheduler logs, the error will show up there

Thank you for the above, I will check. I logged into the pod:

> kubectl exec -it pod/on-redshift-worker-7d499bbf-d029-468d-8cf5-5286443d8682-0-hiigv -n airbyte -- /bin/bash

Got the below :

Defaulted container "main" out of: main, relay-stdout, relay-stderr, call-heartbeat-server, init (init)
root@on-redshift-worker-7d499bbf-d029-468d-8cf5-5286443d8682-0-hiigv:/config# command terminated with exit code 137

Exit code 137 is Out of memory error. Any idea how I can debug this further?

I think this is related to the memory capacity. If you have the access to EKS cluster can you confirm what's the error shown there in te UI ?

I am running 2 t3.medium nodes, and only the base airbyte setup is running and no connectors.

Let me check if there is anything on the EKS UI

@Kriti (Postman) any change scale up your cluster?