@kapa.ai:

i.a.b.ApplicationKt(main):28 - Unable to bootstrap Airbyte environment.

io.airbyte.db.init.DatabaseInitializationException: Database availability check failed.

Those log lines mean Airbyte’s bootloader couldn’t connect to its PostgreSQL metadata database long enough for the startup “database availability check” to succeed. This is the same failure pattern shown in several issues where the bootloader repeatedly logs that the DB is not ready, then errors with

DatabaseInitializationException

/

DatabaseCheckException

and shuts down.[abctl db error; Colima postgres] From the available sources, the concrete things to check are: 1. Is the Postgres service reachable? ◦ For local/`abctl` or Docker: confirm the

airbyte-db

(or

airbyte-db-svc

) container is running and listening on port 5432, and that nothing else is already bound to that port (otherwise Postgres fails to start and Airbyte can never connect).[db port in use] ◦ For Kubernetes/Helm: ensure the

airbyte-db

pod is

Running

and the service name/port in Airbyte’s env vars matches (e.g.

airbyte-db-svc:5432

). Connection‑refused errors to

airbyte-db-svc:5432

indicate the DB pod isn’t accepting connections yet or at all.[abctl db error; Colima postgres] 2. If you’re using an external Postgres (RDS, Aurora, etc.): ◦ Verify network access (security groups / firewall / VPC) so the Airbyte deployment can reach the DB host:port. Several reports show timeouts when the external RDS instance is not reachable.[helm external rds] ◦ Double‑check the DB URL and credentials in your configuration (

DATABASE_*

or

CONFIG_DATABASE_*

env vars, or Helm values). A misconfigured

CONFIG_DATABASE_URL

pointing to a cloud DB or wrong host can cause the “database not ready” loop.[db not ready env] 3. Environment variables for the DB: ◦ If you want to use a single local DB for both configs and jobs, the guidance is to remove the

CONFIG_DATABASE_*

variables and only set: ▪︎

DATABASE_USER

▪︎

DATABASE_PASSWORD

▪︎

DATABASE_HOST

▪︎

DATABASE_PORT

▪︎

DATABASE_DB

▪︎

DATABASE_URL

(as

jdbc:postgresql://${DATABASE_HOST}:${DATABASE_PORT}/${DATABASE_DB}

, without username/password).[db not ready env] 4. Look at the database container/pod logs, not just bootloader: ◦ In all similar cases, the root cause is visible in the Postgres logs (port already in use, crash loop, permission/bind issues, etc.).[db port in use] Because your snippet only shows the final error and not the preceding lines (host, port, or specific SQL/connection error), the knowledge sources don’t let me pinpoint a single root cause. They do, however, consistently indicate that this error is always due to Airbyte being unable to open a TCP connection to its Postgres instance or the DB not starting correctly. If you paste: • the preceding 20–30 lines around that error from

airbyte-bootloader

/

airbyte-server

, and • the logs from your Postgres container/pod, I can map them more precisely to one of the documented patterns above. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.