<@U04S8PLJWMT> how can I upgrade abctl?
# ask-ai
f
@kapa.ai how can I upgrade abctl?
k
You can upgrade
abctl
with Homebrew:
Copy code
bash brew upgrade abctl
This updates only the
abctl
CLI, not your Airbyte deployment.[\[Upgrade guides\]](https://docs.airbyte.com/platform/operator-guides/upgrading-airbyte)[\[abctl install\]](https://docs.airbyte.com/platform/deploying-airbyte/abctl#install-abctl)
f
@kapa.ai how can I upgrade abctl under debian 12?
k
A message from kapa.ai
On Debian 12 you have two documented options to upgrade `abctl`: 1. If you installed via Homebrew (Linuxbrew) Upgrade just like on macOS:
Copy code
bash    brew upgrade abctl
[[Upgrading Airbyte](https://docs.airbyte.com/platform/operator-guides/upgrading-airbyte)] 2. If you installed from the GitHub Linux tarball The docs only describe a fresh install flow, but you can “upgrade” by repeating it with the newer release: 1. Download the latest Linux release matching your architecture (e.g.
linux-amd64
or
linux-arm64
). [[Install abctl](https://docs.airbyte.com/platform/deploying-airbyte/abctl#install-abctl)] 2. Extract it:
Copy code
bash       tar -xvzf {name-of-file-downloaded.linux-*.tar.gz}       chmod +x abctl/abctl
3. Replace the existing binary in your PATH:
Copy code
bash       sudo mv abctl /usr/local/bin
4. Verify:
Copy code
bash       abctl version
The documentation does not mention any other Debian‑specific upgrade method beyond these Homebrew and GitHub-based flows.
f
@kapa.ai my values.yaml is like this
Copy code
postgresql:
  enabled: false
  extraVolumes:
  - name: postgres-ssl-cert
    configMap:
      name: postgres-ssl-cert
  extraVolumeMounts:
    - name: postgres-ssl-cert
      mountPath: /etc/ssl/certs/postgres-ca.crt
      subPath: ca.crt
  extraEnv:
    - name: POSTGRES_TLS_ENABLED
      value: "true"
    - name: POSTGRES_TLS_DISABLE_HOST_VERIFICATION
      value: "true"
    - name: SQL_TLS_ENABLED
      value: "true"
    - name: SQL_TLS_DISABLE_HOST_VERIFICATION
      value: "true"

global:
  auth:
    enabled: false
  network:
    name: kind
  envVars:
    DATABASE_URL: "jdbc:<postgresql://10.36.77.17:5432/postgres?ssl=true&sslmode=require>"
  database:
    type: external
    host: 10.36.77.17
    port: "5432"
    database: postgres
    secretName: "airbyte-database-secrets"
    userSecretKey: "postgres-user"
    passwordSecretKey: "postgres-password"
but the bootloader is getting the following error when installing with abctl
Copy code
2025-12-04 06:50:08,239 [virtual-executor-1202706875]	ERROR	i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [10.36.77.17:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms (total=0, active=0, idle=0, waiting=0)
java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms (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 io.micronaut.management.health.indicator.jdbc.JdbcIndicator.lambda$getResult$0(JdbcIndicator.java:92)
	at io.micronaut.core.async.publisher.AsyncSingleResultPublisher$ExecutorServiceSubscription.lambda$request$1(AsyncSingleResultPublisher.java:107)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.lang.VirtualThread.run(VirtualThread.java:329)
Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2734)
	at org.postgresql.core.v3.QueryExecutorImpl.readStartupMessages(QueryExecutorImpl.java:2859)
	at org.postgresql.core.v3.QueryExecutorImpl.<init>(QueryExecutorImpl.java:178)
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:344)
	at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:57)
	at org.postgresql.jdbc.PgConnection.<init>(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)
how can I resolve?
k
A message from kapa.ai
The error is coming from Postgres, not TLS: Airbyte is trying to connect to a database named
db-airbyte
, but that database does not exist on your Postgres instance: >
FATAL: database "db-airbyte" does not exist
Two things to fix: --- ### 1. Make sure the Airbyte DB exists With an external Postgres, you must have the Airbyte DB (and Temporal DBs) created up front. Examples from users:
Copy code
sql CREATE DATABASE airbyte WITH OWNER = postgres; CREATE DATABASE temporal WITH OWNER = postgres; CREATE DATABASE temporal_visibility WITH OWNER = postgres; ```[[External Postgres issue](<https://github.com/airbytehq/airbyte/issues/49304>); [Unable to create SQL database](<https://discuss.airbyte.io/t/1544>)]  Or, if you want the name `db-airbyte`, create that:  ```sql CREATE DATABASE "db-airbyte" WITH OWNER = postgres;
and grant privileges to the user in your secret if it’s not
postgres
. [[Unable to create SQL database](https://discuss.airbyte.io/t/1544)] --- ### 2. Align the DB name in
values.yaml
with what you actually created Right now you have:
Copy code
yaml global:   envVars:     DATABASE_URL: "jdbc:<postgresql://10.36.77.17:5432/postgres?ssl=true&sslmode=require>"   database:     type: external     host: 10.36.77.17     port: "5432"     database: postgres
But the bootloader log shows it is checking
10.36.77.17:5432/db-airbyte
, which means the effective configuration (either from defaults or other values) is using
db-airbyte
as the Airbyte DB name. To resolve, pick one DB name and use it consistently: - If you want to use an existing
postgres
DB: - Create the schemas/tables is handled by Airbyte, but the DB must exist and match config. - Set the DB name accordingly, e.g. for Helm v1:
Copy code
yaml     global:       database:         type: external         host: 10.36.77.17         port: "5432"         database: postgres         secretName: airbyte-database-secrets         userSecretKey: postgres-user         passwordSecretKey: postgres-password
[[External DB values 1.8](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/database)] - If you prefer `db-airbyte`: 1. Create
db-airbyte
in Postgres (see SQL above). 2. Set: ```yaml global: database: type: external host: 10.36.77.17 port: "5432" database: db-airbyte secretName: airbyte-database-secrets userSecretKey: postgres-user passwordSecretKey: postgres-password ```[[External DB values](https://docs.airbyte.com/platform/deploying-airbyte/integrations/database)] Make sure your
airbyte-database-secrets
secret has the keys
postgres-user
and
postgres-password
containing valid credentials, as per the docs. [[External DB secrets](https://docs.airbyte.com/platform/deploying-airbyte/integrations/database)] --- After fixing the DB name and ensuring the DB exists, re-run your
abctl
install/upgrade; the bootloader’s Hikari health check should then succeed.
f
@kapa.ai for helm v2 how can I explicitate my database name? It seems that is asking for a
airbyte-db
, but my data are under
postgres
k
A message from kapa.ai
In Helm chart V2, the database name key changed from
database
to
name
. You need to set it under
global.database.name
and disable the internal Postgres. For Core / Community:
Copy code
yaml global:   database:     type: external        # if you’re following the integrations doc     secretName: "airbyte-config-secrets"     host: "10.36.77.17"     port: "5432"     name: "postgres"      # <-- your DB name here     userSecretKey: "database-user"     passwordSecretKey: "database-password"  postgresql:   enabled: false
[[Chart v2 values](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#update-your-valuesyaml-file); [External DB v2](https://docs.airbyte.com/platform/deploying-airbyte/integrations/database)] For Self‑Managed Enterprise, it’s the same pattern:
Copy code
yaml postgresql:   enabled: false  global:   database:     secretName: "airbyte-config-secrets"     host: "10.36.77.17"     port: "5432"     name: "postgres"      # <-- was `database` in v1     user: ""              # or userSecretKey     userSecretKey: "database-user"     passwordSecretKey: "database-password"
[[Enterprise impl v2](https://docs.airbyte.com/platform/enterprise-setup/implementation-guide#configuring-the-airbyte-database)] So to avoid Airbyte trying to use
db-airbyte
, explicitly set
global.database.name: postgres
(for v2) instead of
global.database.database
, and ensure the
postgres
database actually exists in your Postgres instance.