qBittorrent inadvertently crashing while downloading
Posted: Sun Dec 29, 2024 11:54 pm
Docker Image: ghcr.io/linuxserver/qbittorrent:latest (5.0.3-r0-ls369)
For the past few weeks, whenever I am downloading a torrent that is relatively large (usually > 10GB), my qBittorrent container will crash and restart. I imagine it's a memory issue that's causing it to be killed or something along those lines. I tried to debug with logs from multiple places, but none were helpful. When I checked the docker logs: this is the only thing that shows up before restarting
I check for something useful and there's nothing useful there either. However, when I check the container stats, it shows that my qBittorrent container frequently uses multiple GiB of memory despite the physical memory usage limit being set to 512 MiB in the WebUI.
There's also nothing useful to be seen in dmesg that I could find, or at least nothing related to memory.
I also see in Proxmox around the time the container crashes, the memory usage on the VM (which no matter how much memory I give it, it always ends up at 95+% usage) plummets to ~10% usage and slowly rises back to 95%.
Has anyone else ran into something similar to this, and if so, have you been able to fix it?
For the past few weeks, whenever I am downloading a torrent that is relatively large (usually > 10GB), my qBittorrent container will crash and restart. I imagine it's a memory issue that's causing it to be killed or something along those lines. I tried to debug with logs from multiple places, but none were helpful. When I checked the docker logs: this is the only thing that shows up before restarting
Code: Select all
Catching signal: SIGTERM
Exiting cleanly
Code: Select all
qbittorrent/config/qBittorrent/logs
There's also nothing useful to be seen in dmesg that I could find, or at least nothing related to memory.
I also see in Proxmox around the time the container crashes, the memory usage on the VM (which no matter how much memory I give it, it always ends up at 95+% usage) plummets to ~10% usage and slowly rises back to 95%.
Has anyone else ran into something similar to this, and if so, have you been able to fix it?