<@U04S8PLJWMT> trying to set potsgres source on Ku...
# ask-ai
a
@kapa.ai trying to set potsgres source on Kubernetes installation but getting the following 2025-11-25 162827 INFO 2025-11-25 162827 info 2025-11-25 162827 INFO 2025-11-25 162827 info Transitioning workload to running state 2025-11-25 162827 INFO 2025-11-25 162827 info ----- START CHECK ----- 2025-11-25 162827 INFO 2025-11-25 162827 info 2025-11-25 162827 INFO 2025-11-25 162827 info Workload successfully transitioned to running state 2025-11-25 162848 INFO 2025-11-25 162848 info Connector exited, processing output 2025-11-25 162848 INFO 2025-11-25 162848 info Output file jobOutput.json found 2025-11-25 162848 INFO 2025-11-25 162848 info Connector exited with exit code 0 2025-11-25 162848 INFO 2025-11-25 162848 info Reading messages from protocol version 0.2.0 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.i.s.p.PostgresSource(main):750 starting source: class io.airbyte.integrations.source.postgres.PostgresSource 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.c.i.b.IntegrationCliParser$Companion(parseOptions):144 integration args: {check=null, config=/config/connectionConfiguration.json} 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.c.i.b.IntegrationRunner(runInternal):130 Running integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedSource 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.c.i.b.IntegrationRunner(runInternal):131 Command: CHECK 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.c.i.b.IntegrationRunner(runInternal):132 Integration config: IntegrationConfig{command=CHECK, configPath='/config/connectionConfiguration.json', catalogPath='null', statePath='null'} 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword group - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword always_show - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword pattern_descriptor - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword multiline - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword display_type - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword min - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword max - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 WARN 2025-11-25 162848 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword groups - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.c.i.b.s.SshTunnel$Companion(getInstance):424 Starting connection with method: NO_TUNNEL 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.i.s.p.PostgresUtils(isCdc):70 using CDC: false 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.i.s.p.PostgresSource(toSslJdbcParamInternal):976 DISABLED toSslJdbcParam disable 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main c.z.h.HikariDataSource(<init>):79 HikariPool-1 - Starting... 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main c.z.h.HikariDataSource(<init>):81 HikariPool-1 - Start completed. 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main c.z.h.HikariDataSource(close):349 HikariPool-1 - Shutdown initiated... 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main c.z.h.HikariDataSource(close):351 HikariPool-1 - Shutdown completed. 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.c.i.b.IntegrationRunner(runInternal):224 Completed integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedSource 2025-11-25 162848 INFO 2025-11-25 162848 info INFO main i.a.i.s.p.PostgresSource(main):752 completed source: class io.airbyte.integrations.source.postgres.PostgresSource 2025-11-25 162848 INFO 2025-11-25 162848 info Checking for optional control message... 2025-11-25 162848 INFO 2025-11-25 162848 info Optional control message not found. Skipping... 2025-11-25 162849 INFO 2025-11-25 162849 info Writing output of decd338e-5647-4c0b-adf4-da0e75f5a750_436d097d-c41f-4775-bc3f-186803310e78_0_check to the doc store 2025-11-25 162849 INFO 2025-11-25 162849 info Marking workload decd338e-5647-4c0b-adf4-da0e75f5a750_436d097d-c41f-4775-bc3f-186803310e78_0_check as successful 2025-11-25 162849 INFO 2025-11-25 162849 info 2025-11-25 162849 INFO 2025-11-25 162849 info Deliberately exiting process with code 0. 2025-11-25 162849 INFO 2025-11-25 162849 info ----- END CHECK ----- 2025-11-25 162849 INFO 2025-11-25 162849 info what is the issue?
k
From the logs you shared, the Postgres source CHECK job finishes successfully with exit code 0, and the worker marks the workload as successful: -
Connector 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).
a
@kapa.ai this is the UI error: Failed to save Postgres due to the following error: Message: HikariPool-1 - Connection is not available, request timed out after 10002ms (total=0, active=0, idle=0, waiting=0)
k
A message from kapa.ai
The error means the connector could not get a DB connection from HikariCP at all (
total=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.