search

binhex / arch-rtorrentvpn

Docker build script for Arch Linux base with ruTorrent, rTorrent, autodl-irssi, Privoxy and OpenVPN
GNU General Public License v3.0
238 stars 35 forks source link

rTorrent does not start #167

Open xipdk opened 3 years ago

xipdk commented 3 years ago

It seems to go into a loop, after i while or a few manual restarts it will work. Running it on my Synology NAS with Docker. From the Log:

2020-11-02 10:29:48,167 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '216.58.207.228'

2020-11-02 10:29:48,169 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place...

2020-11-02 10:29:48,185 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place

2020-11-02 10:29:48,193 DEBG 'watchdog-script' stdout output: [info] rTorrent not running

2020-11-02 10:29:48,194 DEBG 'watchdog-script' stdout output: [info] Removing any rTorrent session lock files left over from the previous run...

2020-11-02 10:29:48,196 DEBG 'watchdog-script' stdout output: [info] Attempting to start rTorrent...

2020-11-02 10:29:48,198 DEBG 'watchdog-script' stdout output: Script started, output log file is '/home/nobody/typescript'.

2020-11-02 10:29:48,236 DEBG 'watchdog-script' stdout output: Script done.

2020-11-02 10:29:48,245 DEBG 'watchdog-script' stdout output: [debug] Waiting for rTorrent process to start [debug] Re-check in 1 secs... [debug] 11 retries left

2020-11-02 10:29:49,255 DEBG 'watchdog-script' stdout output: [info] rTorrent process started [info] Waiting for rTorrent process to start listening on port 5000...

2020-11-02 10:29:49,263 DEBG 'watchdog-script' stdout output: [info] rTorrent process listening on port 5000

2020-11-02 10:29:49,263 DEBG 'watchdog-script' stdout output: [info] Initialising ruTorrent plugins (checking rTorrent is running)...

2020-11-02 10:29:49,272 DEBG 'watchdog-script' stdout output: [info] rTorrent running [info] Initialising ruTorrent plugins (checking nginx is running)...

2020-11-02 10:29:49,281 DEBG 'watchdog-script' stdout output: [info] nginx running [info] Initialising ruTorrent plugins...

2020-11-02 10:29:55,099 DEBG 'watchdog-script' stdout output: [info] ruTorrent plugins initialised [debug] VPN IP is 10.8.3.2

2020-11-02 10:29:55,100 DEBG 'watchdog-script' stdout output: [debug] rTorrent IP is 10.8.3.2

2020-11-02 10:30:25,102 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address...

2020-11-02 10:30:26,099 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.20.36'

2020-11-02 10:30:26,101 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place...

2020-11-02 10:30:26,117 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place

2020-11-02 10:30:26,126 DEBG 'watchdog-script' stdout output: [info] rTorrent not running

2020-11-02 10:30:26,127 DEBG 'watchdog-script' stdout output: [info] Removing any rTorrent session lock files left over from the previous run...

2020-11-02 10:30:26,129 DEBG 'watchdog-script' stdout output: [info] Attempting to start rTorrent...

2020-11-02 10:30:26,131 DEBG 'watchdog-script' stdout output: Script started, output log file is '/home/nobody/typescript'.

2020-11-02 10:30:26,168 DEBG 'watchdog-script' stdout output: Script done.

2020-11-02 10:30:26,177 DEBG 'watchdog-script' stdout output: [debug] Waiting for rTorrent process to start [debug] Re-check in 1 secs... [debug] 11 retries left

2020-11-02 10:30:27,187 DEBG 'watchdog-script' stdout output: [info] rTorrent process started [info] Waiting for rTorrent process to start listening on port 5000...

2020-11-02 10:30:27,196 DEBG 'watchdog-script' stdout output: [info] rTorrent process listening on port 5000

2020-11-02 10:30:27,196 DEBG 'watchdog-script' stdout output: [info] Initialising ruTorrent plugins (checking rTorrent is running)...

2020-11-02 10:30:27,205 DEBG 'watchdog-script' stdout output: [info] rTorrent running [info] Initialising ruTorrent plugins (checking nginx is running)...

2020-11-02 10:30:27,214 DEBG 'watchdog-script' stdout output: [info] nginx running [info] Initialising ruTorrent plugins...

2020-11-02 10:30:33,127 DEBG 'watchdog-script' stdout output: [info] ruTorrent plugins initialised

2020-11-02 10:30:33,127 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.8.3.2 [debug] rTorrent IP is 10.8.3.2

xipdk commented 3 years ago

If i remove the .rtorrent and resume files from the session folder it works again.

fboterblom commented 2 years ago

Hi, I have the same problem, where can i find the .rtorrent?

fboterblom commented 2 years ago

hmm changing PGID and PUID to 0, seems to solve it, but security wise maybe not the best solution.

fboterblom commented 2 years ago

throwing away the config directory from the docker container solves this issue

doubleopinter commented 2 years ago

I ran into this issue as well and I found that changing the PGID and PUID did the trick. What is the impact of doing that though? Will that mess up downloaded file permissions? I'm willing and able to test and provide feedback. I'm running this on a standalone docker in Debian.

napei commented 1 year ago

@binhex I am still having this issue presently, even on a brand new container on Unraid's docker running with WireGuard.

Setting PUID=0,PGID=0 is the only way I have been able to have rTorrent start, which would be fine however the downloaded files it makes are not able to be mutated by Sonarr/Radarr as they are created owned by root:root.

Setting PUID=99,PGID=100 does not allow rTorrent to start and it just sits there forever attempting to start. I would love to run this container as non-root.

There are some suggestions in #188 to why this is happening.

image