Hi Team, I am using external PSQL RDS for airbyte and got stucked with this error, Investigated a lot but could find resolutions . It looks like this

CONTAINER_ALREADY_STARTED_PLACEHOLDER

is not getting created within container, Looking at this bash script i feel container will through this error again again unless this command works

touch $CONTAINER_ALREADY_STARTED

. Please help with your assistance 🙏

Done init
PostgreSQL started.
touch: CONTAINER_ALREADY_STARTED_PLACEHOLDER: Permission denied
2023-01-08T22:26:34.633Z        ERROR   Unable to create SQL database.  {"error": "pq: database \"temporal\" already exists", "logging-call-at": "handler.go:97"}
2023-01-08T22:26:34.653Z        INFO    Starting schema setup   {"config": {"SchemaFilePath":"","InitialVersion":"0.0","Overwrite":false,"DisableVersioning":false}, "logging-call-at": "setuptask.go:57"}

Hi Sandip! Could you double check that the user has permission to create new databases? Another user had this solution that worked: Manually create the databases called

temporal

and

temporal_visibility

in the Postgres server and assign permissions to the Airbyte user. This is the code required to be run if connecting to the Postgres server using psql

create database temporal;
grant all privileges on database temporal to airbyte;

create database temporal_visibility;
grant all privileges on database temporal_visibility to airbyte;

Let me know if this helps!

Hi @Nataly Merezhuk (Airbyte) temporal / temporal_visibility db got created in RDS but loops keeps running by this error

PostgreSQL started.
touch: CONTAINER_ALREADY_STARTED_PLACEHOLDER: Permission denied
2023-01-08T22:26:34.633Z        ERROR   Unable to create SQL database.  {"error": "pq: database \"temporal\" already exists", "logging-call-at": "handler.go:97"}
2023-01-08T22:26:34.653Z        INFO    Starting schema setup   {"config":

Oh got it, thanks for reiterating the error! So then it looks like the database already exists. Did you deploy Airbyte before trying to separate the database? Did you delete the existing containers that were created? Here's another thread I found that might be helpful! https://discuss.airbyte.io/t/airbyte-server-unable-to-start-after-configuring-an-external-database-backend/554