Redshift destination setup keeps timing out

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: MacOS. But deloyed in an AWS EC2 instance.
  • Deployment: Docker
  • Destination name/version: Redshift
  • Step: The issue is happening during creating a new destination.
  • Description: Remove this with the description of your problem.

Here are the the last lines of the failed logs:

2023-03-16 11:36:01 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):165 - WARN o.a.s.c.k.StaticServerKeyVerifier(handleAcceptance):59 Server at /52.57.91.5:22 presented unverified EC key: SHA256:CqK69dmRuOH9qda+NMzZ/j2fk7zMk4x96RTUtM4i3lI
2023-03-16 11:36:01 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - INFO i.a.i.b.s.SshTunnel(openTunnel):367 Established tunneling session to ismael-redshift-cluster.c4sahjrlvjps.eu-central-1.redshift.amazonaws.com:5439. Port forwarding started on /127.0.0.1:42753 
2023-03-16 11:36:01 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - INFO i.a.i.d.s.S3DestinationConfig(createS3Client):238 Creating S3 client...
2023-03-16 11:36:02 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - INFO i.a.i.d.s.S3BaseChecks(testIAMUserHasListObjectPermission):131 Started testing if IAM user can call listObjects on the destination bucket
2023-03-16 11:36:02 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - INFO i.a.i.d.s.S3BaseChecks(testIAMUserHasListObjectPermission):134 Finished checking for listObjects permission
2023-03-16 11:36:02 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - INFO c.z.h.HikariDataSource(<init>):80 HikariPool-1 - Starting...
2023-03-16 11:36:02 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - INFO c.z.h.HikariDataSource(<init>):82 HikariPool-1 - Start completed.
2023-03-16 11:37:02 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - INFO c.z.h.HikariDataSource(close):350 HikariPool-1 - Shutdown initiated...
2023-03-16 11:38:02 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):165 - WARN c.z.h.p.HikariPool(shutdown):218 Timed-out waiting for add connection executor to shutdown
2023-03-16 11:38:02 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):168 - INFO c.z.h.HikariDataSource(close):352 HikariPool-1 - Shutdown completed.
2023-03-16 11:38:02 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):165 - WARN o.a.s.c.c.ClientChannelPendingMessagesQueue(operationComplete):200 operationComplete(ClientChannelPendingMessagesQueue[channel=TcpipClientChannel[id=0, recipient=-1]-ClientSessionImpl[ec2-user@/52.57.91.5:22], open=false]) got SshException[Closed] signal while queue is closed
2023-03-16 11:38:02 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):165 - WARN o.a.s.c.u.l.LoggingUtils(warn):610 Failed (SshException) to open channel for session=MinaSession[local=/127.0.0.1:42753, remote=/127.0.0.1:60484]: Closed

It doesnt specify much, besides that the connection timed out.

2

This was solved when specifically allowing port 5439. Even though the security group pretty much allows all traffic.

3

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

1 Like