January 30, 20224 yr Background info: Unraid 6.9.2 Container: lscr.io/linuxserver/qbittorrent latest version. Symptoms: notification from *arrs, that they cannot communicate with qbittorrent, qbittorrent does either stay up or reload, but functions incorrectly until docker engine is restarted. So here's where I'm at. I think it may be a IO flooding issue due to a high amount of torrents (2200) in qbittorrent. However, stopping/starting/restarting the container doesn't fix it. Some torrents will still connect, but many torrents will stall out/fail to upload. For perspective, after a crash/issue, my active torrents goes down to 3-5 with a bit of upload or download. I had several torrents going, only getting 1-5 mbps down. I stopped the array, and restarted the array, and immediately it shot up to 50+ mbps of traffic and 10-15 active with the same torrents. I have noticed in the unraid log that there is a " kernel: TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters." message. I have theorized that the high number of torrents is causing some sort of rate limiting on the container/docker. Oddly, I don't think the issue is inside the container as a restart of the container doesn't help, you must restart docker as a whole for the communication to go back to normal. Ideas? Logs attached. gladiator-diagnostics-20220130-1148.zip
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.