wisemanofhyrule

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

wisemanofhyrule's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Has Flood stopped working with the new update for anyone else? Rutorrent works fine, but flood isnt. Im seeing 2019-01-06 00:01:11,964 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 22911187286784 for <Subprocess at 22911187284840 with name flood-script in state RUNNING> (stdout)> 2019-01-06 00:01:11,964 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 22911187287072 for <Subprocess at 22911187284840 with name flood-script in state RUNNING> (stderr)> 2019-01-06 00:01:11,964 INFO exited: flood-script (exit status 0; expected) In the logs.
  2. So I did a little bit more digging (it took a while), and every time rtorrent goes unresponsive, the process is in an "uninterruptible sleep" according to top, so it has something to do with I/O and is probably page faults. So I look into the control groups stats (https://docs.docker.com/config/containers/runmetrics/#control-groups) to check the memory metrics, and I see the following: total_pgpgin 27153324 total_pgpgout 25232442 total_pgfault 29154873 And this is for a container thats been running for ~13 hours, its hitting page faults more than its paging data in normally. Its not my hardware going bad since this only happens on containers using rtorrent (I chedked both this one and the LinuxServer.io one). I have other containers running that are doing perfectly fine. At least I now know why rtorrent has been hanging up these past few months, I have no clue what to do about it though.
  3. Ive been having that issue for a while, see my post here for some info I tried to come up with. I think its the scgi port just being slow for some reason.
  4. 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!
  5. Updated and progress is showing up. Thanks!
  6. There isnt a progress bar when I do any transfers. I did some digging around and any similar issues I found were how kde plasma would have them in the notification tray, which I cant find to save my life here. So it possibly has something to do with that.