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 #1337] Check-Health at 100% CPU usage #1066

New issue

Closed

opened 2026-02-26 06:35:38 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:35:38 +03:00

Owner

Originally created by @twihno on GitHub (Aug 21, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1337

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug
The check-health script starts to use 100% of the resources of one CPU core until the container is restarted again.
Unfortunately, I do not know when exactly this starts to happen.
I can confirm that this problem already existed in v2.9.6 and “survived” a recreation of the app container.
I did neither recreate the database in the meantime nor delete/clear the app volumes.

Nginx Proxy Manager Version
v2.9.7

To Reproduce
Steps to reproduce the behavior:

Start Docker container
Use proxy and wait

Expected behavior
Running the check health script shouldn't result in a 100% CPU usage

Screenshots
docker status:

CONTAINER ID   NAME          CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS
############   nginx_app_1   100.44%   135.1MiB / 7.627GiB   1.73%     534MB / 525MB     93.4MB / 86kB	   ####

htop:

CPU%    MEM%   TIME+      Command
100.0   0.0    80h11:30   /bin/bash /bin/check-health

Operating System
Ubuntu Server 21.04 on rpi 4 8GB

Additional context
Docker version 20.10.8, build 3967b7d

Originally created by @twihno on GitHub (Aug 21, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1337 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** The check-health script starts to use 100% of the resources of one CPU core until the container is restarted again. Unfortunately, I do not know when exactly this starts to happen. I can confirm that this problem already existed in v2.9.6 and “survived” a recreation of the app container. I did neither recreate the database in the meantime nor delete/clear the app volumes. **Nginx Proxy Manager Version** v2.9.7 **To Reproduce** Steps to reproduce the behavior: 1. Start Docker container 2. Use proxy and wait **Expected behavior** Running the check health script shouldn't result in a 100% CPU usage **Screenshots** docker status: ``` CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS ############ nginx_app_1 100.44% 135.1MiB / 7.627GiB 1.73% 534MB / 525MB 93.4MB / 86kB #### ``` htop: ``` CPU% MEM% TIME+ Command 100.0 0.0 80h11:30 /bin/bash /bin/check-health ``` **Operating System** Ubuntu Server 21.04 on rpi 4 8GB **Additional context** Docker version 20.10.8, build 3967b7d

kerem

2026-02-26 06:35:38 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:35:38 +03:00

Author

Owner

@twihno commented on GitHub (Aug 21, 2021):

docker restart nginx_app_1 nginx_db_1 doesn't work either

@twihno commented on GitHub (Aug 21, 2021): ```docker restart nginx_app_1 nginx_db_1``` doesn't work either

kerem commented

2026-02-26 06:35:38 +03:00

Author

Owner

@jc21 commented on GitHub (Aug 22, 2021):

Hmm I do see spikes when the healthcheck is running but it's immediately back to nothing for me.

Docker healthchecks have been found to be horrible on performance for the docker host recently. I wanted to remove the healthcheck from this project and instead people who want it can add it to their docker-compose file. I've hesitated to do this as it would mean anyone with external monitoring setup would have it fail.

But I think I'll remove it anyway, this seems like a good enough reason.

@jc21 commented on GitHub (Aug 22, 2021): Hmm I do see spikes when the healthcheck is running but it's immediately back to nothing for me. Docker healthchecks have been found to be horrible on performance for the docker host recently. I wanted to remove the healthcheck from this project and instead people who want it can add it to their docker-compose file. I've hesitated to do this as it would mean anyone with external monitoring setup would have it fail. But I think I'll remove it anyway, this seems like a good enough reason.

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#1066

No description provided.

Rows
Columns