GithubHelp home page GithubHelp logo

supabase-db is unhealthy about supabase HOT 3 OPEN

myozin-kyaw avatar myozin-kyaw commented on June 18, 2024 2
supabase-db is unhealthy

from supabase.

Comments (3)

encima avatar encima commented on June 18, 2024

Hey there, thanks for opening!

From your description, I am not 100% sure what you are trying to do so I will ask a few clarifying questions if thats alright?!

  • Are you trying to connect the Supabase containers to an existing Postgres database and not supabase-db as part of the docker-compose?
  • If yes, is that database on the same machine?
  • If yes, have you updated the configuration for Supabase to remove the postgres container and point all other services to your existing db?

If possible, it is likely easier to:

  • Clear the cache and volumes in the docker directory
  • Pull the latest commit and also the latest images
  • Dump the contents of your existing DB and restore into the supabase-db

from supabase.

myozin-kyaw avatar myozin-kyaw commented on June 18, 2024

I want to connect supabase using external postgres database

supabase .env is as below

#POSTGRES_PASSWORD=bFh9K2GchSexMzJuDU6R73JyshRvdQvw5j3
POSTGRES_PASSWORD=secret123
JWT_SECRET=bFh9K2GchSexMzJuDU6R73JyshRvdQvw5j3
ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.ewogICJyb2xlIjogImFub24iLAogICJpc3MiOiAic3VwYWJhc2UiLAogICJpYXQiOiAxNzEzMzc1MDAwLAogICJleHAiOiAxODcxMTQxNDAwCn0.d151c0IpsFtDUmPv2nftkmGEBnrPKIyg1hdOpYSp_WU
SERVICE_ROLE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.ewogICJyb2xlIjogInNlcnZpY2Vfcm9sZSIsCiAgImlzcyI6ICJzdXBhYmFzZSIsCiAgImlhdCI6IDE3MTMzNzUwMDAsCiAgImV4cCI6IDE4NzExNDE0MDAKfQ.BR85w0U9Ah2ojMU6aQ2ZxlNdizo0VSgNcgk8RRdgvAI
DASHBOARD_USERNAME=supabase
DASHBOARD_PASSWORD=password

############

Database - You can change these to any PostgreSQL database that has logical replication enabled.

############

POSTGRES_HOST=127.0.0.1
POSTGRES_DB=supabase
POSTGRES_PORT=5432
POSTGRES_USER=postgres

Also you provided in docker-compose.yml and docker-compose.s3.yml if i'm using external postgres database comment out below, I've already did that.

and when i run
sudo docker-compose pull
and then
and sudo docker-compose up

it cuases

WARN[0000] /home/ubuntu/supabase/docker/docker-compose.yml: version is obsolete
[+] Running 7/0
✔ Container supabase-rest Running 0.0s
✔ Container supabase-meta Running 0.0s
✔ Container supabase-storage Running 0.0s
✔ Container supabase-vector Running 0.0s
✔ Container supabase-imgproxy Running 0.0s
✔ Container realtime-dev.supabase-realtime Running 0.0s
✔ Container supabase-analytics Running 0.0s
Attaching to realtime-dev.supabase-realtime, supabase-analytics, supabase-auth, supabase-edge-functions, supabase-imgproxy, supabase-kong, supabase-meta, supabase-rest, supabase-storage, supabase-studio, supabase-vector
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:07:52Z"}
supabase-auth | {"args":[0.001804187],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:07:52Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:07:52Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:07:54Z"}
supabase-auth | {"args":[0.008741942],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:07:54Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:07:54Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:07:55Z"}
supabase-auth | {"args":[0.003398431],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:07:55Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:07:55Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:07:56Z"}
supabase-auth | {"args":[0.00171649],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:07:56Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:07:56Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:07:58Z"}
supabase-auth | {"args":[0.001219128],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:07:58Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:07:58Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:08:04Z"}
supabase-auth | {"args":[0.003032842],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:08:04Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:08:04Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:08:16Z"}
supabase-auth | {"args":[0.076254124],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:08:16Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:08:16Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:08:27Z"}
supabase-auth | {"args":[0.005311669],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:08:27Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:08:27Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:08:48Z"}
supabase-auth | {"args":[0.001940699],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:08:48Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:08:48Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:09:18Z"}
supabase-auth | {"args":[0.000961671],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:09:18Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:09:18Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:10:14Z"}
supabase-auth | {"args":[0.07377409],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:10:14Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:10:14Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:11:29Z"}
supabase-auth | {"args":[0.004412912],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:11:29Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:11:29Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:12:39Z"}
supabase-auth | {"args":[0.001625579],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:12:39Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:12:39Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:13:49Z"}
supabase-auth | {"args":[0.003277072],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:13:49Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:13:49Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:14:58Z"}
supabase-auth | {"args":[0.001349933],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:14:58Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:14:58Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:16:06Z"}
supabase-auth | {"args":[0.000791144],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:16:06Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:16:06Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:17:10Z"}
supabase-auth | {"args":[0.143560348],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:17:10Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:17:10Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:18:18Z"}
supabase-auth | {"args":[0.001082704],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:18:18Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:18:18Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:19:24Z"}
supabase-auth | {"args":[0.00183924],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:19:24Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:19:24Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:20:31Z"}
supabase-auth | {"args":[0.001148786],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:20:31Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:20:31Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:21:37Z"}
supabase-auth | {"args":[0.00186867],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:21:37Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:21:37Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:22:40Z"}
supabase-auth | {"args":[0.001070979],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:22:40Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:22:40Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:23:45Z"}
supabase-auth | {"args":[0.00547081],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:23:45Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:23:45Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:24:52Z"}
supabase-auth | {"args":[0.002036858],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:24:52Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:24:52Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:25:59Z"}
supabase-auth | {"args":[0.070230252],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:25:59Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:25:59Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:27:06Z"}
supabase-auth | {"args":[0.142635812],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:27:07Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:27:07Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:28:16Z"}
supabase-auth | {"args":[0.001658145],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:28:16Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:28:16Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:29:22Z"}
supabase-auth | {"args":[0.001096545],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:29:22Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:29:22Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:30:29Z"}
supabase-auth | {"args":[0.553412127],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:30:30Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:30:30Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:31:36Z"}
supabase-auth | {"args":[0.001437791],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:31:36Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:31:36Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:32:41Z"}
supabase-auth | {"args":[0.00191478],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:32:41Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:32:41Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:33:49Z"}
supabase-auth | {"args":[0.000857206],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:33:49Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:33:49Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:34:54Z"}
supabase-auth | {"args":[0.003104551],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:34:54Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:34:54Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:36:01Z"}
supabase-auth | {"args":[0.001528339],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:36:01Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:36:01Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:37:07Z"}
supabase-auth | {"args":[0.003694005],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:37:07Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:37:07Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:38:12Z"}
supabase-auth | {"args":[0.001180107],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:38:12Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:38:12Z"}
supabase-auth | {"level":"info","msg":"Go runtime metrics collection started","time":"2024-04-21T05:39:18Z"}
supabase-auth | {"args":[0.00114214],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-04-21T05:39:18Z"}
supabase-auth | {"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to host=127.0.0.1 user=postgres database=supabase: dial error (dial tcp 127.0.0.1:5432: connect: connection refused)","time":"2024-04-21T05:39:18Z"}
supabase-analytics | {"Kernel pid terminated",application_controller,"{application_start_failure,logflare,{{shutdown,{failed_to_start_child,'Elixir.Cainophile.Adapters.Postgres',econnrefused}},{'Elixir.Logflare.Application',start,[normal,[]]}}}"}
supabase-analytics | Kernel pid terminated (application_controller) ({application_start_failure,logflare,{{shutdown,{failed_to_start_child,'Elixir.Cainophile.Adapters.Postgres',econnrefused}},{'Elixir.Logflare.Application',start,[normal,[]]}}})
supabase-analytics |
dependency failed to start: container supabase-analytics is unhealthy

How to solve that please

from supabase.

Hallidayo avatar Hallidayo commented on June 18, 2024

Hi @myozin-kyaw - Just checking in here, are you still experiencing the same issue?

from supabase.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.