Hi all - I keep getting a

non-json response

error. I use Google Analytics 4 as source and PostgreSQL as destination. I shows up after 60 seconds, which indicates the default timeout. I tried to set it to 0 (infinity) in the jdbc string, but doesnt work. I see that many have had this problem, but has anyone ever found the solution?

Mads, where this problem happens? During the destination setup connection or when you try to create the connection? Maybe take a look from the API response in network tab the request

check_connection_for_update

I tried to downgrade v 40.16 - but now i ge this error with this stack trace. My init image and bootloader never starts in docker, does that have anything to do with it?

2022-11-21 18:11:24 INFO i.a.w.t.TemporalAttemptExecution(get):136 - Docker volume job log path: /tmp/workspace/e9f09fde-4b34-4d4c-bc56-2c068bd5ebb1/0/logs.log

2022-11-21 18:11:24 INFO i.a.w.t.TemporalAttemptExecution(get):141 - Executing worker wrapper. Airbyte version: 0.40.16

2022-11-21 18:11:24 INFO i.a.c.i.LineGobbler(voidCall):114 -

2022-11-21 18:11:24 INFO i.a.c.i.LineGobbler(voidCall):114 - ----- START CHECK -----

2022-11-21 18:11:24 INFO i.a.c.i.LineGobbler(voidCall):114 -

2022-11-21 18:11:24 INFO i.a.c.i.LineGobbler(voidCall):114 - Checking if airbyte/destination-postgres:0.3.26 exists...

2022-11-21 18:11:25 INFO i.a.c.i.LineGobbler(voidCall):114 - airbyte/destination-postgres:0.3.26 was found locally.

2022-11-21 18:11:25 INFO i.a.w.p.DockerProcessFactory(create):119 - Creating docker container = destination-postgres-check-e9f09fde-4b34-4d4c-bc56-2c068bd5ebb1-0-yrfwe with resources io.airbyte.config.ResourceRequirements@35341622[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=]

2022-11-21 18:11:25 INFO i.a.w.p.DockerProcessFactory(create):163 - Preparing command: docker run --rm --init -i -w /data/e9f09fde-4b34-4d4c-bc56-2c068bd5ebb1/0 --log-driver none --name destination-postgres-check-e9f09fde-4b34-4d4c-bc56-2c068bd5ebb1-0-yrfwe --network host -v airbyte_workspace:/data -v /tmp/airbyte_local:/local -e DEPLOYMENT_MODE=OSS -e USE_STREAM_CAPABLE_STATE=true -e AIRBYTE_ROLE= -e WORKER_ENVIRONMENT=DOCKER -e WORKER_CONNECTOR_IMAGE=airbyte/destination-postgres:0.3.26 -e WORKER_JOB_ATTEMPT=0 -e AIRBYTE_VERSION=0.40.16 -e WORKER_JOB_ID=e9f09fde-4b34-4d4c-bc56-2c068bd5ebb1 airbyte/destination-postgres:0.3.26 check --config source_config.json

2022-11-21 18:11:30 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):117 - starting destination: class io.airbyte.integrations.destination.postgres.PostgresDestination

2022-11-21 18:11:30 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):117 - integration args: {check=null, config=source_config.json}

2022-11-21 18:11:30 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):117 - Running integration: io.airbyte.integrations.base.ssh.SshWrappedDestination

2022-11-21 18:11:30 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):117 - Command: CHECK

2022-11-21 18:11:30 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):117 - Integration config: IntegrationConfig{command=CHECK, configPath='source_config.json', catalogPath='null', statePath='null'}

2022-11-21 18:11:30 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):114 - Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword

2022-11-21 18:11:30 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):114 - Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword

2022-11-21 18:11:31 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):117 - Starting connection with method: NO_TUNNEL

2022-11-21 18:11:31 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):117 - HikariPool-1 - Starting...

2022-11-21 18:11:31 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):117 - HikariPool-1 - Start completed

This is happening to all connectors? What type of deployment are running (docker or Kubernetes)? The logs you shared doesn’t show any error.

I use docker 🙂

Latest always is the first choice. This is happening to all connectors? Did you try other connectors?

Hmm, no - but this is really the only data that i have .

Yes, but using a different connector can limit the reason of the problem. Can you try Local JSON connector as destination?

It works with local json 🙂

I strongly recommend to check the server logs to see any error there to identify why this error is happening.

This is whats happening in my network tab

Amazing.