Airbyte-temporal started failed after execute docker-compose up

Platform, Deploy & Infra Issues
1
  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: MacOS 12.6
  • Memory / Disk: 2TB
  • Deployment: Docker
  • Airbyte Version: 0.40.32
  • Step: I follow the official deploy doc with following step:
git clone https://github.com/airbytehq/airbyte.git
cd airbyte
docker compose up

After execute docker compose up, I check the service logs and find the root error is in airbyte-temporal. I can access the postgresql DB directly with psql and find all the airbyte needed tables are successfully created as follows. Can any one tell me how to solve the issue?

BTW, I am in restricted region, I use proxy in docker.

temporal=# select * from schema_version;
 version_partition | db_name  |       creation_time       | curr_version | min_compatible_version
-------------------+----------+---------------------------+--------------+------------------------
                 0 | temporal | 2023-02-12 16:02:49.96513 | 1.6          | 1.0
(1 row)

temporal=# select * from schema_update_history;
 version_partition | year | month |        update_time         |                               description                                |           manifest_md5           | new_version | old_version
-------------------+------+-------+----------------------------+--------------------------------------------------------------------------+----------------------------------+-------------+-------------
                 0 | 2023 |     2 | 2023-02-12 16:02:49.462872 | initial version                                                          |                                  | 0.0         | 0
                 0 | 2023 |     2 | 2023-02-12 16:02:49.925995 | base version of schema                                                   | 55b84ca114ac34d84bdc5f52c198fa33 | 1.0         | 0.0
                 0 | 2023 |     2 | 2023-02-12 16:02:49.934216 | schema update for cluster metadata                                       | 58f06841bbb187cb210db32a090c21ee | 1.1         | 1.0
                 0 | 2023 |     2 | 2023-02-12 16:02:49.939031 | schema update for RPC replication                                        | c6bdeea21882e2625038927a84929b16 | 1.2         | 1.1
                 0 | 2023 |     2 | 2023-02-12 16:02:49.947682 | schema update for kafka deprecation                                      | 3beee7d470421674194475f94b58d89b | 1.3         | 1.2
                 0 | 2023 |     2 | 2023-02-12 16:02:49.954255 | schema update for cluster metadata cleanup                               | c53e2e9cea5660c8a1f3b2ac73cdb138 | 1.4         | 1.3
                 0 | 2023 |     2 | 2023-02-12 16:02:49.961864 | schema update for cluster_membership, executions and history_node tables | bfb307ba10ac0fdec83e0065dc5ffee4 | 1.5         | 1.4
                 0 | 2023 |     2 | 2023-02-12 16:02:49.966141 | schema update for queue_metadata                                         | 978e1a6500d377ba91c6e37e5275a59b | 1.6         | 1.5
(8 rows)

airbyte-temporal logs
touch: CONTAINER_ALREADY_STARTED_PLACEHOLDER: Permission denied
2023-02-13T02:39:22.702Z ERROR Unable to create SQL database. {“error”: “pq: database "temporal" already exists”, “logging-call-at”: “handler.go:97”}
2023-02-13T02:39:22.722Z INFO Starting schema setup {“config”: {“SchemaFilePath”:“”,“InitialVersion”:“0.0”,“Overwrite”:false,“DisableVersioning”:false}, “logging-call-at”: “setuptask.go:57”}
2023-02-13T02:39:22.722Z DEBUG Setting up version tables {“logging-call-at”: “setuptask.go:67”}
2023-02-13T02:39:22.723Z ERROR Unable to setup SQL schema. {“error”: “pq: relation "schema_version" already exists”, “logging-call-at”: “handler.go:57”}
2023-02-13T02:39:22.744Z ERROR Unable to create SQL database. {“error”: “pq: database "temporal_visibility" already exists”, “logging-call-at”: “handler.go:97”}
2023-02-13T02:39:22.767Z INFO Starting schema setup {“config”: {“SchemaFilePath”:“”,“InitialVersion”:“0.0”,“Overwrite”:false,“DisableVersioning”:false}, “logging-call-at”: “setuptask.go:57”}
2023-02-13T02:39:22.767Z DEBUG Setting up version tables {“logging-call-at”: “setuptask.go:67”}
2023-02-13T02:39:22.768Z ERROR Unable to setup SQL schema. {“error”: “pq: relation "schema_version" already exists”, “logging-call-at”: “handler.go:57”}
2023-02-13T02:39:22.789Z INFO UpdateSchemeTask started {“config”: {“DBName”:“”,“TargetVersion”:“”,“SchemaDir”:“/etc/temporal/schema/postgresql/v96/temporal/versioned”,“IsDryRun”:false}, “logging-call-at”: “updatetask.go:98”}
2023-02-13T02:39:22.793Z DEBUG found zero updates from current version 1.6 {“logging-call-at”: “updatetask.go:128”}
2023-02-13T02:39:22.793Z INFO UpdateSchemeTask done {“logging-call-at”: “updatetask.go:121”}
2023-02-13T02:39:22.813Z INFO UpdateSchemeTask started {“config”: {“DBName”:“”,“TargetVersion”:“”,“SchemaDir”:“/etc/temporal/schema/postgresql/v96/visibility/versioned”,“IsDryRun”:false}, “logging-call-at”: “updatetask.go:98”}
2023-02-13T02:39:22.818Z DEBUG found zero updates from current version 1.1 {“logging-call-at”: “updatetask.go:128”}
2023-02-13T02:39:22.818Z INFO UpdateSchemeTask done {“logging-call-at”: “updatetask.go:121”}

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hey @KaimingWan! We’re doing a big refactor and the docker compose up command has been deprecated. Could you please update and try the new command? It’s in the same doc :slight_smile: