Airbyte Startup Issues with PostgreSQL on Remote Machine

Summary

User is experiencing connectivity issues with the airbyte-temporal service when trying to connect to a PostgreSQL instance using SSL. The error indicates that the default namespace could not be initialized in temporal despite correct parameters and connectivity.


Question

Hi team

I am having problems when starting up Airbyte on a remote machine I have configured.

The idea is that Airbyte will use an existing PostgreSQL instance with other databases (using SSL).

I’m having problems with airbyte-temporal service, for some reason is not possible to connect to my PostgreSQL instance and I’m pretty sure all parameters are set ok and the connectivity is ok.

The main error I’m receiving now is that namespace default could not be initialized in temporal

WARN i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):159 - Waiting for namespace default to be initialized in temporal...

I changed in docker-compose the airbyte-temporal service and added a new env var called “DATABASE_URL” with the whole URL, including sslmode=require

Any idea ?

Thank you in advice !



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

['airbyte-temporal', 'postgresql', 'ssl', 'docker-compose', 'database-url']