Manish Tomar
03/17/2022, 6:55 AMManish Tomar
03/17/2022, 6:55 AMJavier Llorente Mañas
03/17/2022, 9:34 AMDan Siegel
03/17/2022, 1:40 PMDan Siegel
03/17/2022, 1:54 PMJavier Llorente Mañas
03/17/2022, 2:30 PMFabian Benik
03/17/2022, 3:50 PMwebapp
and server
deployments stay in invalid state.
Inside the server
logs I see that the pod crashes after following messages:
2022-03-17 16:42:12.889 CET2022-03-17 15:42:12 [32mINFO[m i.t.s.WorkflowServiceStubsImpl(<init>):188 - Created GRPC client for channel: ManagedChannelOrphanWrapper{delegate=ManagedChannelImpl{logId=9, target=airbyte-temporal:7233}}
2022-03-17 16:42:10.880 CET2022-03-17 15:42:10 [33mWARN[m i.a.w.t.TemporalUtils(getTemporalClientWhenConnected):185 - Waiting for default namespace to be initialized in temporal...
Lucas Wiley
03/17/2022, 5:59 PMMaxime edfeed
03/17/2022, 6:13 PMAakash K
03/17/2022, 6:14 PMSharal Pinto
03/17/2022, 9:23 PMJason Carey
03/17/2022, 10:00 PMgetTransportChannel() called when needsExecutor() is true
error with no logs. This seems to happen very early in the destination provisioning since I receive the same error even after using an invalid private key, invalid topic, or invalid project. Anyone seen this before or have insights?Jakub Jablonski
03/17/2022, 10:46 PMNate
03/17/2022, 11:29 PMIs this your first time deploying Airbyte: No
OS Version / Instance: EC2 t2.large (problem seems to exist on a local instance as well)
Deployment: Docker
Airbyte Version: 0.35.57-alpha
Source: n/a
Destination: n/a
hi all - my question is on the configuration (archive.gz
) import. We're designing a disaster recovery process for saving connector configurations and we're able to grab the export tarball no problem (programmatically, using the endpoint or manually in Settings > Export Configuration) but unable to consistently import the archive.gz
into a given instance. If I drag and drop my archive.gz
via the UI, it seems to accept it but then does nothing (i.e. fresh instance remains empty) and then I followed along with these docs to try and use the import endpoint instead but that didn't respect the contents of the archive.gz
either
other things that might be relevant:
• original problem detected on AWS EC2 but then reproduced on a local docker deployment
• the airbyte instance version (0.35.57-alpha) was consistent across export and import attempts
any help is greatly appreciated (tagging @Josh Liu for visibility)Owais Javed
03/18/2022, 3:16 AMAyyoub Maulana Hadidy
03/18/2022, 3:21 AMMahak Urooj
03/18/2022, 6:44 AMThiago Chiliatto
03/18/2022, 12:15 PMGeorge Barrett
03/18/2022, 1:18 PMSébastien Haentjens
03/18/2022, 2:50 PMjames yang
03/19/2022, 10:00 AMjames yang
03/19/2022, 10:03 AMSteve Reeling
03/19/2022, 4:52 PMRajnish Malik
03/19/2022, 6:32 PMOctavia Squidington III
03/21/2022, 12:25 AMManish Tomar
03/21/2022, 9:31 AMManish Tomar
03/21/2022, 9:31 AMOctavia Squidington III
03/21/2022, 1:28 PMManish Tomar
03/21/2022, 9:33 AMAlfie Mountfield
03/21/2022, 10:41 AMalfie documents/code/airbyte master export DOCKER_BUILD_PLATFORM=linux/arm64
export DOCKER_BUILD_ARCH=arm64
export ALPINE_IMAGE=arm64v8/alpine:3.14
export POSTGRES_IMAGE=arm64v8/postgres:13-alpine
export JDK_VERSION=17
alfie documents/code/airbyte master VERSION=dev docker-compose up
WARNING: The RUN_DATABASE_MIGRATION_ON_STARTUP variable is not set. Defaulting to a blank string.
WARNING: The SECRET_PERSISTENCE variable is not set. Defaulting to a blank string.
WARNING: The WORKER_ENVIRONMENT variable is not set. Defaulting to a blank string.
Creating network "airbyte_default" with the default driver
Creating volume "airbyte_workspace" with default driver
Creating volume "airbyte_data" with default driver
Creating volume "airbyte_db" with default driver
Pulling init (airbyte/init:dev)...
ERROR: manifest for airbyte/init:dev not found: manifest unknown: manifest unknown