Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to install Airbyte locally - Unable to connect to the database #45456

Closed
kassi opened this issue Sep 13, 2024 · 11 comments
Closed

Unable to install Airbyte locally - Unable to connect to the database #45456

kassi opened this issue Sep 13, 2024 · 11 comments
Labels
area/abctl Issues with the abctl quickstart cli autoteam community team/use type/bug Something isn't working

Comments

@kassi
Copy link

kassi commented Sep 13, 2024 •
edited
Loading

What happened?

I'm on a Mac M3 Pro and Docker is up and running.
I'm following the documentation, installing airbyte locally with

    $ brew tap airbytehq/tap
    $ brew install abctl
    $ abctl local install

Result:

  INFO    Using Kubernetes provider:
            Provider: kind
            Kubeconfig: /Users/kassi/.airbyte/abctl/abctl.kubeconfig
            Context: kind-airbyte-abctl
 SUCCESS  Found Docker installation: version 27.2.0
  INFO    No existing cluster found, cluster 'airbyte-abctl' will be created
 SUCCESS  Port 8000 appears to be available
 SUCCESS  Cluster 'airbyte-abctl' created
  INFO    Namespace 'airbyte-abctl' created
  INFO    Persistent volume 'airbyte-minio-pv' created
  INFO    Persistent volume 'airbyte-volume-db' created
  INFO    Persistent volume claim 'airbyte-minio-pv-claim-airbyte-minio-0' created
  INFO    Persistent volume claim 'airbyte-volume-db-airbyte-db-0' created
  DEBUG   getting helm chart "airbyte/airbyte" with version ""
  DEBUG   determined latest airbyte chart url: https://airbytehq.github.io/helm-charts/airbyte-0.551.0.tgz
  INFO    Starting Helm Chart installation of 'airbyte/airbyte' (version: 0.551.0)
  DEBUG   helm: preparing upgrade for airbyte-abctl
  DEBUG   helm: performing update for airbyte-abctl
  DEBUG   helm: creating upgraded release for airbyte-abctl
  DEBUG   helm: Starting delete for "airbyte-abctl-airbyte-env" ConfigMap
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 30m0s
  DEBUG   helm: creating 1 resource(s)
  DEBUG   helm: Starting delete for "airbyte-abctl-airbyte-secrets" Secret
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 30m0s
  DEBUG   helm: creating 1 resource(s)
  DEBUG   helm: Starting delete for "airbyte-abctl-airbyte-bootloader" Pod
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 30m0s
  DEBUG   helm: creating 1 resource(s)
  DEBUG   helm: Watching for changes to Pod airbyte-abctl-airbyte-bootloader with timeout of 30m0s
  DEBUG   helm: Add/Modify event for airbyte-abctl-airbyte-bootloader: ADDED
  DEBUG   helm: Pod airbyte-abctl-airbyte-bootloader pending
  DEBUG   helm: Add/Modify event for airbyte-abctl-airbyte-bootloader: MODIFIED
  DEBUG   helm: Pod airbyte-abctl-airbyte-bootloader pending
  DEBUG   Successfully assigned airbyte-abctl/airbyte-abctl-airbyte-bootloader to airbyte-abctl-control-plane
  DEBUG   helm: Add/Modify event for airbyte-abctl-airbyte-bootloader: MODIFIED
  DEBUG   helm: Pod airbyte-abctl-airbyte-bootloader pending
  DEBUG   Container image "airbyte/bootloader:0.64.3" already present on machine
  DEBUG   Created container airbyte-bootloader-container
  DEBUG   start streaming bootloader logs
  DEBUG   helm: Add/Modify event for airbyte-abctl-airbyte-bootloader: MODIFIED
  DEBUG   helm: Pod airbyte-abctl-airbyte-bootloader running
  DEBUG   airbyte-bootloader: Unsetting empty environment variable 'AB_INSTANCE_ADMIN_CLIENT_SECRET'
  DEBUG   airbyte-bootloader: Unsetting empty environment variable 'AB_INSTANCE_ADMIN_CLIENT_ID'
  DEBUG   airbyte-bootloader: Unsetting empty environment variable 'AB_INSTANCE_ADMIN_PASSWORD'
  DEBUG   airbyte-bootloader: Unsetting empty environment variable 'AB_JWT_SIGNATURE_SECRET'
  DEBUG   airbyte-bootloader: 2024-09-13T11:52:28.951057304Z main INFO Loading mask data from '/seed/specs_secrets_mask.yaml
  DEBUG   airbyte-bootloader:
  DEBUG   airbyte-bootloader:     ___    _      __          __
  DEBUG   airbyte-bootloader:    /   |  (_)____/ /_  __  __/ /____
  DEBUG   airbyte-bootloader:   / /| | / / ___/ __ \/ / / / __/ _ \
  DEBUG   airbyte-bootloader:  / ___ |/ / /  / /_/ / /_/ / /_/  __/
  DEBUG   airbyte-bootloader: /_/  |_/_/_/  /_.___/\__, /\__/\___/
  DEBUG   airbyte-bootloader:                     /____/
  DEBUG   airbyte-bootloader:         : airbyte-bootloader :
  DEBUG   airbyte-bootloader:
  DEBUG   airbyte-bootloader: i.m.c.e.DefaultEnvironment(<init>):168 - Established active environments: [k8s, cloud]
  DEBUG   airbyte-bootloader: i.m.c.i.MeterRegistry$Config(logWarningAboutLateFilter):851 - A MeterFilter is being configured after a Meter has been registered to this registry. All MeterFilters should be configured before any Meters are registered. If that is not possible or you have a use case where it should be allowed, let the Micrometer maintainers know at https://github.com/micrometer-metrics/micrometer/issues/4920. Enable DEBUG level logging on this logger to see a stack trace of the call configuring this MeterFilter.
  DEBUG   airbyte-bootloader: i.m.r.Micronaut(start):101 - Startup completed in 1053ms. Server Running: http://airbyte-abctl-airbyte-bootloader:9002
  DEBUG   airbyte-bootloader: i.a.f.ConfigFileClient(<init>):113 - path /flags does not exist, will return default flag values
  DEBUG   airbyte-bootloader: i.a.m.l.MetricClientFactory(initialize):72 - MetricClient was not recognized or not provided. Accepted values are `datadog` or `otel`.
  DEBUG   airbyte-bootloader: i.a.c.s.RemoteDefinitionsProvider(<init>):75 - Creating remote definitions provider for URL 'https://connectors.airbyte.com/files/' and registry 'OSS'...
  DEBUG   airbyte-bootloader: i.a.c.i.c.SeedBeanFactory(seedDefinitionsProvider):39 - Using local definitions provider for seeding
  DEBUG   airbyte-bootloader: i.a.b.Bootloader(load):103 - Initializing databases...
  DEBUG   airbyte-bootloader: i.a.b.Bootloader(initializeDatabases):228 - Initializing databases...
  DEBUG   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(check):38 - Waiting for database to become available...
  DEBUG   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):75 - Testing airbyte configs database connection...
  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [4e7d7d55, L:/127.0.0.1:48840 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused
  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [4e7d7d55, L:/127.0.0.1:48840 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused
  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [4e7d7d55, L:/127.0.0.1:48840 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused
  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [4e7d7d55, L:/127.0.0.1:48840 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused
  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [4e7d7d55, L:/127.0.0.1:48840 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused
  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [4e7d7d55, L:/127.0.0.1:48840 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused
  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [4e7d7d55, L:/127.0.0.1:48840 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused
  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [4e7d7d55, L:/127.0.0.1:48840 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30004ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30003ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30003ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30003ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30003ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30003ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30003ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30003ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30021ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.b.Application(main):25 - Unable to bootstrap Airbyte environment.
  ERROR   airbyte-bootloader: io.airbyte.db.init.DatabaseInitializationException: Database availability check failed.
  ERROR   airbyte-bootloader: Caused by: io.airbyte.db.check.DatabaseCheckException: Unable to connect to the database.
  ERROR   Failed to install airbyte/airbyte Helm Chart
  ERROR   Unable to install Airbyte locally
  ERROR   unable to install airbyte chart:
          pod airbyte-abctl-airbyte-bootloader: Caused by: io.airbyte.db.check.DatabaseCheckException: Unable to connect to the database.

What did you expect to happen?

AirByte should be installed locally and open up in the browser under http://localhost:8000

Abctl Version

$ abctl version
version: v0.16.0

Docker Version

$ docker version
Client:
 Version:           27.2.0
 API version:       1.47
 Go version:        go1.21.13
 Git commit:        3ab4256
 Built:             Tue Aug 27 14:14:45 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.34.2 (167172)
 Engine:
  Version:          27.2.0
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.21.13
  Git commit:       3ab5c7d
  Built:            Tue Aug 27 14:15:41 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.20
  GitCommit:        8fc6bcff51318944179630522a095cc9dbf9f353
 runc:
  Version:          1.1.13
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

OS Version

# On Mac:
$ uname -a
Darwin MacBook-Pro-von-Karsten.local 23.4.0 Darwin Kernel Version 23.4.0: Wed Feb 21 21:44:54 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6030 arm64
@kassi kassi added area/abctl Issues with the abctl quickstart cli needs-triage type/bug Something isn't working labels Sep 13, 2024
@marcosmarxm
Copy link
Member

@kassi can you downgrade Docker to 4.33 or change the mount system from VirtioFS to gRPC FUSE?
image

The problem you're having is related to run Postgres on Mac/Docker: docker/for-mac#7415

@kassi
Copy link
Author

kassi commented Sep 13, 2024

@marcosmarxm I tried changing the mount system to gRPC FUSE, restarted Docker, uninstalled and installed again.
Same result

  DEBUG   airbyte-bootloader: i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [5ed93596, L:/127.0.0.1:47306 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused

@kassi
Copy link
Author

kassi commented Sep 13, 2024

I now downgraded to 4.33, uninstalled and reinstalled. Same error still happening.

@mileszim
Copy link

I'm getting the same error, Mac Sequoia , Docker Desktop 4.34.2

@sebastiantruj
Copy link

I am getting the same error with Docker Desktop 4.33.0 on macOS Sonoma 14.6.1.

@vinioliveira
Copy link

@kassi can you downgrade Docker to 4.33 or change the mount system from VirtioFS to gRPC FUSE? image

The problem you're having is related to run Postgres on Mac/Docker: docker/for-mac#7415

That did it for me.

@otabekgh
Copy link

got the same error on Mac Sequoia

@kimlam-wk
Copy link

I have the same issue, I tried downgrading docker to 4.33 and changed the mount system to gRPC FUSE but issue still remains.

  • Docker version: 4.33
  • os: MacOS Sequoia 15.0 running on Macbook M3 Pro

Are there any other potential solution to try out?

@airs0urce
Copy link

For me this temp solution worked:
https://discuss.airbyte.io/t/error-running-abctl-local-install-in-airbyte-oss/7999/5

@kimlam-wk
Copy link

kimlam-wk commented Sep 25, 2024 •
edited
Loading

Amazing yeah that worked after running the manual creation of the db:

docker exec -it airbyte-abctl-control-plane kubectl -n airbyte-abctl exec -it airbyte-db-0 -- psql --user airbyte --dbname postgres --command='create database "db-airbyte"'

before:

            Provider: kind
            Kubeconfig: /Users/kim.lam/.airbyte/abctl/abctl.kubeconfig
            Context: kind-airbyte-abctl
 SUCCESS  Found Docker installation: version 27.1.1
  INFO    No existing cluster found, cluster 'airbyte-abctl' will be created
 SUCCESS  Port 8000 appears to be available
 SUCCESS  Cluster 'airbyte-abctl' created
  INFO    Namespace 'airbyte-abctl' created
  INFO    Persistent volume 'airbyte-minio-pv' created
  INFO    Persistent volume 'airbyte-volume-db' created
  INFO    Persistent volume claim 'airbyte-minio-pv-claim-airbyte-minio-0' created
  INFO    Persistent volume claim 'airbyte-volume-db-airbyte-db-0' created
  INFO    Starting Helm Chart installation of 'airbyte/airbyte' (version: 1.0.0)
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30002ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
  ERROR   airbyte-bootloader: org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)
  ERROR   airbyte-bootloader: Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=0)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   airbyte-bootloader: i.m.m.h.i.HealthResult$Builder(exception):123 - Health indicator [airbyte-db-svc:5432/db-airbyte] reported exception: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30001ms (total=0, active=0, idle=0, waiting=1)
  ERROR   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: FATAL: database "db-airbyte" does not exist
  ERROR   Failed to install airbyte/airbyte Helm Chart
  ERROR   Unable to install Airbyte locally
  ERROR   unable to install airbyte chart: unable to install helm: context canceled

after:


  INFO    Using Kubernetes provider:
            Provider: kind
            Kubeconfig: /Users/kim.lam/.airbyte/abctl/abctl.kubeconfig
            Context: kind-airbyte-abctl
 SUCCESS  Found Docker installation: version 27.1.1
 SUCCESS  Existing cluster 'airbyte-abctl' found
 SUCCESS  Cluster 'airbyte-abctl' validation complete
  INFO    Namespace 'airbyte-abctl' already exists
  INFO    Persistent volume 'airbyte-minio-pv' already exists
  INFO    Persistent volume 'airbyte-volume-db' already exists
  INFO    Persistent volume claim 'airbyte-minio-pv-claim-airbyte-minio-0' already exists
  INFO    Persistent volume claim 'airbyte-volume-db-airbyte-db-0' already exists
  INFO    Starting Helm Chart installation of 'airbyte/airbyte' (version: 1.0.0)
 SUCCESS  Installed Helm Chart airbyte/airbyte:
            Name: airbyte-abctl
            Namespace: airbyte-abctl
            Version: 1.0.0
            AppVersion: 1.0.0
            Release: 2
  INFO    Starting Helm Chart installation of 'nginx/ingress-nginx' (version: 4.11.2)
 SUCCESS  Installed Helm Chart nginx/ingress-nginx:
            Name: ingress-nginx
            Namespace: ingress-nginx
            Version: 4.11.2
            AppVersion: 1.11.2
            Release: 1
  INFO    No existing Ingress found, creating one
 SUCCESS  Ingress created
 SUCCESS  Launched web-browser successfully for http://localhost:8000
 SUCCESS  Airbyte installation complete.
            A password may be required to login. The password can by found by running
            the command abctl local credentials

Thank you @airs0urce !

@bgroff
Copy link
Contributor

bgroff commented Sep 30, 2024 •
edited
Loading

This has been fixed in the latest release of abctl.

@bgroff bgroff closed this as completed Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/abctl Issues with the abctl quickstart cli autoteam community team/use type/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@airs0urce @bgroff @vinioliveira @kassi @mileszim @marcosmarxm @otabekgh @sebastiantruj @octavia-squidington-iii @kimlam-wk