[Solved] Issue with rTorrent and fstab linked directory

ds105 · 2019-03-22 19:07:10

Long story short, rTorrent is set to save files to a directory outside of it's own file system. That directory is added via FSTAB configuration as shown below. rTorrent can pick up files and create the placeholder files as needed, but can't seem to initiate the download. This normally would indicate a permissions issue, however with rTorrent actually being able to create the files I know that it can see the folder and make changes. I've accessed the shares under the account that the downloader runs under and was able to fully access all files.

I have a similar configuration working in Ubuntu. Can't seem to figure out why it won't work in Arch. I know this isn't an rTorrent expert place, but given that it is Arch was hoping someone might have some insight.

Edit: I don't think this is an rTorrent issue but more of a play nice with Arch issue. I could be wrong. By no means am I a Linux expert. It's been a decade since I went through college and until recently hadn't really touched it since.

Environment:

Unraid hosting basic Arch Linux VM.
Shared folder from the Unraid host added to Arch Linux via mapping within Unraid config and FSTAB configuration
Using rTorrent and RuTorrent as configured from here with some minor modifications for updates to the rTorrent client. Config files below.

FSTAB configuration, which allows for root directory of Unraid shares (direct port from Ubuntu):

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# UUID=f621ea41-4044-4dcc-ad3e-d591ab3cab97
/dev/vda2               /               ext4            rw,relatime     0 1

# UUID=211754de-745d-4a29-8c12-50494d4cea13
/dev/vda1               none            swap            defaults        0 0

unraid  /unraid 9p      trans=virtio,version=9p2000.L,_netdev,rw        0 0

The following configuration files were modified from the original guide and are below. Unlisted files are unmodified from the guide.

.rtorrent.rc

scgi_port = 127.0.0.1:5001
encoding_list = UTF-8
port_range = 45000-45000
port_random = no
check_hash = no
directory = /unraid/Downloads/torrent
session = /home/sdbox/session
encryption = allow_incoming, try_outgoing, enable_retry
#schedule = watch_directory,1,1,"load_start=/home/sdbox/watch/*.torrent"
#schedule = untied_directory,5,5,"stop_untied=/home/sdbox/watch/*.torrent"
#use_udp_trackers = yes
dht = off
#peer_exchange = no
protocol.pex.set = 0
min_peers = 40
max_peers = 100
min_peers_seed = 10
max_peers_seed = 50
max_uploads = 15
execute = {sh,-c,/usr/bin/php /usr/share/nginx/html/rutorrent/php/initplugins.php sdbox &}
schedule = espace_disque_insuffisant,1,30,close_low_diskspace=500M

/usr/share/nginx/html/rutorrent/conf/users/sdbox/config.php

<?php

$pathToExternals['curl'] = '/usr/bin/curl';
$topDirectory = '/';
$scgi_port = 5001;
$scgi_host = '127.0.0.1';
$XMLRPCMountPoint = '/SDBOX';
$tempDirectory = '/usr/share/nginx/html/rutorrent/tmp/';

I've been bouncing my head off my desk for a few days now. Any insight would be greatly appreciated.

Last edited by ds105 (2019-03-23 02:01:42)

freek · 2019-03-22 19:38:15

schedule = watch_directory,1,1,"load_start=/unraid/Downloads/torrent/*.torrent"

ds105 · 2019-03-22 20:14:53

freek wrote:

schedule = watch_directory,1,1,"load_start=/unraid/Downloads/torrent/*.torrent"

Thanks for the reply! Unfortunately that didn't seem to make a difference

I should note that if I specify the download location of /home/sdbox/torrents, the files will download properly. If I attempt to use a symbolic link from /home/sbox/torrents to the desired download directory in /unraid the downloads fail again.

Last edited by ds105 (2019-03-22 20:20:34)

Slithery · 2019-03-22 20:40:27

Can you post the service file you're using to start rtorrent.

Do you have anything like apparmor/selinux running?

ds105 · 2019-03-22 20:46:36

Slithery wrote:

Can you post the service file you're using to start rtorrent.
Do you have anything like apparmor/selinux running?

No, nothing like apparmor or selinux.

[Unit]
Description=rTorrent Daemon
After=network.target

[Service]
Type=forking
KillMode=none
User=sdbox
ExecStart=/usr/bin/tmux new-session -c /usr/bin/rtorrent -s rtorrent -n rtorrent -d rtorrent
ExecStop=/usr/bin/bash -c "/usr/bin/tmux send-keys -t rtorrent C-q && while pidof rtorrent > /dev/null; do sleep 0.5; done"
WorkingDirectory=/home/sdbox/
Restart=on-failure

[Install]
WantedBy=multi-user.target

The same occurs when starting the client manually as the sdbox user

ds105 · 2019-03-23 02:01:26

Kindof-solved. Got samba to work in it's place, though not without it's own annoying hurdles.

Thanks.

Arch Linux

#1 2019-03-22 19:07:10

[Solved] Issue with rTorrent and fstab linked directory

#2 2019-03-22 19:38:15

Re: [Solved] Issue with rTorrent and fstab linked directory

#3 2019-03-22 20:14:53

Re: [Solved] Issue with rTorrent and fstab linked directory

#4 2019-03-22 20:40:27

Re: [Solved] Issue with rTorrent and fstab linked directory

#5 2019-03-22 20:46:36

Re: [Solved] Issue with rTorrent and fstab linked directory

#6 2019-03-23 02:01:26

Re: [Solved] Issue with rTorrent and fstab linked directory

Board footer