pod airbyte-bootloader failed

[ma-gk]

Helm Chart Version

2.0.19

What step the error happened?

On deploy

Relevant information

• I am not using external DB still facing this issue
  org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  at org.jooq_3.19.18.POSTGRES.debug(Unknown Source)
  at org.jooq.impl.DataSourceConnectionProvider.acquire(DataSourceConnectionProvider.java:90)
  at org.jooq.impl.DefaultExecuteContext.connection(DefaultExecuteContext.java:651)
  at org.jooq.impl.AbstractQuery.connection(AbstractQuery.java:388)
  at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:308)
  at org.jooq.impl.AbstractResultQuery.fetchLazy(AbstractResultQuery.java:301)
  at org.jooq.impl.AbstractResultQuery.fetchLazyNonAutoClosing(AbstractResultQuery.java:322)
  at org.jooq.impl.SelectImpl.fetchLazyNonAutoClosing(SelectImpl.java:3256)
  at org.jooq.impl.ResultQueryTrait.fetchOne(ResultQueryTrait.java:509)
  at org.jooq.impl.Tools.attach(Tools.java:1687)
  at org.jooq.impl.DefaultDSLContext.fetchOne(DefaultDSLContext.java:5019)
  at org.jooq.impl.DefaultDSLContext.lambda$fetchValue$55(DefaultDSLContext.java:5039)
  at org.jooq.impl.Tools.attach(Tools.java:1687)
  at org.jooq.impl.DefaultDSLContext.fetchValue(DefaultDSLContext.java:5039)
  at org.jooq.impl.DefaultDSLContext.fetchValue(DefaultDSLContext.java:5058)
  at org.jooq.impl.DefaultDSLContext.fetchExists(DefaultDSLContext.java:5150)
  at io.airbyte.db.check.DatabaseAvailabilityCheck$DefaultImpls.isDatabaseConnected$lambda$6$lambda$4(DatabaseAvailabilityCheck.kt:98)
  at io.airbyte.db.Database.query(Database.kt:13)
  at io.airbyte.db.check.DatabaseAvailabilityCheck$DefaultImpls.isDatabaseConnected$lambda$6(DatabaseAvailabilityCheck.kt:97)
  at io.airbyte.db.check.DatabaseAvailabilityCheck$DefaultImpls.check(DatabaseAvailabilityCheck.kt:71)
  at io.airbyte.db.check.ConfigsDatabaseAvailabilityCheck.check(ConfigsDatabaseAvailabilityCheck.kt:18)
  at io.airbyte.db.init.DatabaseInitializer$DefaultImpls.initialize(DatabaseInitializer.kt:85)
  at io.airbyte.db.init.ConfigsDatabaseInitializer.initialize(ConfigsDatabaseInitializer.kt:20)
  at io.airbyte.bootloader.Bootloader.initializeDatabases(Bootloader.kt:221)
  at io.airbyte.bootloader.Bootloader.load(Bootloader.kt:77)
  at io.airbyte.bootloader.ApplicationKt.main(Application.kt:25)
  Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30011ms (total=0, active=0, idle=0, waiting=0)
  at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:709)
  at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:188)
  at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:146)
  at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:99)
  at org.jooq.impl.DataSourceConnectionProvider.acquire(DataSourceConnectionProvider.java:87)
  ... 24 common frames omitted
  Caused by: org.postgresql.util.PSQLException: Connection to airbyte-db-svc.airbyte.svc.cluster.local:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
  at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:373)
  at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:57)
  at org.postgresql.jdbc.PgConnection.(PgConnection.java:277)
  at org.postgresql.Driver.makeConnection(Driver.java:448)
  at org.postgresql.Driver.connect(Driver.java:298)
  at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:139)
  at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:368)
  at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:205)
  at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:483)
  at com.zaxxer.hikari.pool.HikariPool$PoolEntryCreator.call(HikariPool.java:747)
  at com.zaxxer.hikari.pool.HikariPool$PoolEntryCreator.call(HikariPool.java:726)
  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
  at java.base/java.lang.Thread.run(Thread.java:1583)
  Caused by: java.net.ConnectException: Connection refused
  at java.base/sun.nio.ch.Net.pollConnect(Native Method)
  at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:682)
  at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:542)
  at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:592)
  at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
  at java.base/java.net.Socket.connect(Socket.java:751)
  at org.postgresql.core.PGStream.createSocket(PGStream.java:261)
  at org.postgresql.core.PGStream.(PGStream.java:122)
  at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:146)
  at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:289)
  ... 14 common frames omitted

Relevant log output

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/11565

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will do an initial review and may:

• Ask clarifying questions if needed
• Suggest relevant documentation or workarounds
• Flag this for internal visibility

Note: Community issues are reviewed on a best-effort basis and do not have a guaranteed response time. For additional help:

• Join the Airbyte Community Slack to connect with other users and community members
• If you're an Airbyte Cloud customer, you can open a support ticket or contact your account representative, referencing this issue URL

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/5dfae879490e4d1a924028b0cd43d3bb

✅ Devin AI session created successfully!

[devin-ai-integration]

Hi Mahesh Kamble (@ma-gk), thank you for reporting this issue!

The stack trace shows that the airbyte-bootloader pod is failing because it cannot connect to the PostgreSQL database at airbyte-db-svc.airbyte.svc.cluster.local:5432. The root error is:

Connection to airbyte-db-svc.airbyte.svc.cluster.local:5432 refused.
Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

This means the database service was not reachable when the bootloader attempted to initialize. Here are some things to check:

Troubleshooting Steps

1. Verify the database pod is running:

   kubectl get pods -n airbyte | grep db

   Ensure the airbyte-db pod is in Running status and Ready.

2. Check the database pod logs:

   kubectl logs -n airbyte <airbyte-db-pod-name>

   Look for any startup errors (e.g., disk full, permission issues, corrupted data directory).

3. Verify the database service exists and has endpoints:

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

4. If using an external database, verify that:

   • The hostname/port in your Helm values are correct
   • Network policies or firewalls allow traffic from the bootloader pod to the database
   • The database is accepting connections

5. Check pod startup ordering: The bootloader may have started before the database was ready. You can try restarting the bootloader pod after confirming the DB is healthy:

   kubectl delete pod -n airbyte -l app.kubernetes.io/name=bootloader

A few clarifying questions:

• Are you using the bundled PostgreSQL (default Helm chart database) or an external database?
• Is this a fresh install or an upgrade from a previous version?
• Can you share the output of kubectl get pods -n airbyte so we can see the status of all pods?

Please ensure you mask or remove any sensitive information (API keys, passwords, tokens, connection strings) before sharing logs.

I've escalated this to the internal team for further investigation.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

This message is generated from Devin.ai (internal session link).

[devin-ai-integration]

This issue is being tracked internally: https://github.com/airbytehq/oncall/issues/11565

This message is generated from Devin.ai (internal session link).

[ma-gk]

How can I change the order of initialization?