-
Out of memory error
Thanks, will do that
-
Out of memory error
Yeah, i've never seen my host system go above 14 Gigs of RAM so its unlikely to be the Host system. I'll give the qBit instance in question 4 Gigs of RAM Thanks for your patience.
-
Out of memory error
Heavyweight dockers I'm running are multiple qBits, Jellyfin, Immich, Nextcloud
-
Out of memory error
But some of them are databases which use next to no RAM
-
Out of memory error
Yeah I'm running a lot of containers, around 38 containers
-
Out of memory error
So it's actually not my Host system running out of total memory but instead the Docker Container overflowing the RAM
-
Out of memory error
Yeah exactly -> the total memory assigned to the container is 2118364kB, which should be the 2GB I assigned in the Webinterface, correct?
-
Out of memory error
Astaroth kernel: Memory cgroup out of memory Thats the line in the syslog that got me thinking about that
-
Out of memory error
Actually, I got a question, if the qBit client runs out of memory if you limit it via the WebInterface / Docker command and it overflows, it also gets killed. Could the entries in the log mean the client reached the memory threshhold?
-
Out of memory error
Or did you mean something else? What exactly means folder mapped correctly? I assume it's that all persistent storage folders are on a drive like Cache or Array drive, yes?
-
Out of memory error
Folders are mapped correctly, all folders are mapped to either the cache or the array. Also, all my containers are RAM-limited so technically that shouldn't happen? Where in the logs did you find the entry?
-
Out of memory error
During my weekly scan of the Fix Common Problems Plugin I got the following error message: "Out Of Memory errors detected on your server" The forum post of the plugin said to post here in the support forum so here I am. My server is a pretty powerful server, it's running Unraid 7.1.0, has 32 GB DDR5 RAM, XMP / EXPO profile is NOT enabled so RAM is running at base speed. I am running two cache NVMEs SSDs in RAID 1 and 3 Array HDDs with one assigned for Parity. I have encountered a weird issue three days ago where Docker containers refused to update and my assumption was that the Docker.img file ran out of space so I increased it from the default 20GB to 30GB. After some manual cleanup I managed to update the Containers just fine and the system has been rock stable since then. So I don't really got any idea where the error could be coming from. I would appreciate your help, diagnostics attached. astaroth-diagnostics-20250516-1413.zip
Shochraos
Members
-
Joined
-
Last visited