Unable to deploy due to airbyte-db not building properly

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Windows
  • Memory / Disk: 32Gb / 1 Tb
  • Deployment: Docker
  • Airbyte Version: latest

After cloning I run run-ab-platform.sh and my build runs into a problem with airbyte-db which goes in a constant loop

airbyte-db                        | 2023-04-14 15:26:36.399 UTC [1] LOG:  starting PostgreSQL 13.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit
airbyte-db                        | 2023-04-14 15:26:36.400 UTC [1] LOG:  could not bind IPv4 address "0.0.0.0": Address in use
airbyte-db                        | 2023-04-14 15:26:36.400 UTC [1] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
airbyte-db                        | 2023-04-14 15:26:36.402 UTC [1] LOG:  could not bind IPv6 address "::": Address in use
airbyte-db                        | 2023-04-14 15:26:36.402 UTC [1] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
airbyte-db                        | 2023-04-14 15:26:36.402 UTC [1] WARNING:  could not create listen socket for "*"
airbyte-db                        | 2023-04-14 15:26:36.402 UTC [1] FATAL:  could not create any TCP/IP sockets
airbyte-db                        | 2023-04-14 15:26:36.403 UTC [1] LOG:  database system is shut down
airbyte-db exited with code 1
airbyte-bootloader                | 2023-04-14 15:26:36 INFO i.m.r.Micronaut(lambda$start$2):98 - Startup completed in 787ms. Server Running: http://46642e479290:9002
airbyte-bootloader                | 2023-04-14 15:26:37 INFO i.a.f.ConfigFileClient(<init>):98 - path /flags does not exist, will return default flag values
airbyte-bootloader                | 2023-04-14 15:26:37 INFO i.a.c.EnvConfigs(getEnvOrDefault):1222 - Using default value for environment variable LOCAL_CONNECTOR_CATALOG_PATH: 'seed/oss_catalog.json'
airbyte-db                        | 2023-04-14 15:26:37.206 UTC [1] LOG:  starting PostgreSQL 13.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit
airbyte-db                        | 2023-04-14 15:26:37.208 UTC [1] LOG:  could not bind IPv4 address "0.0.0.0": Address in use
airbyte-db                        | 2023-04-14 15:26:37.208 UTC [1] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
airbyte-db                        | 2023-04-14 15:26:37.219 UTC [1] LOG:  could not bind IPv6 address "::": Address in use
airbyte-db                        | 2023-04-14 15:26:37.219 UTC [1] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
airbyte-db                        | 2023-04-14 15:26:37.219 UTC [1] WARNING:  could not create listen socket for "*"
airbyte-db                        | 2023-04-14 15:26:37.219 UTC [1] FATAL:  could not create any TCP/IP sockets
airbyte-db                        | 2023-04-14 15:26:37.221 UTC [1] LOG:  database system is shut down
airbyte-bootloader                | 2023-04-14 15:26:37 INFO i.a.b.Bootloader(load):100 - Initializing databases...
airbyte-bootloader                | 2023-04-14 15:26:37 INFO i.a.b.Bootloader(initializeDatabases):199 - Initializing databases...
airbyte-bootloader                | 2023-04-14 15:26:37 WARN i.a.d.c.DatabaseAvailabilityCheck(check):38 - Waiting for database to become available...
airbyte-bootloader                | 2023-04-14 15:26:37 INFO i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):75 - Testing airbyte configs database connection...
airbyte-db exited with code 1
airbyte-db                        | 2023-04-14 15:26:38.079 UTC [1] LOG:  starting PostgreSQL 13.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit
airbyte-db                        | 2023-04-14 15:26:38.081 UTC [1] LOG:  could not bind IPv4 address "0.0.0.0": Address in use
airbyte-db                        | 2023-04-14 15:26:38.081 UTC [1] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
airbyte-db                        | 2023-04-14 15:26:38.092 UTC [1] LOG:  could not bind IPv6 address "::": Address in use
airbyte-db                        | 2023-04-14 15:26:38.092 UTC [1] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
airbyte-db                        | 2023-04-14 15:26:38.092 UTC [1] WARNING:  could not create listen socket for "*"
airbyte-db                        | 2023-04-14 15:26:38.092 UTC [1] FATAL:  could not create any TCP/IP sockets
airbyte-db                        | 2023-04-14 15:26:38.094 UTC [1] LOG:  database system is shut down
airbyte-db exited with code 1

the last part is the part which keeps looping.

This causes errors with airbyte-temporal giving error,

