kirk8999
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by kirk8999
-
-
2 hours ago, EC28 said:
I'm getting a lot of rutorrent timeout errors and login issues with my image. I have about 1100 torrents running currently. I know stability is an issue with rutorrent historically. I've even read and attempted some of the fixes on the tuning website: Performance Tuning
I've not been able to find anything that really solves this problem yet. I saw one person recommend the arch-rtorrentvpn image as being more stable. Debating about giving that a go.
Are there any things you guys or anyone has been able to do to manage a high torrent load and still have rutorrent be functional? I'd like to go even high in torrent count, but until it's stable I know it will be an issue. Thanks!
I get many "Request to rTorrent has timed out" errors as well, but at least now that I'm on Toronto PIA nothing seems to actually crash..... I haven't been able to figure out whether I should worry about these errors or not. I'm running around 700 torrents currently and it seems to be OK. Would love to know how to tune to max number of torrents and eliminate errors.
-
On 8/2/2020 at 10:56 AM, dewlite said:
My VPN passport is stamped all over. I wonder if PIA is going to get themselves sorted out. Are there any other providers that have the ability to do Port Forwarding? Curious about their Wireguard implementation once they get it figured out but assume we would need to use a separate container and route everything through it.
If it isnt said enough, thank you for the work you do on all of this.
The Toronto PIA server seems to be working well for me, right now at least. I had problems with a bunch of others.
-
Yet another update..... I had 1500 torrents running, so I deleted 1000 of them. I am still getting various "rTorrent is not responding" errors periodically but so far the container hasn't seized up. So perhaps the issue is just too many torrents. Does anyone know if there is some setting change I can make to allow for more torrents? I've already increased memory and processor allocation to Docker quite a bit.
-
Hi, one more update, before I posted the log when I tried to stop the container and it wouldn't. Here's the log for when the container hangs in the first place. It appears to be related to privoxy possibly
2020-07-19 16:14:45,301 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received
[info] 2 retries left
[info] Retrying in 2 secs...
2020-07-19 16:14:49,314 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received
[info] 1 retries left
[info] Retrying in 2 secs...
2020-07-19 16:14:51,332 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received, exhausted retries
1
2020-07-19 16:14:51,364 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed
2020-07-19 16:15:11,454 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received
[info] 5 retries left
[info] Retrying in 2 secs...
2020-07-19 16:15:21,507 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received
[info] 4 retries left
[info] Retrying in 2 secs...
2020-07-19 16:15:29,528 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received
[info] 3 retries left
[info] Retrying in 2 secs...
2020-07-19 16:15:35,552 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received
[info] 2 retries left
[info] Retrying in 2 secs...
2020-07-19 16:15:39,592 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received
[info] 1 retries left
[info] Retrying in 2 secs...
2020-07-19 16:15:41,605 DEBG 'watchdog-script' stdout output:
[warn] Exit code '6' from curl != 0 or no response body received, exhausted retries
2020-07-19 16:15:41,607 DEBG 'watchdog-script' stdout output:
1
2020-07-19 16:15:41,632 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed
-
Hi, things had been rock solid for some time, but now I am having problems. First, when the container is running I get a lot of "The requst to rTorrent" has timed out errors, even though it appears the torrents are running. Then, after a while things seem to lock up, and when I try to shut down the container it hangs. Here are the last few pages of logs. Unfortunately, the container seems to hang every day so it's not really usable unless I can solve this.
2020-07-18 17:52:16,632 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed
2020-07-18 17:52:50,737 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:52:50 [error] 6379#6379: *162114 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910093&_=1595016892263 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:53:02,124 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:53:02 [error] 6379#6379: *162482 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910098&_=1594948550914 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:53:51,732 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:53:51 [error] 6379#6379: *162501 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910093&_=1595016892265 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:54:05,125 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:54:05 [error] 6379#6379: *162508 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910098&_=1594948550917 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:55:05,149 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:55:05 [error] 6379#6379: *162508 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910093&_=1595016892268 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:55:06,412 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:55:06 [error] 6379#6379: *162526 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910098&_=1594948550919 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:55:15,068 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:55:15 [error] 6379#6379: *162530 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "POST /plugins/rss/action.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:55:21,940 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:55:21 [error] 6378#6378: *162534 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/diskspace/action.php?_=1594948550920 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:55:37,076 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:55:37 [error] 6379#6379: *162536 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "POST /plugins/rss/action.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:56:22,010 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:56:22 [error] 6378#6378: *162534 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910093&_=1595016892271 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:56:34,078 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:56:34 [error] 6379#6379: *162546 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910098&_=1594948550921 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:56:37,089 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:56:37 [error] 6379#6379: *162550 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "POST /plugins/rss/action.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:56:38,058 DEBG 'rutorrent-script' stderr output:
2020/07/18 17:56:38 [error] 6379#6379: *162536 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/diskspace/action.php?_=1594948550922 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"
2020-07-18 17:57:00,137 WARN received SIGTERM indicating exit request
2020-07-18 17:57:00,150 DEBG killing watchdog-script (pid 199) with signal SIGTERM
2020-07-18 17:57:00,152 INFO waiting for logrotate-script, rutorrent-script, start-script, watchdog-script to die
2020-07-18 17:57:01,163 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 140187461548016 for <Subprocess at 140187461546096 with name watchdog-script in state STOPPING> (stdout)>
2020-07-18 17:57:01,165 DEBG fd 30 closed, stopped monitoring <POutputDispatcher at 140187461548064 for <Subprocess at 140187461546096 with name watchdog-script in state STOPPING> (stderr)>
2020-07-18 17:57:01,168 INFO stopped: watchdog-script (terminated by SIGTERM)
2020-07-18 17:57:01,190 DEBG received SIGCHLD indicating a child quit
2020-07-18 17:57:01,203 DEBG killing start-script (pid 197) with signal SIGTERM
2020-07-18 17:57:01,218 DEBG fd 25 closed, stopped monitoring <POutputDispatcher at 140187461547488 for <Subprocess at 140187461488496 with name start-script in state STOPPING> (stderr)>
2020-07-18 17:57:01,225 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 140187461488544 for <Subprocess at 140187461488496 with name start-script in state STOPPING> (stdout)>
2020-07-18 17:57:01,227 INFO stopped: start-script (terminated by SIGTERM)
2020-07-18 17:57:01,229 DEBG received SIGCHLD indicating a child quit
2020-07-18 17:57:01,232 DEBG killing rutorrent-script (pid 196) with signal SIGTERM
2020-07-18 17:57:02,235 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 140187461488352 for <Subprocess at 140187461488304 with name rutorrent-script in state STOPPING> (stdout)>
2020-07-18 17:57:02,236 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 140187461547200 for <Subprocess at 140187461488304 with name rutorrent-script in state STOPPING> (stderr)>
2020-07-18 17:57:02,239 INFO stopped: rutorrent-script (terminated by SIGTERM)
2020-07-18 17:57:02,242 DEBG received SIGCHLD indicating a child quit
2020-07-18 17:57:02,245 DEBG killing logrotate-script (pid 194) with signal SIGTERM
2020-07-18 17:57:02,252 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140187461794448 for <Subprocess at 140187461795024 with name logrotate-script in state STOPPING> (stdout)>
2020-07-18 17:57:02,254 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140187461546288 for <Subprocess at 140187461795024 with name logrotate-script in state STOPPING> (stderr)>
2020-07-18 17:57:02,256 INFO stopped: logrotate-script (terminated by SIGTERM)
2020-07-18 17:57:02,258 DEBG received SIGCHLD indicating a child quit
-
Hi, another dumb question. I was able to get Privoxy working in the container and am using Windows. When I set a proxy to localhost:8118 at the Windows level, the proxy works.
But if I go to a web site like (with proxy off): http://google.com:8118 I get a browser error. Isn't this supposed to work? Thanks!
-
Thanks, I should have seen that in the FAQ!
-
Hi, I am new to Docker. I set up binhex/arch-rtorrentvpn successfully, but for some reason when I try to change the port number for torrents, it stays stuck at default 6118 (which for some reason is banned by my tracker) even though the port I selected is listed in ruTorrent settings. Then when I restart the container, the port listed in ruTorrent settings also goes back to default. Is this a bug or am I doing something wrong? Thanks!
[Support] binhex - rTorrentVPN
in Docker Containers
Posted
Ditto - I can't get this container to work with PIA at all any more. Is anyone else having more luck? I'm a little confused on the old API/new API, net gen server etc - I just know it's not working. Will there be an update so that the container works with PIA? If not anyone know of alternatives?
thanks!