Arch Linux

Mirhawk

Member

Registered: 2015-10-04

Posts: 6

[SOLVED]rtorrent/rutorrent connection issues

So I recently updated my arch setup and this is one of the issue I have been facing.
I have updated rtorrent and have beenusing latest rutorrent setup.
But whenever I try to access rutorrent via web, I get following errors:

[04.04.2020 19:44:59] WebUI started.
[04.04.2020 19:45:00] ruTorrent cannot determine the UID of rTorrent user. Some functionality will be unavailable.
[04.04.2020 19:45:00] rss: Some functionality will be unavailable. Webserver user can't access external program (curl).
[04.04.2020 19:45:00] autotools: Plugin failed to start.
[04.04.2020 19:45:00] erasedata: Plugin failed to start.
[04.04.2020 19:45:00] retrackers: Plugin failed to start.
[04.04.2020 19:45:00] rutracker_check: Plugin will not work. Webserver user must have execute access to the rtorrent session directory ().
[04.04.2020 19:45:00] history: Plugin failed to start.
[04.04.2020 19:45:00] unpack: Plugin failed to start.
[04.04.2020 19:45:00] throttle: Plugin failed to start.
[04.04.2020 19:45:00] ratio: Plugin failed to start.
[04.04.2020 19:45:00] seedingtime: Plugin failed to start.
[04.04.2020 19:45:00] retrackers: Plugin failed to start.
[04.04.2020 19:45:00] mediainfo: Plugin will not work. rTorrent user can't access external program (mediainfo).
[04.04.2020 19:45:00] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.
[04.04.2020 19:47:00] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.
[04.04.2020 19:49:00] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.
[04.04.2020 19:51:01] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.
[04.04.2020 19:53:01] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.
[04.04.2020 19:55:01] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.
[04.04.2020 19:57:01] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.
[04.04.2020 19:59:01] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.

Due to this, I'm not able to manage torrent in rtorrent via web at all.
I think the error is due to

[04.04.2020 19:45:00] ruTorrent cannot determine the UID of rTorrent user. Some functionality will be unavailable.

or

[04.04.2020 19:51:01] Bad response from server: (500 [error,list]) Warning: XMLRPC call is failed.

I have tried updating my config files for rtorrent adn rutorrent, but still they are giving the same issue.
My files are as follows:
systemd script

[Unit]
Description=rTorrent
After=network.target

[Service]
Type=forking
User=1000
Group=1000
KillMode=none
User=%I
ExecStart=/usr/bin/tmux new-session -s rt -n rtorrent -d rtorrent
ExecStop=/usr/bin/bash -c "/usr/bin/tmux send-keys -t rt:rtorrent C-q && while pidof rtorrent > /dev/null; do sleep 0.5; echo rtorrent still running...; done"
WorkingDirectory=/home/%I/

[Install]
WantedBy=multi-user.target

rutorrent config:

<?php
	// configuration parameters

	// for snoopy client
	@define('HTTP_USER_AGENT', 'Mozilla/5.0 (Windows NT 6.0; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0', true);
	@define('HTTP_TIME_OUT', 30, true);	// in seconds
	@define('HTTP_USE_GZIP', true, true);
	$httpIP = null;				// IP string. Or null for any.

	@define('RPC_TIME_OUT', 5, true);	// in seconds

	@define('LOG_RPC_CALLS', false, true);
	@define('LOG_RPC_FAULTS', true, true);

	// for php	
	@define('PHP_USE_GZIP', false, true);
	@define('PHP_GZIP_LEVEL', 2, true);

	$schedule_rand = 10;			// rand for schedulers start, +0..X seconds

	$do_diagnostic = true;
	$log_file = '/tmp/ruterrors.log';		// path to log file (comment or leave blank to disable logging)

	$saveUploadedTorrents = true;		// Save uploaded torrents to profile/torrents directory or not
	$overwriteUploadedTorrents = false;     // Overwrite existing uploaded torrents in profile/torrents directory or make unique name

	$topDirectory = '/';			// Upper available directory. Absolute path with trail slash.
	$forbidUserSettings = false;

	$scgi_port = 0;
	$scgi_host = "unix:///home/user/rpc.socket";
	//$scgi_host = "127.0.0.1";
	//$scgi_host = "localhost";
	
	// For web->rtorrent link through unix domain socket 
	// (scgi_local in rtorrent conf file), change variables 
	// above to something like this:
	//
	// $scgi_port = 0;
	// $scgi_host = "unix:///tmp/rpc.socket";

	$XMLRPCMountPoint = "/RPC2";		// DO NOT DELETE THIS LINE!!! DO NOT COMMENT THIS LINE!!!

	$pathToExternals = array(
		"php" 	=> '',			// Something like /usr/bin/php. If empty, will be found in PATH.
		"curl"	=> '',			// Something like /usr/bin/curl. If empty, will be found in PATH.
		"gzip"	=> '',			// Something like /usr/bin/gzip. If empty, will be found in PATH.
		"id"	=> '',			// Something like /usr/bin/id. If empty, will be found in PATH.
		"stat"	=> '',			// Something like /usr/bin/stat. If empty, will be found in PATH.
	);

	$localhosts = array( 			// list of local interfaces
		"127.0.0.1",
		"localhost",
	);

	$profilePath = '../share';		// Path to user profiles
	$profileMask = 0777;			// Mask for files and directory creation in user profiles.
						// Both Webserver and rtorrent users must have read-write access to it.
						// For example, if Webserver and rtorrent users are in the same group then the value may be 0770.

	$tempDirectory = null;			// Temp directory. Absolute path with trail slash. If null, then autodetect will be used.
	$locale = "UTF8";

