Postgres Connection Issue via SSH

Summary

User reports a successful setup log for connecting Postgres via SSH, but the connection ultimately fails. They inquire if increasing the liveness probe timeout from 30 seconds might resolve the issue.


Question

Hi Team,
I am trying to connect a postgres destination to Postgres via SSH. Surprisingly, the log mentions that setup was successful.

2024-02-14 21:47:43 platform > 2024-02-14 21:47:43 INFO c.z.h.HikariDataSource(<init>):79 - HikariPool-1 - Starting...
2024-02-14 21:47:43 platform > 2024-02-14 21:47:43 INFO c.z.h.HikariDataSource(<init>):81 - HikariPool-1 - Start completed.
2024-02-14 21:47:51 platform > 2024-02-14 21:47:51 INFO c.z.h.HikariDataSource(close):349 - HikariPool-1 - Shutdown initiated...
2024-02-14 21:47:51 platform > 2024-02-14 21:47:51 INFO c.z.h.HikariDataSource(close):351 - HikariPool-1 - Shutdown completed.
2024-02-14 21:47:52 platform > 2024-02-14 21:47:52 INFO i.a.c.i.b.IntegrationRunner(runInternal):231 - Completed integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedDestination
2024-02-14 21:47:52 platform > 2024-02-14 21:47:52 INFO i.a.i.d.p.PostgresDestination(main):139 - completed destination: class io.airbyte.integrations.destination.postgres.PostgresDestination
2024-02-14 21:47:53 INFO i.a.w.p.ExitCodeWatcher(persistExitCode):117 - Received exit code 0 for pod ion-postgres-check-96167fbc-3b66-44b8-87f4-05b9850e6655-0-sulwz
2024-02-14 21:47:53 platform > (pod: airbyte / ion-postgres-check-96167fbc-3b66-44b8-87f4-05b9850e6655-0-sulwz) - Closed all resources for pod
2024-02-14 21:47:53 platform > Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@280e2109[status=succeeded,message=<null>,additionalProperties={}]
2024-02-14 21:47:53 INFO i.a.c.t.HeartbeatUtils(withBackgroundHeartbeat):64 - Stopping temporal heartbeating...
2024-02-14 21:47:53 platform > 
2024-02-14 21:47:53 INFO i.a.c.t.HeartbeatUtils(withBackgroundHeartbeat):73 - Temporal heartbeating stopped.
2024-02-14 21:47:53 platform > ----- END CHECK -----
2024-02-14 21:47:53 platform > ```
Yet, the connection to postgres failed with error like this. We’ve liveness probe set to 30s. Do you think that should be higher than that?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1707947702723139) if you want
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
['postgres', 'ssh', 'connection', 'liveness-probe', 'error']
</sub>