mirror of
https://github.com/qdm12/ddns-updater.git
synced 2026-07-31 01:38:17 -04:00
Bug: Swap memory almost entirely consumed by ddns-updater #405
Reference in New Issue
Block a user
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 @TheCarrotStick on GitHub (May 22, 2024).
TLDR: Describe your issue in a one liner here
SWAP space almost entirely consumed by ddns-updater no matter what the swap space is on the system after some time of the container running.
htopI see the container showing as a process called 'app'. When digging into it I see the path /updater/app that helped me to originally identify this was coming from ddns-updater and it was an in-container path. Stopping ddns-updater resolved this. I added the memory limits to the compose file to see if I could limit the app's usage, but it barreled past that so I assume that's not doing much, haha.Logs:
Nothing unusual in the logs.
Configuration file (remove your credentials!):
Host OS:
Ubuntu 22.04.4 LTS x86_64
@qdm12 commented on GitHub (May 23, 2024):
That's strange, what does
docker statssay? Mine uses 9.3MB of ram. Does it increase slowly over time?How did you identify using htop that ddns-updater was at fault for the swap space being used all up?
By the way, I just changed it from
/updater/appto/updater/ddns-updaterin commit8e09cd6342since that was indeed unclear in terms of process name@TheCarrotStick commented on GitHub (May 24, 2024):
Appreciate that, it was definitely a bit of a chase to figure out where that was initially, haha. Looks like it calmed back down now. Once my alert goes off again I'll visit

docker statsagain.@TheCarrotStick commented on GitHub (Jun 3, 2024):
Hey, I think I've resolved my swap space issue, it wasn't the ddns-updater app, but it looked to be gluetun. I added
DOT=offto get rid of unbound and my swap space has drastically improved with only 10% usage at most across my entire stack of containers. Thank you!@qdm12 commented on GitHub (Jun 14, 2024):
That's strange. Unbound does use memory for sure, due to its blocklists mostly, but it should stay at around 500MB.
This is changing soon (after next release) with https://github.com/qdm12/gluetun/issues/137 and memory is a bit reduced as far as I've seen. Feel free to subscribe to that issue 😉