Status unhealthy after server reset #1257
-
|
Recently my server restarted and now my NPM status health marked as This is all the information I have and I can think it may be relevant. The option Update: I fount at some point the container exited with code 137 (OMM - Out of memory). I cleared the memory and I even restarted the server but it still happening... |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Solved it by turning down the stack, and turning it up again with a different name (the name of the containers remain the same). |
Beta Was this translation helpful? Give feedback.
-
|
Glad it’s working.
Did you try bringing down the stack and bringing it back up without changing the name? That’s usually all I have to do when this happens.
(I’m not so sure this is an NPM thing so much as docker getting confused. It happens to me every once and a while on various non-NPM containers.)
… On Jul 23, 2021, at 6:57 AM, Kenny Lajara ***@***.***> wrote:
Solved it by turning down the stack, and turning it up again with a different name (the name of the containers remain the same).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#1257 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGI5CYSS665KY77VSPDUGW3TZFKL3ANCNFSM5A3E3IKA>.
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, I tried it without changing the stack name, I don't know why it didn't work. Also, I'm not sure if it's an NPM or Docker thing. I was using traditional hosting before and I just have about half a year using docker. This is the first time it's happened to me. |
Beta Was this translation helpful? Give feedback.
Solved it by turning down the stack, and turning it up again with a different name (the name of the containers remain the same).