[Support] binhex - rTorrentVPN


Recommended Posts

I am trying to set a custom incoming port. 

 

I stop the docker, open rtorrent.rc and uncomment this line and set my port :

network.port_range.set = 20568

And restart the docker. 

I can open the WebUI but my torrents are gone and any time I click on a button or try to navigate I get the following logs: 

 

[18.11.2018 08:35:00] WebUI started.
[18.11.2018 08:35:01] Bad response from server: (0 [error,getplugins])
[18.11.2018 08:35:05] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined
[18.11.2018 08:35:07] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined
[18.11.2018 08:35:08] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined
[18.11.2018 08:35:08] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined
[18.11.2018 08:35:08] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined

 

I can then comment out the line in rtorrent.rc, restart the docker, and things work like they should (without my custom port obviously) 

 

Please help. :/ 

 

Link to comment
6 hours ago, AaronJAnderson said:

I am trying to set a custom incoming port. 

 

I stop the docker, open rtorrent.rc and uncomment this line and set my port :


network.port_range.set = 20568

And restart the docker. 

I can open the WebUI but my torrents are gone and any time I click on a button or try to navigate I get the following logs: 

 


[18.11.2018 08:35:00] WebUI started.
[18.11.2018 08:35:01] Bad response from server: (0 [error,getplugins])
[18.11.2018 08:35:05] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined
[18.11.2018 08:35:07] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined
[18.11.2018 08:35:08] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined
[18.11.2018 08:35:08] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined
[18.11.2018 08:35:08] JS error: [http://admin:[email protected]:9080/js/stable.js : 1735] Uncaught TypeError: Cannot read property 'scrollTop' of undefined

 

I can then comment out the line in rtorrent.rc, restart the docker, and things work like they should (without my custom port obviously) 

 

Please help. :/ 

 

didnt you see the example shown in the rtorrent.rc?:-

 

# Port range to use for listening.
#
#network.port_range.set = 49160-49160

note the difference.

  • Like 1
Link to comment
On 6/8/2018 at 10:14 PM, wisemanofhyrule said:

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 5256Mf3.png

(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!

 

 

 

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. 

Link to comment
1 hour ago, wisemanofhyrule said:

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. 

if you believe the issue is related to the rtorrent process then your best bet is to raise this as an "issue" on the rtorrent github repo, if you want the problem solved then i would advise you to give as much detail as possible to help the dev:-

 

https://github.com/rakshasa/rtorrent/issues

Link to comment

Hi. I went back to repository: binhex/arch-rtorrentvpn:0.9.7-1-11

 

Because the last version had a problem with the webserver not loading.

 

Today I just noticed a very serious error with this version though.

 

My machine is at 100% CPU AND RAM usage because of this docker container. The ruTorrent WebUI is completely unresponsive.

 

CPU and RAM usage when rTorrent-VPN is running:

 

f0ESR8VO.png

 

htop showing that rTorrent-VPN is the culprit:

 

sijRAGuF.png

 

Here's a shot of the docker window which doesn't show high CPU usage but it shows high RAM usage:

 

RLUu6Q7l.png

 

Here's my CPU and RAM after stopping the rTorrent-VPN container:

 

qARRj30a.png


My question is what am I supposed to do now? This version has been messing up doing this for a couple of days now, and the latest version has a webserver problem.

 

What's the default repo so I can at least try the latest version, is it: binhex/arch-rtorrentvpn:latest ?

Edited by plantsandbinary
Link to comment
5 hours ago, plantsandbinary said:

Because the last version had a problem with the webserver not loading.

this is the first ive heard of it (maybe i missed your post), im using the latest built image 24/7 with no issues, can you give me more details on this?.

 

5 hours ago, plantsandbinary said:

My machine is at 100% CPU AND RAM usage because of this docker container. The ruTorrent WebUI is completely unresponsive.

ive not experienced this myself, rutorrent is rock solid, rtorrent CAN crash under certain circumstances but i auto restart if it does, but ive not seen it consume all cpu resources, and its def never been a memory hog, being extremely light on resources if anything, not sure what i can say at this point, a restart of the container, or better still a reboot of your host perhaps.

Edited by binhex
Link to comment

@binhex you literally replied about the problem. It's from the last page of this thread (page 50)

 

Quote

sorry guys this caught me at a bad time, automated update picked up a new build with a library that wasn't included in the base, so to prevent this happening i am updating to target live repo from now on, means larger images but should prevent breakage in the future.

 

Everyone had this issue with a previous update. I just left that repo active to solve the problem the update had. Well this issue was what happened after reverting to use an older repo/version than the one that was bugged.

 

Anyway updating to the latest version fixed the issue entirely.

 

Though I seem to be getting a lot of these errors in the log now with the latest version:

 

2018/11/30 02:24:46 [error] 1984#1984: *15 FastCGI sent in stderr: "PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 163
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 163
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 166
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 166
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 163
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 163
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 166
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 166
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 163
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 163
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/share/webapps/rutorrent/plugins/trafic/stat.php on line 166
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr
2018/11/30 02:24:46 [error] 1984#1984: *15 upstream sent too big header while reading response header from upstream, client: 192.168.1.108, server: localhost, request: "POST /plugins/trafic/action.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.50:9443", referrer: "https://192.168.1.50:9443/"

 

Edited by plantsandbinary
Link to comment
10 hours ago, plantsandbinary said:

Though I seem to be getting a lot of these errors in the log now with the latest version:

googling around i think the issue is php 7.2 incompatibility with the traffic stats plugin, see here for people with similar issues (different app):-

 

https://github.com/Automattic/jetpack/issues/8420

 

and another:-

 

https://github.com/mpdf/mpdf/issues/562

 

so options are i can attempt to roll back to php 7.1 which should fix it (this can be tough on a rolling distro but maybe possible), or a better outcome is to contact the plugin author and get them to update their code to be compatible with php 7.2,

 

my guess is that 'count' is equal to null in the code for that plugin, and this is no longer permitted in php 7.2

Link to comment
On 8/4/2018 at 7:01 PM, bumperjeep said:

So I removed the rtorrent.rc file, the container and started the container again, and it still doesn't come back up. Here is the full logs. 

 

 


Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2018-08-04 18:56:11.319555 [info] System information Linux 8dd3c06831be 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 GNU/Linux
2018-08-04 18:56:11.361603 [info] PUID defined as '1000'
2018-08-04 18:56:11.451168 [info] PGID defined as '1000'
2018-08-04 18:56:11.502370 [info] UMASK defined as '000'
2018-08-04 18:56:11.542956 [info] Permissions already set for volume mappings
2018-08-04 18:56:11.588439 [info] VPN_ENABLED defined as 'yes'
2018-08-04 18:56:11.635162 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Toronto.ovpn
dos2unix: converting file /config/openvpn/CA Toronto.ovpn to Unix format...
2018-08-04 18:56:11.694563 [info] VPN remote line defined as 'remote ca-toronto.privateinternetaccess.com 1198'
2018-08-04 18:56:11.735606 [info] VPN_REMOTE defined as 'ca-toronto.privateinternetaccess.com'
2018-08-04 18:56:11.777282 [info] VPN_PORT defined as '1198'
2018-08-04 18:56:11.822301 [info] VPN_PROTOCOL defined as 'udp'
2018-08-04 18:56:11.863818 [info] VPN_DEVICE_TYPE defined as 'tun0'
2018-08-04 18:56:11.905185 [info] VPN_PROV defined as 'pia'
2018-08-04 18:56:11.946579 [info] LAN_NETWORK defined as '10.10.10.0/24'
2018-08-04 18:56:11.987852 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2018-08-04 18:56:12.111140 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2018-08-04 18:56:12.151911 [info] STRICT_PORT_FORWARD defined as 'yes'
2018-08-04 18:56:12.192809 [info] ENABLE_PRIVOXY defined as 'yes'
2018-08-04 18:56:12.233986 [info] ENABLE_FLOOD defined as 'no'
2018-08-04 18:56:12.275712 [info] ENABLE_AUTODL_IRSSI defined as 'yes'
2018-08-04 18:56:29.726221 [info] Starting Supervisor...
2018-08-04 18:56:29,929 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
2018-08-04 18:56:29,929 INFO Set uid to user 0 succeeded
2018-08-04 18:56:29,933 INFO supervisord started with pid 8
2018-08-04 18:56:30,935 INFO spawned: 'start-script' with pid 153
2018-08-04 18:56:30,937 INFO spawned: 'rutorrent-script' with pid 154
2018-08-04 18:56:30,939 INFO spawned: 'flood-script' with pid 155
2018-08-04 18:56:30,941 INFO spawned: 'irssi-script' with pid 156
2018-08-04 18:56:30,943 INFO spawned: 'rtorrent-script' with pid 157
2018-08-04 18:56:30,945 INFO spawned: 'privoxy-script' with pid 159
2018-08-04 18:56:30,946 INFO reaped unknown pid 9
2018-08-04 18:56:30,947 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2018-08-04 18:56:30,947 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-08-04 18:56:30,947 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-08-04 18:56:30,947 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-08-04 18:56:30,947 INFO success: irssi-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-08-04 18:56:30,947 INFO success: rtorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-08-04 18:56:30,947 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-08-04 18:56:30,957 DEBG 'flood-script' stdout output:
[info] Flood not enabled, skipping starting Flood Web UI

2018-08-04 18:56:30,958 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 139685100496800 for <Subprocess at 139685100516776 with name flood-script in state RUNNING> (stdout)>
2018-08-04 18:56:30,958 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 139685100497016 for <Subprocess at 139685100516776 with name flood-script in state RUNNING> (stderr)>
2018-08-04 18:56:30,958 INFO exited: flood-script (exit status 0; expected)
2018-08-04 18:56:30,958 DEBG received SIGCLD indicating a child quit
2018-08-04 18:56:30,970 DEBG 'rtorrent-script' stdout output:
[info] rTorrent config file doesnt exist, copying default to /config/rtorrent/config/...

2018-08-04 18:56:30,999 DEBG 'rtorrent-script' stderr output:
dos2unix: converting file /config/rtorrent/config/rtorrent.rc to Unix format...

2018-08-04 18:56:31,001 DEBG 'rtorrent-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2018-08-04 18:56:31,036 DEBG 'start-script' stdout output:
[info] Default route for container is 172.19.0.1

2018-08-04 18:56:31,041 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2018-08-04 18:56:31,046 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2018-08-04 18:56:31,085 DEBG 'start-script' stdout output:
[info] Attempting to load tun kernel module...

2018-08-04 18:56:31,089 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/4.4.0-131-generic

2018-08-04 18:56:31,090 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2018-08-04 18:56:31,091 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

2018-08-04 18:56:31,091 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2018-08-04 18:56:31,106 DEBG 'start-script' stdout output:
[info] Adding 10.10.10.0/24 as route via docker eth0

2018-08-04 18:56:31,108 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2018-08-04 18:56:31,110 DEBG 'start-script' stdout output:
default via 172.19.0.1 dev eth0
10.10.10.0/24 via 172.19.0.1 dev eth0
172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.0.2
--------------------

2018-08-04 18:56:31,120 DEBG 'start-script' stdout output:
iptable_mangle         16384  0
ip_tables              24576  3 iptable_filter,iptable_mangle,iptable_nat
x_tables               36864  21 xt_DSCP,xt_dscp,xt_mark,xt_hl,xt_helper,xt_length,ip_tables,xt_tcpmss,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_nat,iptable_filter,xt_TCPMSS,ipt_REJECT,xt_REDIRECT,iptable_mangle,xt_addrtype

2018-08-04 18:56:31,121 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2018-08-04 18:56:31,157 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.19.0.0/16

2018-08-04 18:56:31,255 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2018-08-04 18:56:31,258 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.19.0.0/16 -d 172.19.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A INPUT -s 10.10.10.0/24 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT
-A INPUT -s 10.10.10.0/24 -d 172.19.0.0/16 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.19.0.0/16 -d 172.19.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A OUTPUT -d 10.10.10.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT
-A OUTPUT -s 172.19.0.0/16 -d 10.10.10.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2018-08-04 18:56:31,258 DEBG 'start-script' stdout output:
--------------------

2018-08-04 18:56:31,259 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2018-08-04 18:56:31,268 DEBG 'start-script' stdout output:
Sat Aug  4 18:56:31 2018 WARNING: file 'credentials.conf' is group or others accessible
Sat Aug  4 18:56:31 2018 OpenVPN 2.4.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar  1 2018
Sat Aug  4 18:56:31 2018 library versions: OpenSSL 1.1.0g  2 Nov 2017, LZO 2.10

2018-08-04 18:56:31,271 DEBG 'start-script' stdout output:
[info] OpenVPN started
Sat Aug  4 18:56:31 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sat Aug  4 18:56:31 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.82:1198
Sat Aug  4 18:56:31 2018 UDP link local: (not bound)
Sat Aug  4 18:56:31 2018 UDP link remote: [AF_INET]172.98.67.82:1198

2018-08-04 18:56:31,384 DEBG 'start-script' stdout output:
Sat Aug  4 18:56:31 2018 [74e9e038cc1ee5f11e97abf6aba60f3a] Peer Connection Initiated with [AF_INET]zzz

2018-08-04 18:56:32,590 DEBG 'start-script' stdout output:
Sat Aug  4 18:56:32 2018 auth-token received, disabling auth-nocache for the authentication token

2018-08-04 18:56:32,590 DEBG 'start-script' stdout output:
Sat Aug  4 18:56:32 2018 TUN/TAP device tun0 opened
Sat Aug  4 18:56:32 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sat Aug  4 18:56:32 2018 /usr/bin/ip link set dev tun0 up mtu 1500

2018-08-04 18:56:32,593 DEBG 'start-script' stdout output:
Sat Aug  4 18:56:32 2018 /usr/bin/ip addr add dev tun0 local 10.66.10.6 peer 10.66.10.5

2018-08-04 18:56:32,594 DEBG 'start-script' stdout output:
Sat Aug  4 18:56:32 2018 /root/openvpnup.sh tun0 1500 1558 10.66.10.6 10.66.10.5 init

2018-08-04 18:56:32,609 DEBG 'start-script' stdout output:
Sat Aug  4 18:56:32 2018 Initialization Sequence Completed

2018-08-04 18:56:32,633 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...

2018-08-04 18:56:32,642 DEBG 'rtorrent-script' stdout output:
[info] rTorrent not running
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.66.10.6 different, marking for reconfigure

2018-08-04 18:56:32,658 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...

2018-08-04 18:56:32,659 DEBG 'privoxy-script' stderr output:
2018-08-04 18:56:32.659 7f7bd9f8d0c0 Info: Privoxy version 3.0.26
2018-08-04 18:56:32.659 7f7bd9f8d0c0 Info: Program name: /usr/bin/privoxy

2018-08-04 18:56:32,729 DEBG 'irssi-script' stdout output:
Script started, file is /home/nobody/typescript

2018-08-04 18:56:32,738 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=UUID...

2018-08-04 18:56:32,756 DEBG 'irssi-script' stdout output:
Script done, file is /home/nobody/typescript

2018-08-04 18:56:32,763 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 139685100496008 for <Subprocess at 139685100516632 with name irssi-script in state RUNNING> (stdout)>
2018-08-04 18:56:32,763 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 139685100461520 for <Subprocess at 139685100516632 with name irssi-script in state RUNNING> (stderr)>
2018-08-04 18:56:32,763 INFO exited: irssi-script (exit status 0; expected)
2018-08-04 18:56:32,763 DEBG received SIGCLD indicating a child quit
2018-08-04 18:56:32,843 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 

2018-08-04 18:56:33,997 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=UUID, response code 200

2018-08-04 18:56:34,852 DEBG 'rtorrent-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2018-08-04 18:56:34,855 DEBG 'rtorrent-script' stdout output:
[info] Attempting to start rTorrent...

2018-08-04 18:56:34,856 DEBG 'rtorrent-script' stdout output:
Script started, file is /home/nobody/typescript

2018-08-04 18:56:34,879 DEBG 'rtorrent-script' stdout output:
Script done, file is /home/nobody/typescript

2018-08-04 18:56:35,010 DEBG 'rtorrent-script' stdout output:
Script started, file is /home/nobody/typescript

2018-08-04 18:56:35,022 DEBG 'rtorrent-script' stdout output:
duplicate session: irssi_session

2018-08-04 18:56:35,032 DEBG 'rtorrent-script' stdout output:
Script done, file is /home/nobody/typescript

 

I'm getting the modprobe errors again and I completed removed the persistent container data and restarted like you suggested. Am I missing something? I haven't rebooted this machine in about 100 days, could that be the issue

Link to comment

I noticed that in my docker config path there is a file "access.log" which seems to be updated continuously. The docker is working fine, but that access.log file is now over 8 GB in size. Is this normal? I have about 100 torrents, but typically fewer than 20 are active, if that helps.

Link to comment

@binhex Do you have any ideas on the modprobe errors - modprobe: FATAL: Module tun not found in directory /lib/modules/4.4.0-131-generic

 

My container wasn't loading rtorrent last night, had a lot of issues. Didn't see anything obvious in supervisor.log other than the modprobe errors. I also looked at the FAQs in your signature. 

Edited by bumperjeep
Link to comment
On 12/5/2018 at 5:23 AM, sonofdbn said:

Ah, OK! I see it's been happily logging stuff for over a year. Thanks.

Since you've had stable performance over a year I usually set up a cron job to purge old log files.

I'll gzip the logs once a week to the array, and purge any gzips older than a month or two.

 

I haven't done this with Unraid yet, but had done it with my previous server running Arch.

Link to comment

I am getting really slow transfer speed in rtorrent. I cant figure out why. I have tried different VPN endpoints, change rtorrent settings, checked log etc.

If I restart the docker i will shortly get higher speed, and shortly after return to a few kb/s. 

All of these should easily could get 50-100mbit/s

image.png.07ca74162f38e4d7cebaefff3dd4a9ab.png

 

If I start the qbittorrentvpn container, I can easily max out my internet connection. 

Edited by ZataH
Link to comment
56 minutes ago, ZataH said:

I am getting really slow transfer speed in rtorrent. I cant figure out why. I have tried different VPN endpoints, change rtorrent settings, checked log etc.

If I restart the docker i will shortly get higher speed, and shortly after return to a few kb/s. 

All of these should easily could get 50-100mbit/s

image.png.07ca74162f38e4d7cebaefff3dd4a9ab.png

 

If I start the qbittorrentvpn container, I can easily max out my internet connection. 

You referring to upload or download? Private site or public site?

Link to comment

I've always wanted to know. Why the heck is rTorrent so slow at deleting files when I click 'delete data' from the ruTorrent GUI? Seriously Deluge and Transmission just deleted them immediately. rTorrent can take 15-20 MINS! just to delete 1TB. Whilst doing that it also times out again and again and won't respond to any other actions or show me any information about my downloads. Why is it so slow to delete files compared to any other client?

Link to comment

Hello there binhex,

 

FIrst of all I wanna say thank you for putting with the no ends to the suport thread you have here.

I have been a user of this container 2-3 years. 

 

Yet I have had some very problematic issues, rtorrent seems to time out all the time for me now. I have about 1500 torrents inside it. 

The only thing that the log can show me is:

[error] 1862#1862: *1061 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.19.0.7, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "rtorrent:9080"

 

Please, what can I do to solve this?, it is getting to the point where if it continues I am goign to have to find another solution. Also speeds are down quite allot when using the container but i guess that can be because of other factors. 

 

If you have any suggesitons please let me know. 

 

I forgot to add that unpack hasn't been working for the past few days. I can't find any logs of this anywhere. 

Another thing iave not been able to get to work is ratio rules

An example follows below

 

5arbqVq.png

 

Why aren't the torrents removed?, since i can find no logs of this anywhere i am really out of luck.

 

In case you are wondering about my hardware i am running

EXi 6.5, ubuntu 1604 and running docker inside that VM. 

I have 32 cores 64 gigs of ram running on top of enterprise SSDs so the system shouldn't time out after a single delete or 10 for that amtter. 

 

What am i missing here?

Edited by LaserAllan
Forgot a few things.
Link to comment
  • binhex locked this topic
Guest
This topic is now closed to further replies.