https://linen.dev logo
Join Slack
Powered by
Hi all, I am having an issue installing a fresh i...
# replication-ask-ai
l
Hi all, I am having an issue installing a fresh instance of airbyte on an amazon linux ec2 instance. The issue seems to be with the temporal server starting. The instance is deployed in a private subnet that I connect to with was vpn client. I am able to ping the internet and I can see in my db logs that airbyte does connect to the database correctly. Would anyone be able to help me figure out what is going on? I did see some comments about the privileges for the temporal and temporal_visability, so I went ahead and created those dbs:
Copy code
create database temporal;
create database temporal_visability;
grant all privileges on database temporal to devuser;
grant all privileges on database temporal_visability to devuser;
I do see this error from my database logs: 
ERROR: UNION types "char" and text cannot be matched Position: 628. and 6 duplicate reports
This is the error I get from the airbyte-temporal container logs:
Copy code
[ec2-user airbyte]$ docker logs -f --tail 10 airbyte-temporal
[Fx] ERROR		Failed to initialize custom logger: could not build arguments for function "<http://go.uber.org/fx|go.uber.org/fx>".(*App).constructCustomLogger.func2
	/go/pkg/mod/go.uber.org/fx@v1.18.2/app.go:414:
failed to build fxevent.Logger:
could not build arguments for function "<http://go.temporal.io/server/temporal|go.temporal.io/server/temporal>".glob..func8
	/home/builder/temporal/temporal/fx.go:1025:
failed to build log.Logger:
received non-nil error from function "<http://go.temporal.io/server/temporal|go.temporal.io/server/temporal>".ServerOptionsProvider
	/home/builder/temporal/temporal/fx.go:159:
