starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #721] NPM keeps exiting with status:unhealthy and code 137 - out of memory issues? #611

New issue

Closed

opened 2026-02-26 06:33:39 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 06:33:39 +03:00

Owner

Originally created by @vmavromatis on GitHub (Nov 15, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/721

Version: Latest (2.6.2)
Hardware Raspberry Pi 3B (1GB RAM)

So far this happened 3 times. NPM works perfectly for a few hours and then suddenly dies while all other containers keep running fine. SS from portainer:

The error I see is Exited with 137
Inspect:

Logs (don't show any errors - crash happened at 6:29AM, nothing at that moment):

I suspect that my RPi might be running OOM? But last I checked htop the RAM was at 600MB/1GB so quite far from full. Any ideas?

PS: I have put Restart Policy as Always in order to alleviate this...

Originally created by @vmavromatis on GitHub (Nov 15, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/721 Version: Latest (2.6.2) Hardware Raspberry Pi 3B (1GB RAM) So far this happened 3 times. NPM works perfectly for a few hours and then suddenly dies while all other containers keep running fine. SS from portainer: ![image](https://user-images.githubusercontent.com/8668731/99179476-d1fa1480-2726-11eb-9d39-cad3e80f7f68.png) The error I see is Exited with 137 Inspect: ![image](https://user-images.githubusercontent.com/8668731/99179529-77ad8380-2727-11eb-8172-0c5aec92104b.png) Logs (don't show any errors - crash happened at 6:29AM, nothing at that moment): ![image](https://user-images.githubusercontent.com/8668731/99179543-885df980-2727-11eb-9a8e-64cf145912cb.png) I suspect that my RPi might be running OOM? But last I checked `htop` the RAM was at 600MB/1GB so quite far from full. Any ideas? PS: I have put Restart Policy as `Always` in order to alleviate this...

kerem

2026-02-26 06:33:39 +03:00

closed this issue
added the
stale

product-support
labels

kerem commented

2026-02-26 06:33:39 +03:00

Author

Owner

@olonsoft commented on GitHub (Nov 18, 2020):

Same here !

@olonsoft commented on GitHub (Nov 18, 2020): Same here !

kerem commented

2026-02-26 06:33:39 +03:00

Author

Owner

@jc21 commented on GitHub (Nov 18, 2020):

Ignore my previous (deleted) comment, I jumped the gun there.

I've been running NPM on a few different servers including some older architecture ones for a while and this hasn't happened. I'd say the always restart policy is probably the best temporary solution for now without being able to reproduce this myself.

@jc21 commented on GitHub (Nov 18, 2020): Ignore my previous (deleted) comment, I jumped the gun there. I've been running NPM on a few different servers including some older architecture ones for a while and this hasn't happened. I'd say the always restart policy is probably the best temporary solution for now without being able to reproduce this myself.

kerem commented

2026-02-26 06:33:39 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 23, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 23, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:33:39 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 3, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (May 3, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#611

No description provided.

Rows
Columns