Aviad Deri
11/26/2025, 5:58 AMkapa.ai
11/26/2025, 5:58 AMConnector exited with exit code 0 - Marking workload ... _check as successful - Deliberately exiting process with code 0. - ----- END CHECK ----- The warnings like Unknown keyword order, airbyte_secret, etc. are about JSON‑schema validation metadata and are expected; they do not indicate a failure (similar warnings appear in other Airbyte logs). [[Postgres source forum](https://discuss.airbyte.io/t/801)] The attached knowledge sources don’t contain any error pattern or troubleshooting entry that would indicate a problem based on these lines; in particular, there’s no mention of a failure related to these warnings or to your log sequence. [[Postgres troubleshooting](https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting); [Cloud SQL Postgres troubleshooting](https://docs.airbyte.com/integrations/sources/postgres/cloud-sql-postgres#limitations--troubleshooting)] So, based on the available information: - The connector appears to connect and close the pool cleanly. - The CHECK operation is reported as successful. - No explicit error is shown in the provided excerpt. If you are still seeing a failure in the UI (e.g., “connection failed” or “cannot save source”), the knowledge sources here don’t provide enough detail to explain it. In that case you’d need to: 1. Share the UI error message or status you’re seeing. 2. Include any error log lines after this CHECK block (stack traces or ERROR entries).Aviad Deri
11/26/2025, 5:59 AMkapa.ai
11/26/2025, 5:59 AMkapa.ai
11/26/2025, 6:00 AMtotal=0, active=0, idle=0), i.e. no successful connection to Postgres was ever established. This pattern shows up when: - The hostname/port is wrong or unreachable (network / DNS / firewall / security‑group). [[Failed external Postgres](https://discuss.airbyte.io/t/1264); [abctl airbyte-db](https://github.com/airbytehq/airbyte/issues/54199)] - Postgres is refusing connections or not listening for TCP/IP. [[Failed external Postgres](https://discuss.airbyte.io/t/1264)] - A remote Postgres service (RDS, etc.) is not correctly whitelisting Airbyte’s IP. [[MSSQL timeout](https://discuss.airbyte.io/t/1839)] In the examples from the knowledge sources, the fixes were always on the network/DB side, not inside Airbyte: 1. Verify basic connectivity from the Airbyte pod Exec into a worker/server pod and test with psql (or `nc`/`telnet`) to your DB host and port. If this fails, it’s a network/DNS or firewall/Security Group issue, not Airbyte. [[Failed external Postgres](https://discuss.airbyte.io/t/1264)] 2. Check Kubernetes networking configuration - If Postgres is outside the cluster (RDS, other VPC, on‑prem), confirm: - Correct hostname and port. - Security groups / firewalls allow inbound from the cluster nodes or NAT IPs. - Any VPN / peering is up. Similar issues in RDS setups show as Hikari timeout + Postgres “connection refused” or “host not found”. [[Failed external Postgres](https://discuss.airbyte.io/t/1264); [DNS / Hikari error](https://discuss.airbyte.io/t/3899)] 3. Confirm DB is accepting TCP/IP connections On the Postgres side: - listen_addresses includes the requested IP/`0.0.0.0`. - pg_hba.conf allows the Airbyte source IP range. 4. Double‑check source configuration in the UI - Host, port, DB name, user, password. - SSL mode: match your DB (disabled vs required). Mis‑configurations here lead to the same Hikari timeout signature because no connection can be created. [[Postgres source connection](https://discuss.airbyte.io/t/1640)] The knowledge sources do not show any case where this specific Hikari timeout is caused by an internal Airbyte bug; in all referenced threads and issues it was due to connectivity or DB configuration outside Airbyte. If you can share the exact DB host type (in‑cluster, RDS, etc.) and whether psql from inside the pod works, that’s usually the quickest way to pinpoint which of the above is failing.