mirror of
https://github.com/0xJacky/nginx-ui.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #1240] System got stuck after the docker container started #5108
Labels
No labels
Q/A
bug
casdoor
dependencies
docker
documentation
duplicate
enhancement
help wanted
invalid
lego
platform:openwrt
platform:windows
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-ui#5108
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @iyinchao on GitHub (Jul 17, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1240
Describe the bug
When I updated to the latest version,
about 1~5 min After the container started, the system CPU usage is 100% and cause everything stuck.
Info:
sha256:8624f7eca70b77310711aad6df5e808a089578e18c3f3df8afc4e06d965c8426What happened w/ Logs
However the first run is pretty normal in terms of proxy functionality, and I access to the nginx web ui without problem.
The other day when I access apps proxied by nginx, I found the unraid system get stuck, and all cpu cores is 100% usage.
After a while, event the unraid web ui also crashed.
I remember I'm uploading videos to the server that moment, but I'm not sure if it is related.
Then I checked the logs:
It says OOM but the system do have plenty of free memory.
The older version worked pretty well so I think this might be related to the update. Can you help with the problem, I can upload the full log if it helps, thank you.
@0xJacky commented on GitHub (Jul 18, 2025):
Thank you for the feedback.
Based on the error log you provided, I have modified the code for the configuration file indexing function. You can use the image with the
devtag (uozi/nginx-ui:dev) to test if the problem has been resolved.Also, regarding the errors in the first part, you can resolve them by logging into your account again.
If the CPU usage still reaches 100% and the OOM issue persists after the update, please provide the parameters used for container startup and logs.
@iyinchao commented on GitHub (Jul 18, 2025):
@0xJacky Thank you for the quick response ❤️
I tried the
devimage, but unfortunately, the issue still persists.It seems the problem might be related to uploading large images and videos through the proxy.
I monitored the memory usage during the upload process this time and noticed that it rapidly increases, eventually consuming all available system memory. 🤕
Docker Paramters:
-v /var/run/docker.sock:/var/run/docker.sock, wtih port & volume mapping, and custom network.Log:
The warning added in
b8e017eis present in log:@0xJacky commented on GitHub (Jul 18, 2025):
It seems that the cache indexer mistakenly cached the nginx cache. I will solve this problem tomorrow. For now, perhaps you can modify the configuration to move the cache out of /etc/nginx, for example, to /tmp.
@0xJacky commented on GitHub (Jul 19, 2025):
I have updated the memory usage limit of the indexer, and at the same time we have ignored some common cache folder names. Now, the problem of excessive CPU and memory usage of the indexer should be resolved. You can use the newer dev image
uozi/nginx-ui:devto test whether the issue has been resolved.@iyinchao commented on GitHub (Jul 19, 2025):
I tried the
devversion and the issue is resolved, Thank you! ❤️