and my rutorrent config file:

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed. Remember to
# uncomment the options you wish to enable.

# Maximum and minimum number of peers to connect to per torrent.
#min_peers = 40
#max_peers = 100

# Same as above but for seeding completed torrents (-1 = same as downloading)
#min_peers_seed = 10
#max_peers_seed = 50

# Maximum number of simultanious uploads per torrent.
#max_uploads = 15

# Global upload and download rate in KiB. "0" for unlimited.
#download_rate = 0
#upload_rate = 0

# Default directory to save the downloaded torrents.
directory = /home/user/Downloads/
#scgi_port = localhost:5000

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = /home/user/.rtorrent/session/

#web interfce configuration
scgi_local = /home/user/rpc.socket
execute.nothrow = chmod,770,/home/user/rpc.socket


# Watch a directory for new torrents, and stop those that have been
# deleted.
#schedule = watch_directory,5,5,load_start=./watch/*.torrent
#schedule = untied_directory,5,5,stop_untied=

# Close torrents when diskspace is low.
#schedule = low_diskspace,5,60,close_low_diskspace=100M

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
#port_range = 6890-6999

# Start opening ports at a random position within the port range.
#port_random = no

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
#check_hash = no

# Set whether the client should try to connect to UDP trackers.
#use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
# encryption = allow_incoming,enable_retry,prefer_plaintext

# Enable DHT support for trackerless torrents or when all trackers are down.
# May be set to "disable" (completely disable DHT), "off" (do not start DHT),
# "auto" (start and stop DHT as needed), or "on" (start DHT immediately).
# The default is "off". For DHT to work, a session directory must be defined.
# 
# dht = auto

# UDP port to use for DHT. 
# 
# dht_port = 6881

# Enable peer exchange (for torrents not marked private)
#
# peer_exchange = yes

I have tried searching for similar issue, but there were not many and they didn't solve my issue.

https://github.com/rakshasa/rtorrent/issues/914
https://www.reddit.com/r/rtorrent/comme … _rtorrent/

Tried debugging by fowllowing instructions form here:
https://wiki.archlinux.org/index.php/RTorrent/RuTorrent

I can access rtorrent via terminal and can attach to the tmux session, so this doesn't seem an with the rtorrent.

Edit: One thing I have noticed is that if I stop rtorrent, the rutorrent says "No connection to rTorrent". So at least there is some part of communication between both.

Last edited by Mirhawk (2020-04-18 08:09:30)

Mirhawk

Member

Registered: 2015-10-04

Posts: 6

Re: [SOLVED]rtorrent/rutorrent connection issues

Since only bumping is not allowed, could anyone please point out what I'm missing or if any more details are required?

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [SOLVED]rtorrent/rutorrent connection issues

It's your job to rebuild AUR packages when newer libraries in the official repos are installed.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Mirhawk

Member

Registered: 2015-10-04

Posts: 6

Re: [SOLVED]rtorrent/rutorrent connection issues

Thank you for the advice. I did try rebuilding rtorrent from PKGBUILD and restart, but I'm still facing issue.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [SOLVED]rtorrent/rutorrent connection issues

rtorrent is in the official repos: [community]. rutorrent is the AUR package.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Mirhawk

Member

Registered: 2015-10-04

Posts: 6

Re: [SOLVED]rtorrent/rutorrent connection issues

Funnily enough, I really thought that ruTorrent was just a web application package which just required extraction to webapps. Updating the ruTorrent and applying a fix mentioned AUR package did the trick.
Thank you very much.