-
Notifications
You must be signed in to change notification settings - Fork 18
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
sudden crash how to troubleshoot ? #11
Comments
Same here. This started happening recently. Yesterday it fixed it self, now its again not working.
I tried older versions of the image, but it didn't solve it. |
I'm having the same issue. Started a few weeks ago. |
i tried a few things nothing worked :/ |
HI! @P6g9YHK6 @danyal @DanielHani Remove the file "healthcheck-disable" at the root and restart your stack ;) |
Worked! Thank you! Any idea why this would happen? Is this something that will randomly keep happening? |
It's related to this script. We should ask testdasi https://github.com/testdasi/static-ubuntu/blob/main/grafana-unraid-stack/healthcheck.sh |
Removing it helps but it gets recreated all the time. |
Had this same issue show today for the first time. Deleting the healthcheck-disable worked for me as well. Curious as to why it popped up. Might be an issue since I stop and restart the container every night for my appdata backup. |
Worked well for me thanks @testdasi should maybe have a look at this. |
Any updates on this one? The file keeps getting recreated. I have to remove it every other day which is very annoying. :( |
from one day to the next my stack stopped working i have got no information except the docker logs:
[info] Initialisation started...
[info] influxdb fixed.
[info] loki fixed.
[info] hddtemp fixed.
[info] telegraf fixed.
[info] promtail fixed.
[info] grafana fixed.
[info] Initialisation complete
[info] Runing apps...
[info] All done
[error] influxdb crashed!
[error] loki crashed!
[error] hddtemp crashed!
[error] telegraf crashed!
[error] promtail crashed!
[error] grafana crashed!
how can i fix this ?
The text was updated successfully, but these errors were encountered: