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

I can't run the relay nostream-db is unhealthy [BUG] #345

Closed
Karibura-Cyber opened this issue Dec 2, 2023 · 4 comments
Closed

I can't run the relay nostream-db is unhealthy [BUG] #345

Karibura-Cyber opened this issue Dec 2, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@Karibura-Cyber
Copy link

When I run ./script/start it failed

[+] Running 1/0 ✔ Container nostream-cache Running 0.0s Attaching to nostream, nostream-cache, nostream-db, nostream-migrate dependency failed to start: container nostream-db is unhealthy
@Karibura-Cyber Karibura-Cyber added the bug Something isn't working label Dec 2, 2023
@cameri
Copy link
Owner

cameri commented Dec 2, 2023

Whats the output of docker logs nostream-db ?

@Karibura-Cyber
Copy link
Author

Now I can fix it. I set postgresql config and restart again
thanks.

@asyscom
Copy link

asyscom commented Jan 18, 2024

Now I can fix it. I set postgresql config and restart again thanks.

HI, could you explane as fixed? I cant
Thank you

@anasfik
Copy link

anasfik commented Jan 28, 2024

Now I can fix it. I set postgresql config and restart again thanks.

HI, could you explane as fixed? I cant Thank you

I faced the same issue, it was caused because the resources I was using (1vCPU and 2 RAM) were low compared to what its expected, and so the default configuration set in the postgresql.conf file for the PostgreSQL, precisely the max_connections and shared_buffers value should be reduced, as example if shared_buffers was set to 2GB, try set it to 1GB, 512MB... until it doesn't exceed the available shared memory by PostgreSQL. This applies also to max_connections configuration.

Alternativly, if you were using a VM on the cloud, you can just resize it with higher resources.

if this don't apply to your issue, try running docker logs nostream-db and see the logs there, it should inform about the issue so you can then address it.

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

4 participants