I am running Unraid v6.12.9

 

I have an issue where if I leave the web UI of a qBittorrent instance on for too long in a browser tab, it uses all available RAM and crashes the whole server. I can ping the server but not access the Unraid web UI any more or the shares.

 

I set the --memory flag on the container(s) to limit RAM usage and prevent crashing, but then the instance hits the limit, crashes, and resets itself, which is a problem. This creates a lot of ghost peers and losing upload stats, by not announcing to trackers before the crash.

 

The middle client has 804 torrents with only a maximum of 8 being allowed active to seed, which is causing the biggest issue as it increases in RAM the fastest out of the three.

 

When the problem begins by accessing the web UI:

 

 

End result just before a server crash (bottom container crashed itself and uptime reset):

 

 

Total RAM:

 

 

Edited March 30, 20242 yr by Unraidmule

Suggest posting in the container support thread/discoed:

 

 

1 hour ago, JorgeB said:

Suggest posting in the container support thread/discoed:

 

 

 

Thanks for the reply, since it is happening with all qBit containers from different docker images — so I would have to post the same to the maintainers of each container?

You can try one of them first, or post in all.

If it's affecting all then it's likely nothing the container maintainers can do something about, but something with the qbittorrent app itself.