airbyte-temporal                  | nc: bad address 'db'
airbyte-temporal                  | Waiting for PostgreSQL to startup.

And i get a bunch of other errors from bootloader.

So for some reason the postgres db isn’t being built properly, I have tried solutions i found on stack, mainly ones in the following link

but I still have not been able to see any difference.

edit:
forgot to add this is the initial airbyte-db build before bootloader,

airbyte-temporal                  | Waiting for PostgreSQL to startup.
airbyte-db                        | selecting default time zone ... UTC
airbyte-db                        | creating configuration files ... ok
airbyte-db                        | running bootstrap script ... ok
airbyte-db                        | sh: locale: not found
airbyte-db                        | 2023-04-14 15:26:34.498 UTC [30] WARNING:  no usable system locales were found
init exited with code 0
airbyte-db                        | performing post-bootstrap initialization ... ok
airbyte-db                        | initdb: warning: enabling "trust" authentication for local connections
airbyte-db                        | You can change this by editing pg_hba.conf or using the option -A, or
airbyte-db                        | --auth-local and --auth-host, the next time you run initdb.
airbyte-db                        | syncing data to disk ... ok
airbyte-db                        |
airbyte-db                        |
airbyte-db                        | Success. You can now start the database server using:
airbyte-db                        |
airbyte-db                        |     pg_ctl -D /var/lib/postgresql/data -l logfile start
airbyte-db                        |
airbyte-db                        | waiting for server to start....2023-04-14 15:26:35.112 UTC [36] LOG:  starting PostgreSQL 13.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit
airbyte-db                        | 2023-04-14 15:26:35.117 UTC [36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
airbyte-db                        | 2023-04-14 15:26:35.133 UTC [37] LOG:  database system was shut down at 2023-04-14 15:26:34 UTC
airbyte-db                        | 2023-04-14 15:26:35.141 UTC [36] LOG:  database system is ready to accept connections
airbyte-db                        |  done
airbyte-db                        | server started
airbyte-temporal                  | Waiting for PostgreSQL to startup.
airbyte-db                        | CREATE DATABASE
airbyte-db                        |
airbyte-db                        |
airbyte-db                        | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/000_init.sql
airbyte-db                        | ALTER SYSTEM
airbyte-db                        | CREATE DATABASE
airbyte-db                        | You are now connected to database "airbyte" as user "docker".
airbyte-db                        | GRANT
airbyte-db                        |
airbyte-db                        |
airbyte-db                        | waiting for server to shut down...2023-04-14 15:26:35.456 UTC [36] LOG:  received fast shutdown request
airbyte-db                        | .2023-04-14 15:26:35.458 UTC [36] LOG:  aborting any active transactions
airbyte-db                        | 2023-04-14 15:26:35.459 UTC [36] LOG:  background worker "logical replication launcher" (PID 43) exited with exit code 1
airbyte-db                        | 2023-04-14 15:26:35.459 UTC [38] LOG:  shutting down
airbyte-db                        | 2023-04-14 15:26:35.480 UTC [36] LOG:  database system is shut down
airbyte-db                        |  done
airbyte-db                        | server stopped
airbyte-db                        |
airbyte-db                        | PostgreSQL init process complete; ready for start up.
airbyte-db                        |
airbyte-db                        | 2023-04-14 15:26:35.576 UTC [1] LOG:  starting PostgreSQL 13.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit
airbyte-db                        | 2023-04-14 15:26:35.578 UTC [1] LOG:  could not bind IPv4 address "0.0.0.0": Address in use
airbyte-db                        | 2023-04-14 15:26:35.578 UTC [1] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
airbyte-db                        | 2023-04-14 15:26:35.579 UTC [1] LOG:  could not bind IPv6 address "::": Address in use
airbyte-db                        | 2023-04-14 15:26:35.579 UTC [1] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
airbyte-db                        | 2023-04-14 15:26:35.579 UTC [1] WARNING:  could not create listen socket for "*"
airbyte-db                        | 2023-04-14 15:26:35.579 UTC [1] FATAL:  could not create any TCP/IP sockets
airbyte-db                        | 2023-04-14 15:26:35.580 UTC [1] LOG:  database system is shut down
airbyte-bootloader                | 2023-04-14 15:26:35,829 main INFO Loading mask data from '/seed/specs_secrets_mask.yaml
airbyte-db exited with code 1

To anybody in the future that has the same problem,

I had an iis server running on the same port, after checking the port and finding the PID, i was able to delete it and it worked fine.