Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

service not healthy: [supabase_vector_chatgpt-your-files] #42

Open
Gourav-21 opened this issue Jul 1, 2024 · 3 comments
Open

service not healthy: [supabase_vector_chatgpt-your-files] #42

Gourav-21 opened this issue Jul 1, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@Gourav-21
Copy link

Bug report

it doesnt start at all when ever i try to run it locally it says service not healthy

Describe the bug

$ npx supabase start
0.28.1-alpine: Pulling from supabase/vector
d261077062b2: Pull complete
2babd04ec7b1: Pull complete
6bbeea27f58c: Pull complete
2b092e92b1a0: Pull complete
9ced58d1ef15: Pull complete
4f4fb700ef54: Pull complete
Digest: sha256:4bc04aca94a44f04b427a490f346e7397ef7ce61fe589d718f744f7d92cb5c80
                                                                               Status: Downloaded newer image for public.ecr.aws/supabase/vector:0.28.1-alpine
supabase_vector_chatgpt-your-files container logs:
                                                  2024-07-01T09:52:25.868166Z  INFO vector::app: Internal log rate limit configured. internal_log_rate_secs=10
                                                                                                                                                              2024-07-01T09:52:25.868467Z  INFO vector::app: Log level is enabled. level="vector=info,codec=info,vrl=info,file_source=info,tower_limit=trace,rdkafka=info,buffers=info,lapin=info,kube=info"
                                                                                                                                                                             2024-07-01T09:52:25.869380Z  INFO vector::app: Loading configs. paths=["/etc/vector/vector.yaml"]
                                                                                                2024-07-01T09:52:25.889166Z  WARN vector::config::loading: Transform "kong_err" has no consumers
                  2024-07-01T09:52:25.889218Z  WARN vector::config::loading: Transform "router._unmatched" has no consumers
                                                                                                                           2024-07-01T09:52:26.019487Z  INFO vector::topology::running: Running healthchecks.
                               2024-07-01T09:52:26.019924Z  INFO vector::topology::builder: Healthcheck passed.
                                                                                                               2024-07-01T09:52:26.019936Z  INFO vector::topology::builder: Healthcheck passed.
                 2024-07-01T09:52:26.019939Z  INFO vector::topology::builder: Healthcheck passed.
                                                                                                 2024-07-01T09:52:26.019942Z  INFO vector::topology::builder: Healthcheck passed.
   2024-07-01T09:52:26.019944Z  INFO vector::topology::builder: Healthcheck passed.
                                                                                   2024-07-01T09:52:26.019947Z  INFO vector::topology::builder: Healthcheck passed.
                                                                                                                                                                   2024-07-01T09:52:26.019949Z  INFO vector::topology::builder: Healthcheck passed.
                                                                     2024-07-01T09:52:26.020132Z  INFO source{component_kind="source" component_id=docker_syslog component_type=syslog component_name=docker_syslog}: vector::sources::util::net::tcp: Listening. addr=0.0.0.0:9000
                                                                                                     2024-07-01T09:52:26.020207Z  INFO vector: Vector has started. debug="false" version="0.28.1" arch="x86_64" revision="ff15924 2023-03-06"
                                                               2024-07-01T09:52:26.027480Z  INFO vector::internal_events::api: API server running. address=0.0.0.0:9001 playground=http://0.0.0.0:9001/playground
                                   service not healthy: [supabase_vector_chatgpt-your-files]
Try rerunning the command with --debug to troubleshoot the error.

A clear and concise description of what the bug is.

To Reproduce

npx supabase start

Expected behavior

it should run

Screenshots

If applicable, add screenshots to help explain your problem.

System information

  • OS: windows 11
  • Version of supabase-js: latest
  • Version of Node.js: v20.12.2
@Gourav-21 Gourav-21 added the bug Something isn't working label Jul 1, 2024
@gregnr
Copy link
Collaborator

gregnr commented Jul 5, 2024

Hey @Gourav-21. Sorry to hear you're facing this - this is the first I've heard of this issue. Confirming that you are working from a clean clone of the repo on the main branch with no existing docker containers running prior to npx supabase start?

@Gourav-21
Copy link
Author

Gourav-21 commented Jul 5, 2024

@gregnr yes there was a supabase docker running but i stopped it before starting this one but it didnt work. then i thought maybe it was because of the prev docker that i was running so i factory reset the docker and started it again but still it didnt work

so i did it in cloud

and just so you know the chat edge function also doesnt work, i had to create the api in next js then it worked

@DuncanLHS
Copy link

@Gourav-21 I too have had this issue and have discussed and attempted to troubleshoot with a couple of other users in the Supabase discord but it doesn't seem to be affecting everyone. I haven't seen a fix I'm afraid but turning analytics off appears to be a good workaround for now. You can disable it in the config.toml.
The problem seems to stem from an update to some of the supabase docker images around a week ago but I can't be sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants