Ive been getting some sporadic garbage performance with both flood and rutorrent. Roughly half the time, they will hang on doing anything, which is due to being unable to communicate with rtorrent. This is both during startup, and during any other time.
Symptoms include:
Not being able to load either ui. rutorrent says "The request to rTorrent has timed out." and flood just hangs on its loading page
(Flood Specific)
Speeds on both ul/dl drop to < 100kbps
Speeds and other stats stop updating
It hangs when changing settings or adding a torrent, it just stays on the prompt with the wheel spinning. It may eventually go back to the main screen, but usually the torrent has been added.
I am unable to tell if this is just during periods of heavy use or just random, because it happens so often.
I have ~140 torrents loaded, none of them outrageously large.
I have a very beefy server that is using maybe 5% of cpu/ram, so its not resource constrained.
My cache has 2ssds that have loads of free space, and no issues with those drives or my actual hdd pool.
There are no reverseproxy/nginx things going on, this purely default.
I wanted to see what could happen if rtorrent used a local socket instead of a scgi port, but the socket seems to not work properly.
I told rtorrent the socket was both in /home/nobody/rtorrent/rtorrent.sock, and ~/rtorrent/rtorrent.sock, same with flood. If I killed the rtorrent that spawns when starting the docker, it started up fine.
I also altered the flood.sh/rutorrent.sh to skip scanning for the open 5000 port to make sure they actually launched, but both hanged and I couldnt tell why. I didnt test killing them and starting them myself, since theres a bit of work your scripts do, and didnt want to just blindly start them, since I might have missed something the startup scripts do (such as copying configs and sessiondata, etc.)
Edit: The vpn is disabled and never has been enabled.
Let me know if you need any more information.
Thanks!