-
Notifications
You must be signed in to change notification settings - Fork 213
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
Got Degraded issue when deployed in Coolify. #1623
Comments
Do you have an idea why it says "unhealthy", and under what conditions? Does it work properly or do you have issues reaching out to the Checkmate dashboard? |
I have no idea why it says "unhealthy", maybe because of the image version that they use to build. I've tried to restart the degraded service and it's healthy for a few moments and change to unhealthy again. It doesn’t work at all, can't access the Checkmate dashboard. |
@khemmapon please have a look at the probably it could be resolved by deleting the mongo volume, but then all you data will be gone. So maybe its a simple issue thats visiible in the mongo logs :) |
Here's the logs. I think I have to change the image for that. ![]() |
It means that MongoDB failed to start because your system's CPU does not support AVX (Advanced Vector Extensions). Currently MongoDB 5.0 needs this. We don't have a time frame to support such CPUs, for now. |
Describe the bug
Got Degraded issue when deployed in Coolify. The issue is with Mongodb container.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect everything’s running and healthy.
Screenshots
The text was updated successfully, but these errors were encountered: