Connection to rTorrent not established #126
Comments
|
Paste here container logs please. |
|
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. Brought to you by linuxserver.io
|
|
This is because you're using 1000:1000. Unfortunately, until he fixes it, it's only working as root, i.e. 0:0. Delete the config folder. Set 0:0 and restart. |
There I can see rtorrent starts correctly. If you are trying to start a new container, i suggest you delete all the persistent data and start from scratch (maybe with the other issue you opened, there are rest of configurations of ssl). If you have data on rtorrent instance already, we need to diagnose what's happening looking at logs directory (rtorrent.log). |
I have my containers running without root user without problems. This error is more aesthetic than functional, so if you are having this problem too, we need to diagnose it to see what's happening. |
Ok! I would gladly help. As soon as I get some time today I'll send the logs etc. |
|
Ok @kvn1351 thank you for your help. I have built a new v4.0.1 version with the npm problem solved, you can try with it, but I suppose the problem will be still there. I have tried it on a Synology Box, no error in the log using 1024:100, and rutorrent and flood are working correctly (but they also worked with the permission error in the log). |
|
I downloaded the new version and rtorrent still won't work. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. Brought to you by linuxserver.io
|
|
The error that makes rtorrent crash is 1585315844 C Caught internal_error: 'priority_queue_erase(...) could not find item in queue.'. Have been trying to reproduce it but I can't :( Could you please test a new instance of the container in a clean persistent directory to see if you have the same error? Thank you. |
|
Hi. I have the exact same problem as @rj452 on my dedicated server (Debian 9) with UUID/GUID 1000 with a fresh install. Rutorrent can be accessed but many errors appear and no connexion with rtorrent. If I change it to 0 instead of 1000 then everything works fine. EDIT : Added log in case you need it
|
|
I'm also running into this issue. Here is a I was initially able to connect to rTorrent but it seems like it choked when I copied my session directory over. root@3898bd0aa605:/# ps -aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 200 4 pts/0 Ss+ 21:17 0:00 s6-svscan -t0 /var/run/s6/services
root 35 0.0 0.0 200 4 pts/0 S+ 21:17 0:00 s6-supervise s6-fdholderd
root 402 0.0 0.0 200 64 pts/0 S+ 21:17 0:00 s6-supervise rtelegram
root 403 0.0 0.0 200 4 pts/0 S+ 21:17 0:00 s6-supervise fpm
root 405 0.0 0.0 200 4 pts/0 S+ 21:17 0:00 s6-supervise flood
root 406 0.0 0.0 200 4 pts/0 S+ 21:17 0:00 s6-supervise rutorrent
root 407 0.0 0.0 200 4 pts/0 S+ 21:17 0:00 s6-supervise cron
root 409 0.0 0.0 200 64 pts/0 S+ 21:17 0:00 s6-supervise irssi
root 410 0.0 0.0 200 4 pts/0 S+ 21:17 0:00 s6-supervise nginx
root 412 0.0 0.0 2208 1584 ? Ss 21:17 0:00 bash ./run
abc 413 0.2 0.1 258200 35580 ? Ssl 21:17 0:00 npm
root 414 0.0 0.0 2208 1684 ? Ss 21:17 0:00 bash ./run
root 416 0.0 0.0 2212 1720 ? Ss 21:17 0:00 bash ./run
root 417 0.0 0.0 5848 4468 ? Ss 21:17 0:00 nginx: master process /usr/sbin/nginx -c /config/nginx/nginx.conf
root 434 0.0 0.0 180712 11816 ? Ss 21:17 0:00 php-fpm: master process (/etc/php7/php-fpm.d/rutorrent.conf)
root 437 0.0 0.0 1580 4 ? S 21:17 0:00 /usr/sbin/crond -f -S -l 0 -c /etc/crontabs
root 440 0.0 0.0 772 32 ? Ss 21:17 0:00 dtach -n /detach_sess/.irssi s6-setuidgid abc /usr/bin/irssi --home=/config/.irssi
abc 442 0.3 0.2 40908 37532 pts/1 Ss+ 21:17 0:00 /usr/bin/irssi --home=/config/.irssi
root 446 0.0 0.0 772 36 ? Ss 21:17 0:00 dtach -n /detach_sess/.rtorrent s6-setuidgid abc /usr/local/bin/rtorrent -n -o import=/config/rtorrent/rtorrent.rc
abc 447 94.3 3.4 638084 635840 pts/2 Rsl+ 21:17 4:24 /usr/local/bin/rtorrent -n -o import=/config/rtorrent/rtorrent.rc
abc 449 0.0 0.0 6328 2304 ? S 21:17 0:00 nginx: worker process
abc 455 0.0 0.0 180848 9636 ? S 21:17 0:00 php-fpm: pool rutorrent
abc 456 0.0 0.0 180848 9096 ? S 21:17 0:00 php-fpm: pool rutorrent
abc 466 0.3 0.2 278996 52440 ? Sl 21:17 0:01 node --use_strict server/bin/start.js
root 497 0.0 0.0 1948 560 ? S 21:17 0:00 tail -n 1 -f /config/log/rtorrent/rtorrent.log
root 535 0.0 0.0 2428 2096 pts/3 Ss 21:17 0:00 bash
root 2702 0.0 0.0 2212 1616 ? Ss 21:21 0:00 bash ./run
root 2705 0.0 0.0 1948 532 ? S 21:21 0:00 sleep 1s
root 2709 0.0 0.0 1616 456 pts/3 R+ 21:21 0:00 ps -aux |
|
I am facing the same issue since a few versions back. All I did was update the image and redeploy it and it stopped working. The last 100% working I remember was v4.0.1 Running it in privileged mode made it work again |
|
Some Diagnostic Help 1.sudo docker exec -it container /bin/bash where cointainer is the name of the container, not the image 2.rtorrent -o import=/config/rtorrent/rtorrent.rc The idea is that you will be able to see if rtorrent can even start, I found out my configration file had an error so it never ran. However docker never showed this error. |
|
The problem came back on the newest version The container starts but I cant connect to rtorrent.sock, if I use |
|
i'm also having the same issue i have just setup a new instance and when its start i get the below No connection to rTorrent. Check if it is really running. Check $scgi_port and $scgi_host settings in config.php and scgi_port in rTorrent configuration file. and im using the latest and it also happens with 0.9.8 version |
18.03.2020 20:51:02] No connection to rTorrent. Check if it is really running. Check $scgi_port and $scgi_host settings in config.php and scgi_port in rTorrent configuration file.
How to fix this? 😞
The text was updated successfully, but these errors were encountered: