[Support] binhex - rTorrentVPN


Recommended Posts

19 minutes ago, bonzog said:

 

I am currently having a very similar issue. The container works on first run after barebones install & basic VPN config, but any subsequent restart of the container or the Unraid host causes the startup loop that you posted. 

 

/mnt/user/Media is mapped to /data in the container, permissions look OK, I'm a bit stuck now and would appreciate any advice. Thanks.

Take a look at the log files in "\appdata\binhex-rtorrentvpn\rtorrent\logs". It should be more specific about the error in there.

Link to comment
2 hours ago, ReDew said:

Take a look at the log files in "\appdata\binhex-rtorrentvpn\rtorrent\logs". It should be more specific about the error in there.

 

Interesting - the log file hasn't been updated since the time I shut down the running container. The timestamp is consistent with the when I rebooted my Unraid host to install a new NV driver and the last entries are: 

 

1644174856 N worker_rtorrent: Shutting down thread.
1644174856 N rtorrent main: Shutting down thread.
1644174856 N rtorrent disk: Shutting down thread.

 

Assuming this might be a permissions issue, I have created a new system user, changed the PUID & PGID of the binhex-rtorrent container, and deleted perms.txt before starting the container again. The user:group on all files has changed successfully, but the startup failure cycle still persists. :( 

Link to comment

I'm having some trouble running this container unprivileged with openvpn.

I've set it up with `net_admin` privileges, but when I start the container I see that there is an error at one point:

2022-02-09 18:05:45,625 DEBG 'start-script' stdout output: iptables v1.8.4 (legacy): can't initialize iptables table `filter': Permission denied (you must be root) Perhaps iptables or your kernel needs to be upgraded.

 

The iptables kernel modules loaded on my host are:

❯ sudo lsmod | rg iptable
iptable_nat            16384  0
iptable_filter         16384  0
iptable_mangle         16384  0
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
nf_nat                 45056  4 ipt_MASQUERADE,xt_nat,nft_chain_nat,iptable_nat

 

If I restart the container in privileged mode, then everything starts up fully and works.

I tried this with tags v3.10-01 and v0.9.8-01, it's the same on both. Does the container always need to run as root?

Reading the docs it seems to me that root should only be required when using WireGuard?

 

Any ideas as to why this wouldn't run unprivileged welcome.

Edited by 7thSon
Link to comment
  • 3 weeks later...

I am having trouble connecting to webui using your unraid image for rtorrentvpn. I have paths set, proper LAN and used both openvpn and wireguard. The container starts, but the page won't load no matter what I do.

 

When using openvpn I've made sure to add in the openvpn files received from private internet access.

Link to comment
On 1/18/2022 at 10:10 PM, luizmont said:

I use this container for some time now and it always worked without any problems.

However, lately some torrents are giving me trouble, because I can't download them.

 

When I add the torrent (manually or via RSS) its status is "Queue" and I can't force recheck or tell it to start.

However, if I add another torrent file (a new one, that I never downloaded before), it gets added and start downloading the files.

Usually this happens with some (but not all) files that gets loaded using RSS, specially if the previous release got deleted.

 

When I try to change the location of file (clicking "Save to..."), I get the following error

XMLRPC Error: Duplicate filename found. [getsavepath]

 

I tried to google this error, but got no results...

 

Any help is appreciated, thanks in advance.

 

I'm getting this same exact error for the same exact reason with no luck on figuring out why it's happening. Please let me know if you figured it out.

Edit: I also get the error XMLRPC Error: Duplicate filename found. [removewithdata] when trying to remove it. This only occurs on the one torrent. All others I've added, preexisting files or not, didn't have this issue.

Edited by optibot
Link to comment
On 12/30/2021 at 4:37 PM, Linguafoeda said:

I'm having trouble with something relatively simple that I'd like to incorporate into rtorrent/RuTorrent. I'm running Binhex's rutorrent container on Unraid Docker, and I want the ability to have a change in label / category of the torrent move all the associate files into the related subfolder within my broader Downloads share. I want this to work whether the file is actively seeding, downloading, finished etc. I know qBt does this so I would think rTorrent through a script can accomplish the same task.

I'm relatively new to scripting on rutorrent / docker / unraid so any beginner tips to figure this out would be very much appreciated :)

 

bump - anyone know how to accomplish this?

Link to comment
  • 2 weeks later...

I've been using this image for over 3 months without any problems but today the container just stopped with 135 exit code. Logs:

2022-03-23 22:17:59.808371 [info] Host is running unRAID
2022-03-23 22:17:59.840674 [info] System information Linux 51c011541462 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2022-03-23 22:17:59.883313 [info] OS_ARCH defined as 'x86-64'
2022-03-23 22:17:59.940215 [info] PUID defined as '99'
2022-03-23 22:17:59.981057 [info] PGID defined as '100'
2022-03-23 22:18:00.159134 [info] UMASK defined as '000'
2022-03-23 22:18:00.198197 [info] Permissions already set for '/config'
2022-03-23 22:18:00.244633 [info] Deleting files in /tmp (non recursive)...
2022-03-23 22:18:00.282188 [info] VPN_ENABLED defined as 'yes'
2022-03-23 22:18:00.311848 [info] VPN_CLIENT defined as 'openvpn'
2022-03-23 22:18:00.339490 [info] VPN_PROV defined as 'custom'
2022-03-23 22:18:00.393104 [info] OpenVPN config file (ovpn extension) is located at ----
2022-03-23 22:18:00.459289 [info] VPN remote server(s) defined as '----'
2022-03-23 22:18:00.486324 [info] VPN remote port(s) defined as '443,'
2022-03-23 22:18:00.512464 [info] VPN remote protcol(s) defined as 'tcp-client,'
2022-03-23 22:18:00.539455 [info] VPN_DEVICE_TYPE defined as 'tun0'
2022-03-23 22:18:00.570833 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2022-03-23 22:18:00.599547 [info] LAN_NETWORK defined as '192.168.0.0/24'
2022-03-23 22:18:00.631824 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
2022-03-23 22:18:00.662492 [info] VPN_USER defined as '----'
2022-03-23 22:18:00.693711 [info] VPN_PASS defined as '----'
2022-03-23 22:18:00.726052 [info] ENABLE_PRIVOXY defined as 'no'
2022-03-23 22:18:00.757326 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2022-03-23 22:18:00.786478 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2022-03-23 22:18:00.819120 [info] ENABLE_AUTODL_IRSSI defined as 'no'
2022-03-23 22:18:00.858633 [info] ENABLE_RPC2 defined as 'yes'
2022-03-23 22:18:00.887232 [info] ENABLE_RPC2_AUTH defined as 'yes'
2022-03-23 22:18:00.915570 [info] RPC2_USER defined as 'admin'
2022-03-23 22:18:00.971581 [warn] RPC2_PASS not defined (via -e RPC2_PASS), using randomised password (password stored in '/config/nginx/security/rpc2_pass')
2022-03-23 22:18:01.011645 [info] ENABLE_WEBUI_AUTH defined as 'no'
2022-03-23 22:18:01.053345 [info] Starting Supervisor...

 

I didn't change anything in the configuration, vpn account is still active. Any idea how to fix it?

Link to comment

Trying to use the same container to have multiple rtorrent instances but only one with an active VPN, setting network to none and using --net=container:rutorrent under extra parameters.

 

I've tried changing every necessary port but I can't figure out how to change port 7777 in the configurations. I keep getting this error in the logs:

 

[ERROR] unable to bind listening socket for address '127.0.0.1:7777': Address already in use (98)

 

Any ideas on how to get around this? This seems to be the best optimized rtorrent container for unraid and I'd really like to be able to use multiple-instances, given that the web-gui crashes around 10k torrents.

Link to comment
  • 3 weeks later...

I have started getting the following: 

 

 

2022-04-16 17:20:43,347 DEBG 'rutorrent-script' stderr output:

16 17:20:43 [error] 701#701: *2536 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:21:41,496 DEBG 'rutorrent-script' stderr output:

16 17:21:41 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:21:43,369 DEBG 'rutorrent-script' stderr output:

16 17:21:43 [error] 700#700: *2552 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:22:41,547 DEBG 'rutorrent-script' stderr output:

16 17:22:41 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:23:13,317 DEBG 'rutorrent-script' stderr output:

16 17:23:13 [error] 700#700: *2561 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:24:11,544 DEBG 'rutorrent-script' stderr output:

16 17:24:11 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:24:13,336 DEBG 'rutorrent-script' stderr output:

16 17:24:13 [error] 700#700: *2564 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:25:11,570 DEBG 'rutorrent-script' stderr output:

16 17:25:11 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:25:43,332 DEBG 'rutorrent-script' stderr output:

16 17:25:43 [error] 700#700: *2568 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:26:41,582 DEBG 'rutorrent-script' stderr output:

16 17:26:41 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:26:43,344 DEBG 'rutorrent-script' stderr output:

16 17:26:43 [error] 700#700: *2571 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:27:41,623 DEBG 'rutorrent-script' stderr output:

16 17:27:41 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:28:13,378 DEBG 'rutorrent-script' stderr output:

16 17:28:13 [error] 700#700: *2575 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:29:13,407 DEBG 'rutorrent-script' stderr output:

16 17:29:13 [error] 700#700: *2577 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:42:41,860 DEBG 'rutorrent-script' stderr output:

16 17:42:41 [error] 700#700: *2579 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:43:41,891 DEBG 'rutorrent-script' stderr output:

16 17:43:41 [error] 700#700: *2579 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:44:13,609 DEBG 'rutorrent-script' stderr output:

16 17:44:13 [error] 700#700: *2583 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 17:45:13,648 DEBG 'rutorrent-script' stderr output:

16 17:45:13 [error] 700#700: *2585 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 18:13:42,558 DEBG 'rutorrent-script' stderr output:

16 18:13:42 [error] 700#700: *2588 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 18:14:42,586 DEBG 'rutorrent-script' stderr output:

16 18:14:42 [error] 700#700: *2588 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 18:15:14,112 DEBG 'rutorrent-script' stderr output:

16 18:15:14 [error] 701#701: *2592 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 18:16:14,152 DEBG 'rutorrent-script' stderr output:

16 18:16:14 [error] 700#700: *2594 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 19:14:43,830 DEBG 'rutorrent-script' stderr output:

16 19:14:43 [error] 700#700: *2599 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 19:15:43,861 DEBG 'rutorrent-script' stderr output:

16 19:15:43 [error] 700#700: *2599 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 19:16:14,969 DEBG 'rutorrent-script' stderr output:

16 19:16:14 [error] 700#700: *2603 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"


2022-04-16 19:17:15,002 DEBG 'rutorrent-script' stderr output:

16 19:17:15 [error] 700#700: *2605 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080"

 

 

I have tried removing docker container and install new one, only keeping the session folder. This has happended twice in two days. 

Edited by kakmoster
Link to comment

I have suddenly started getting the following infinite loop in my log, ruTorrent attempting to start over and over again.  See the attached for a full log

2022-04-18 20:32:26,728 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2022-04-18 20:32:26,732 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2022-04-18 20:32:26,734 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2022-04-18 20:32:26,735 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2022-04-18 20:32:26,764 DEBG 'watchdog-script' stdout output:
Script done.

2022-04-18 20:32:27,778 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...

2022-04-18 20:32:27,786 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening on port 5000

2022-04-18 20:32:27,786 DEBG 'watchdog-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

2022-04-18 20:32:27,791 DEBG 'watchdog-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...

2022-04-18 20:32:27,797 DEBG 'watchdog-script' stdout output:
[info] nginx running
[info] Initialising ruTorrent plugins...

2022-04-18 20:32:33,164 DEBG 'watchdog-script' stdout output:
[info] ruTorrent plugins initialised

2022-04-18 20:33:03,317 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

 

The weird thing is that I don't think the docker image even updated recently

Anyone see something similar or have any leads for me?

binhex_utorrentvpn.log

Link to comment

rTorrent wasn't working since yesterday.

Im getting the particular error from the log.

 

2022-04-19 21:19:48,542 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2022-04-19 21:19:48,553 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2022-04-19 21:19:48,556 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2022-04-19 21:19:48,557 DEBG 'start-script' stderr output:
Line unrecognized: `PublicKey='
Configuration parsing error

2022-04-19 21:19:48,560 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2022-04-19 21:19:48,611 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

2022-04-19 21:20:18,616 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2022-04-19 21:20:18,627 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2022-04-19 21:20:18,635 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2022-04-19 21:20:18,638 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2022-04-19 21:20:18,639 DEBG 'start-script' stderr output:
Line unrecognized: `PublicKey='
Configuration parsing error

2022-04-19 21:20:18,641 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2022-04-19 21:20:18,675 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

Link to comment
23 minutes ago, feins said:

Line unrecognized: `PublicKey='
Configuration parsing error

sounds like a screwed up wireguard config file, check the file /config/wireguard/wg0.conf i suspect you will find the PublicKey value is empty and thus invalid, it should look something like this (fake data):-

 

PublicKey = fghgfh/vnL0vcSADFASDFSD343423DFGEZGarVm6gB0=

 

Link to comment
sounds like a screwed up wireguard config file, check the file /config/wireguard/wg0.conf i suspect you will find the PublicKey value is empty and thus invalid, it should look something like this (fake data):-
 
PublicKey = fghgfh/vnL0vcSADFASDFSD343423DFGEZGarVm6gB0=

 


Hi Binhex,

Thanks for your reply.
If that’s the case how should I do?
Can I uninstall and reinstall rTorrentVPN resolve this issue?


Sent from my iPhone using Tapatalk
Link to comment
9 minutes ago, feins said:


Hi Binhex,

Thanks for your reply.
If that’s the case how should I do?
Can I uninstall and reinstall rTorrentVPN resolve this issue?


Sent from my iPhone using Tapatalk

if you are using vpn provider PIA then simply delete that file and restart the container, if you are using another provider then please re-download the wireguard config file from the vpn providers website.

Link to comment
16 hours ago, veri745 said:

I have suddenly started getting the following infinite loop in my log, ruTorrent attempting to start over and over again.  See the attached for a full log

...

The weird thing is that I don't think the docker image even updated recently

Anyone see something similar or have any leads for me?

binhex_utorrentvpn.log 36.3 kB · 2 downloads

I've tried restarting, rebooting, reinstalling the docker image.  I'm really at a loss here

 

It looks like only some of the plugins are loading properly

rtorrent_plugins.thumb.png.714071aac104645393dc5b73f2b717fc.png

Link to comment
On 1/4/2022 at 11:27 AM, ReDew said:

I'm not sure what's going wrong with the initialization, but it is not starting and keeps looping.

Did you figure this out out?  I am seeing the same issue suddenly, and I have not changed my config in months if not years

Edited by veri745
Link to comment
1 hour ago, veri745 said:

Did you figure this out out?  I am seeing the same issue suddenly, and I have not changed my config in months if not years

My symptoms were quite similar to yours. Working fine, no config changes, just stopped working one night. Never did find a fix and moved to binhex-qbittorrentvpn instead, which is working fine.

Edited by bonzog
Link to comment
4 hours ago, veri745 said:

Did you figure this out out?  I am seeing the same issue suddenly, and I have not changed my config in months if not years

My issue was changing the name of the /data directory in the during the install. You should see if you can find any clues in the logs file.

Link to comment
16 hours ago, binhex said:

if you are using vpn provider PIA then simply delete that file and restart the container, if you are using another provider then please re-download the wireguard config file from the vpn providers website.

Hi Binhex,

 

Thanks for the guide.

Ive deleted the wg0.conf files as requested and it work as usual after the docker restart.

Thanks for your time and respond.

  • Like 1
Link to comment
  • 2 weeks later...

What is the max amount of torrents that ruTorrent is able to handle before it becomes unstable and will not load? I have heard of increasing memory and the time out length, but I am not exactly where where to find these settings and what they are called. I have 2000 torrents currently and I noticed it is starting to slow down a bit. 

Link to comment
1 hour ago, esto0pi said:

What is the max amount of torrents that ruTorrent is able to handle before it becomes unstable and will not load? I have heard of increasing memory and the time out length, but I am not exactly where where to find these settings and what they are called. I have 2000 torrents currently and I noticed it is starting to slow down a bit. 

2k is about right without any tweaks. rtorrent by itself (no web ui) can be pushed way further; check some of my previous posts for some hints on how to do it. Since this container has screen, rtorrent-ps and pyrocore, if you don't mind the command line you can certainly make it work.

PS: rtorrent-ps and PyroScope both looks unmaintained and @binhex has already told the community that he may move the containers back to regular rtorrent. To be fair rtorrent is also usable by itself, but PyroScope certainly makes it nicer.

PS II: rtorrent itself is also stuck in version 0.9.8 since 2019. Unfortunately a lot of torrent software is dying.

Link to comment
Posted (edited)

In the last few days I've had a problem with my speeds coming down substantially. I usually get around 25 MiB/s in total, but now I usually get around 6-8 MiB/s. What is odd is that if I restart the container, I get back to full speed initially, but then it comes down again.

 

I use PIA (and Wireguard) and have tried different endpoints, with the same result. What I have noticed in the log files is that I get this line repeated every 15 minutes.

2022-05-05 20:20:48,836 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port 'nnnnn'

 

I don't recall seeing this happening before, and wonder if this has anything to do with the slowing down. Or is this a PIA issue or something else?

 

Edit:

So after analysing what I could, it seems that the speed differences are probably a result of the vagaries of torrents. When I look at longer periods of total traffic, it's hard to discern any real pattern. So looks like nothing to worry about, although I'm still not sure whether the repeated log entry is expected behaviour. 

Edited by sonofdbn
Update
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.