Closed critzo closed 4 years ago
Noting that @jheretic identified this as a stalled or shutdown container, and was investigating the cause.
I suspect it might have been a memory issue on the VM, and the OOM killer got it. Memory usage seems stable so far, so we're not likely to get more info unless it happens again. I'm going to suggest modifying the default docker-compose setup so that containers auto-restart on failure, and look into the possibility of adding prometheus metrics if that's easy to do. Does that sound good @critzo?
That sounds good to me, yes.
@jheretic @critzo would it be helpful to open a new issue for the modification and close this out?
Yes @rudietuesdays Let's open a new issue for the OOM issue. Thanks.
Sounds good, closing this one out!
Attempting to test adding more device data today, I see a 502 Bad Gateway Error when attempting to load the site.