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

[Bug]: supabase_realtime_secondbrain container is not ready: unhealthy #3377

Open
zhukelili opened this issue Oct 16, 2024 · 5 comments
Open
Labels
bug Something isn't working

Comments

@zhukelili
Copy link

What happened?

When I execute the command cd backend && supabase start, the following error appears. How can I fix it?

Relevant log output

----- Native stack trace -----

 1: 0xcc7e17 node::Assert(node::AssertionInfo const&) [node]
 2: 0xd4818e node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
 3: 0xd4826c node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
 4: 0xc7bd07  [node]
 5: 0xc7d264 node::Start(int, char**) [node]
 6: 0x7f076b26e24a  [/lib/x86_64-linux-gnu/libc.so.6]
 7: 0x7f076b26e305 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
 8: 0xbd12ee _start [node]
Stopping containers...
supabase_realtime_secondbrain container is not ready: unhealthy
Error status 503:
supabase_pg_meta_secondbrain container is not ready: unhealthy
supabase_studio_secondbrain container is not ready: unhealthy

Twitter / LinkedIn details

No response

@zhukelili zhukelili added the bug Something isn't working label Oct 16, 2024
Copy link

linear bot commented Oct 16, 2024

Copy link

dosubot bot commented Oct 16, 2024

Hello, @zhukelili! I'm a bot designed to help you solve bugs, answer questions, and become a contributor. I'm here to assist you while you wait for a human maintainer.

I couldn't find specific information about the supabase_realtime_secondbrain container, but there is a similar issue with the supabase_vector_secondbrain container being unhealthy. The suggested solution for that issue includes ensuring that all necessary environment variables are correctly set, such as openai_api_key, azure_openai_embeddings_url, supabase_url, supabase_service_key, pg_database_url, pg_database_async_url, and embedding_dim. Additionally, check the backend/ci-migration.sh script for PROJECT_ID, SUPABASE_ACCESS_TOKEN, and SUPABASE_DB_PASSWORD [1].

If the issue persists, consider checking the Docker logs for more specific error messages related to the health checks. The logs might indicate a network issue, which could be related to Docker's network configuration or a firewall setting. You can try updating Docker Desktop, restarting it, checking firewall settings, and ensuring no other containers are conflicting with the supabase_realtime_secondbrain container [1].

To continue talking to Dosu, mention @dosu.

@zhukelili
Copy link
Author

CORE-238 [Bug]: supabase_realtime_secondbrain container is not ready: unhealthy

thanks,but
image

@StanGirard
Copy link
Collaborator

Can you try to do a supabase stop and then a supabase start?

@zhukelili
Copy link
Author

zhukelili commented Oct 19, 2024

Can you try to do a supabase stop and then a supabase start?

I found the reason why the program failed to start on other websites: insufficient local disk space. When I used a computer with enough space, it could start normally.

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

2 participants