sql schema version compatibility check failed: pq: no pg_hba.conf entry for host "172.32.131.33", user "devuser", database "temporal", no encryption
Unable to create server. Error: could not build arguments for function "<http://go.uber.org/fx|go.uber.org/fx>".(*App).constructCustomLogger.func2 (/go/pkg/mod/go.uber.org/fx@v1.18.2/app.go:414): failed to build fxevent.Logger: could not build arguments for function "<http://go.temporal.io/server/temporal|go.temporal.io/server/temporal>".glob..func8 (/home/builder/temporal/temporal/fx.go:1025): failed to build log.Logger: received non-nil error from function "<http://go.temporal.io/server/temporal|go.temporal.io/server/temporal>".ServerOptionsProvider (/home/builder/temporal/temporal/fx.go:159): sql schema version compatibility check failed: pq: no pg_hba.conf entry for host "172.32.131.33", user "devuser", database "temporal", no encryption.
k
@Lindsay S That's a great question, but unfortunately it is too long. Can you ask me again but make it shorter? I'm here to help!
l
These are partial logs from trying docker compose up:
Copy code
airbyte-temporal         | Start init
init exited with code 0
airbyte-temporal         | Done init
airbyte-temporal         | PostgreSQL started.
airbyte-temporal         | touch: CONTAINER_ALREADY_STARTED_PLACEHOLDER: Permission denied
airbyte-temporal         | 2023-09-07T14:52:47.959Z	ERROR	Unable to create SQL database.	{"error": "unable to connect to DB, tried default DB names: postgres,defaultdb, errors: [pq: no pg_hba.conf entry for host \"172.32.131.33\", user \"devuser\", database \"postgres\", no encryption pq: no pg_hba.conf entry for host \"172.32.131.33\", user \"devuser\", database \"defaultdb\", no encryption]", "logging-call-at": "handler.go:94"}
airbyte-db            |
airbyte-db            | PostgreSQL Database directory appears to contain a database; Skipping initialization
airbyte-db            |
airbyte-temporal         | 2023-09-07T14:52:47.985Z	ERROR	Unable to connect to SQL database.	{"error": "pq: no pg_hba.conf entry for host \"172.32.131.33\", user \"devuser\", database \"temporal\", no encryption", "logging-call-at": "handler.go:52"}
airbyte-db            | 2023-09-07 14:52:48.010 UTC [1] LOG: starting PostgreSQL 13.12 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
airbyte-db            | 2023-09-07 14:52:48.011 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
airbyte-db            | 2023-09-07 14:52:48.011 UTC [1] LOG: listening on IPv6 address "::", port 5432
airbyte-db            | 2023-09-07 14:52:48.015 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
airbyte-temporal         | 2023-09-07T14:52:48.020Z	ERROR	Unable to create SQL database.	{"error": "unable to connect to DB, tried default DB names: postgres,defaultdb, errors: [pq: no pg_hba.conf entry for host \"172.32.131.33\", user \"devuser\", database \"postgres\", no encryption pq: no pg_hba.conf entry for host \"172.32.131.33\", user \"devuser\", database \"defaultdb\", no encryption]", "logging-call-at": "handler.go:94"}
airbyte-db            | 2023-09-07 14:52:48.021 UTC [22] LOG: database system was shut down at 2023-09-07 14:23:30 UTC
airbyte-db            | 2023-09-07 14:52:48.026 UTC [1] LOG: database system is ready to accept connections
airbyte-temporal         | 2023-09-07T14:52:48.049Z	ERROR	Unable to connect to SQL database.	{"error": "pq: no pg_hba.conf entry for host \"172.32.131.33\", user \"devuser\", database \"temporal_visibility\", no encryption", "logging-call-at": "handler.go:52"}
airbyte-temporal         | Starting to update the temporal DB
airbyte-temporal         | 2023-09-07T14:52:48.072Z	ERROR	Unable to connect to SQL database.	{"error": "pq: no pg_hba.conf entry for host \"172.32.131.33\", user \"devuser\", database \"temporal\", no encryption", "logging-call-at": "handler.go:73"}
airbyte-temporal         | Update the temporal DB is done
airbyte-temporal         | Starting to update the temporal visibility DB
airbyte-temporal         | 2023-09-07T14:52:48.095Z	ERROR	Unable to connect to SQL database.	{"error": "pq: no pg_hba.conf entry for host \"172.32.131.33\", user \"devuser\", database \"temporal_visibility\", no encryption", "logging-call-at": "handler.go:73"}
airbyte-temporal         | Update the temporal visibility DB is done
airbyte-temporal         | starting temporal server
airbyte-temporal         | Temporal CLI address: 192.168.208.3:7233.
airbyte-temporal         | Waiting for Temporal server to start...
airbyte-temporal         | 2023/09/07 14:52:48 Loading config; env=docker,zone=,configDir=config
airbyte-temporal         | 2023/09/07 14:52:48 Loading config files=[config/docker.yaml]
airbyte-temporal         | {"level":"info","ts":"2023-09-07T14:52:48.150Z","msg":"Build info.","git-time":"2023-03-29T22:11:52.000Z","git-revision":"edbafd63e19dc0d585ec8cd0ebd793d3c6c6f6d6","git-modified":true,"go-arch":"amd64","go-os":"linux","go-version":"go1.20.2","cgo-enabled":false,"server-version":"1.20.1","debug-mode":false,"logging-call-at":"main.go:143"}
airbyte-temporal         | {"level":"info","ts":"2023-09-07T14:52:48.151Z","msg":"dynamic config changed for the key: frontend.historymgrnumconns oldValue: nil newValue: { constraints: {} value: 30 }","logging-call-at":"file_based_client.go:275"}

…
…
airbyte-worker          | Caused by: java.net.UnknownHostException: airbyte-temporal
airbyte-worker          | 	at java.net.InetAddress$CachedAddresses.get(InetAddress.java:952) ~[?:?]
airbyte-worker          | 	at java.net.InetAddress.getAllByName0(InetAddress.java:1663) ~[?:?]
airbyte-worker          | 	at java.net.InetAddress.getAllByName(InetAddress.java:1528) ~[?:?]
airbyte-worker          | 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:632) ~[grpc-core-1.55.1.jar:1.55.1]
airbyte-worker          | 	at io.grpc.internal.DnsNameResolver.resolveAddresses(DnsNameResolver.java:219) ~[grpc-core-1.55.1.jar:1.55.1]
airbyte-worker          | 	at io.grpc.internal.DnsNameResolver.doResolve(DnsNameResolver.java:282) ~[grpc-core-1.55.1.jar:1.55.1]
airbyte-worker          | 	at io.grpc.grpclb.GrpclbNameResolver.doResolve(GrpclbNameResolver.java:63) ~[grpc-grpclb-1.55.1.jar:1.55.1]
airbyte-worker          | 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:318) ~[grpc-core-1.55.1.jar:1.55.1]
airbyte-worker          | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
airbyte-worker          | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
airbyte-worker          | 	at java.lang.Thread.run(Thread.java:1589) ~[?:?]
here is my .env file:
Copy code
# This file only contains Docker relevant variables.
#
# Variables with defaults have been omitted to avoid duplication of defaults.
# The only exception to the non-default rule are env vars related to scaling.
#
# See <https://github.com/airbytehq/airbyte/blob/master/airbyte-config/config-models/src/main/java/io/airbyte/config/Configs.java>
# for the latest environment variables.
#
# # Contributors - please organise this env file according to the above linked file.

# When using the airbyte-db via default docker image
CONFIG_ROOT=/data
BASIC_AUTH_PASSWORD=password
BASIC_AUTH_PROXY_TIMEOUT=900


### DATABASE ###
# Airbyte Internal Job Database, see <https://docs.airbyte.io/operator-guides/configuring-airbyte-db>
DATABASE_USER=devuser
DATABASE_PASSWORD=********
DATABASE_HOST=<redacted>.<http://rds.amazonaws.com|rds.amazonaws.com>
DATABASE_PORT=5432
DATABASE_DB=airbyte
DATABASE_URL=jdbc:postgresql://<redacted>.<http://rds.amazonaws.com:5432/airbyte|rds.amazonaws.com:5432/airbyte>
JOBS_DATABASE_MINIMUM_FLYWAY_MIGRATION_VERSION=0.40.26.001

# Airbyte Internal Config Database, defaults to Job Database if empty. Explicitly left empty to mute docker compose warnings.
CONFIG_DATABASE_USER=
CONFIG_DATABASE_PASSWORD=
CONFIG_DATABASE_URL=
CONFIGS_DATABASE_MINIMUM_FLYWAY_MIGRATION_VERSION=0.40.23.002

### AIRBYTE SERVICES ###
TEMPORAL_HOST=airbyte-temporal:7233
INTERNAL_API_HOST=airbyte-server:8001
CONNECTOR_BUILDER_API_HOST=airbyte-connector-builder-server:80
WEBAPP_URL=<http://localhost:8000/>
# Although not present as an env var, required for webapp configuration.
CONNECTOR_BUILDER_API_URL=/connector-builder-api
AIRBYTE_API_HOST=airbyte-api-server:8006

### JOBS ###
# Relevant to scaling.
SYNC_JOB_MAX_ATTEMPTS=3
SYNC_JOB_MAX_TIMEOUT_DAYS=3
SYNC_JOB_INIT_RETRY_TIMEOUT_MINUTES=5
JOB_MAIN_CONTAINER_CPU_REQUEST=
JOB_MAIN_CONTAINER_CPU_LIMIT=
JOB_MAIN_CONTAINER_MEMORY_REQUEST=
JOB_MAIN_CONTAINER_MEMORY_LIMIT=

NORMALIZATION_JOB_MAIN_CONTAINER_MEMORY_LIMIT=
NORMALIZATION_JOB_MAIN_CONTAINER_MEMORY_REQUEST=
8 Views
Open in Slack
PreviousNext
Powered by