@kapa.ai: Database is not ready yet. Please wait a moment, it might still be initializing...

That log line means an Airbyte component (often

airbyte-bootloader

or

airbyte-server

) is repeatedly trying and failing to connect to its PostgreSQL database; it keeps retrying and prints “Database is not ready yet. Please wait a moment, it might still be initializing…”. [Failed external DB; abctl db failure] From the knowledge sources, the most common root causes and checks are: 1. Database pod/container not actually reachable ◦ On Kubernetes, confirm the DB pod and service are healthy and reachable from the bootloader pod: [bootloader pod failed]

kubectl get pods -n airbyte | grep db
       kubectl logs -n airbyte <airbyte-db-pod-name>

       kubectl get svc airbyte-db-svc -n airbyte
       kubectl get endpoints airbyte-db-svc -n airbyte

◦ If using an external DB, verify hostname/port, firewall/network policies, and that PostgreSQL is accepting TCP connections. [bootloader pod failed; Failed external DB] 2. Wrong or conflicting DB configuration ◦ For Docker deployments, ensure you’re using the correct env vars: ▪︎ If you want a single DB for configs and jobs, set only:

DATABASE_USER

,

DATABASE_PASSWORD

,

DATABASE_HOST

,

DATABASE_PORT

,

DATABASE_DB

,

DATABASE_URL

and remove any

CONFIG_DATABASE_*

overrides that might point elsewhere. [Compose up DB not ready] ◦ When pointing to an external DB, double‑check

DATABASE_URL

(SSL flags, host, port, DB name). A mismatch (e.g., SSL required but DB not configured for SSL) can cause repeated “not ready yet” messages. [Unable to connect external DB] 3. Connection refused / DB not listening ◦ If logs show

Connection refused

to

airbyte-db-svc:5432

or similar, the DB process is not listening or not reachable on that address/port. [Colima Postgres issue; abctl db failure] ◦ Fix by ensuring PostgreSQL is running, listening on the right interface, and that the service/port mapping is correct. 4. Connection limits / pool settings ◦ In some external Postgres setups (e.g., Cloud SQL), Airbyte can hit

max_connections

, which makes the DB appear “not ready” from Airbyte’s perspective. Lowering

SQL_MAX_CONNS

and

SQL_MAX_IDLE_CONNS

in Airbyte and/or increasing

max_connections

on the DB resolved this in one case. [Server external DB backend] If you share: • your deployment type (Docker / Kubernetes / abctl), • whether you use the bundled DB or an external Postgres, • and the surrounding error lines (especially any

Connection refused

or

PSQLException

), I can map your situation more precisely to the patterns above from the knowledge sources. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.