rutorrent-flood-docker
rutorrent-flood-docker copied to clipboard
How exactly do you get the torrent-queueing to work?
So far I've done the touch config/.pyroscope/run/pyrotorque
, looked over the torque.ini file and adjusted the max concurrent torrents, but there are a ton of settings I don't know what are there for. Maybe add a small section in the README.MD about setting it up? Like what folders (if any) are scanned, what settings are needed (at a minimum) to make it work. This feature is probably the biggest reason why I got this excellent Docker-image over the stock LSIO rutorrent that I have been running for probably two years now.
I think pyrocore documentation is out of the scope of the container itself. Following pyrocore documentation it says that torque.ini.default file contains a small description of all the parameters you can use. You can look at this file inside the .pyrocore directory.
Well, after overhauling some configs and pointing as much as possible to absolute paths instead of relying on "~/", I'm left with these errors:
DEBUG:pyrocore.scripts.pyrotorque.RtorrentQueueManager:Options: config_dir=None, config_file=[], cron=True, debug=False, defines=[], dry_run=False, guard_file=None, no_fork=False, pid_file=None, quiet=False, restart=False, status=False, stop=False, verbose=True
DEBUG:pyrocore.util.load_config.ConfigLoader:Loading '/root/.pyroscope/config.ini'...
WARNING:pyrocore.util.load_config.ConfigLoader:Configuration file '/root/.pyroscope/config.ini' not found, use the command 'pyroadmin --create-config' to create it!
WARNING:pyrocore.util.load_config.ConfigLoader:Configuration file '/root/.pyroscope/config.py' not found!
So apparently, somewhere there are still ~/ references, and they are executed as root...
EDIT: I'm receiving my new server tomorrow, and I'll set up a fresh instance there, now that I know where to look to diagnose, then we'll see if this if from my tampering or if it's a general issue with the image.
I fired up a new copy using the compose-file I have, and now it seems everything is fine in terms of things trying to run as root, so I'm writing that one of as "something went wrong when I first tried to get this image up and running or when I tried to fix it".
However! In the new install, I got an error when trying to run the QueueManager manually (/config/bin/pyrotorque --fg -v), saying that the package requests
was missing. So a quick pip install requests
and it was working!
Well, by "working", I meant "not throwing errors all over the place". It was still not starting jobs, so I replaced the rtorrent.rc pyroscope settings with the config suggested on the official site:
#
# PyroScope SETTINGS
#
# `system.has` polyfill (the "false=" silences the `catch` command, in rTorrent-PS)
catch = {"false=", "method.redirect=system.has,false"}
# Set "pyro.extended" to 1 to activate rTorrent-PS features!
# (the automatic way used here only works with rTorrent-PS builds after 2018-05-30)
method.insert = pyro.extended, const|value, (system.has, rtorrent-ps)
# Set "pyro.bin_dir" to the "bin" directory where you installed the pyrocore tools!
# Make sure you end it with a "/"; if this is left empty, then the shell's path is searched.
method.insert = pyro.bin_dir, string|const, "/config/bin/"
# Remove the ".default" if you want to change something (else your changes
# get over-written on update, when you put them into ``*.default`` files).
import = /config/.pyroscope/rtorrent-pyro.rc.default
# TORQUE: Daemon watchdog schedule
# Must be activated by touching the "~/.pyroscope/run/pyrotorque" file!
# Set the second argument to "-v" or "-q" to change log verbosity.
schedule = pyro_watchdog,30,300,"pyro.watchdog=/config/.pyroscope,-v"
And then it started looking for configs in the /root/.pyroscope folder again. So I sym-linked the /config/.pyroscope folder to /root/.pyroscope to test, and now the container has a functioning torrent-queue, like fully! Only problem is, it seems something is running the queue as root, but I can't verify that atm.