ruTorrent 3.3 + rTorrent by WhoCares

Please post questions about ReadyNAS add-ons here.

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby invader980 » Sun Jun 24, 2012 9:36 pm

Ok So file permissions 777 for both files .... same error
invader980
ReadyNAS User
 
Posts: 52
Joined: Mon Aug 08, 2011 7:25 am
ReadyNAS: Ultra

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Dewdman42 » Sun Jun 24, 2012 9:47 pm

like I said, you have to edit the rtorrent.rc file and change some of the paths, you can't just use exactly what I used. Fix that. Check all the permissions
Dewdman42
Advanced ReadyNAS User
 
Posts: 137
Joined: Sun May 06, 2012 10:13 pm

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Dewdman42 » Sun Jun 24, 2012 10:02 pm

also, the way to start rtorrent is to use frontview to start and stop it.
Dewdman42
Advanced ReadyNAS User
 
Posts: 137
Joined: Sun May 06, 2012 10:13 pm

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby invader980 » Sun Jun 24, 2012 10:40 pm

Figured out the problem with the rc file .... Simply editing it in windows ruined the line returns and such i had to download an editer to edit the file correctly ...

.. i am usding front view to start and stop rtorrent ...

assumming the same thing happend with start up i also re-made RUTORRENT_service .. im up and running ( i think will have to test the session part is working)

WOOT WOOT --- told u i was a linux noob lol learned alot tho :

for other noobs out there = i used Komodo Edit 7.0 to edit the files and u have to change the file prefrences /line ending to UNIX (\n) to prevent issues if u edited the files in windows

thanks for trying to help me Dewdman i know its frustration when the user should know better :) lol
invader980
ReadyNAS User
 
Posts: 52
Joined: Mon Aug 08, 2011 7:25 am
ReadyNAS: Ultra

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Dewdman42 » Sun Jun 24, 2012 11:57 pm

I would reccomend for the future you use apt-get to install pico or vim so you can edit the files directly on unix. glad you got it working
Dewdman42
Advanced ReadyNAS User
 
Posts: 137
Joined: Sun May 06, 2012 10:13 pm

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby wizzard » Thu Jul 05, 2012 4:26 am

I need a second pair of eyes to se what I have done wrong. I have earlier had rtorrent running on ubuntu

Symtoms:
- Torrents will not autoload from watched catalogs
- Torrents can not be started, they are stuck in PAUSED (Save as catalog is "./" acording to rutorrent)
- If I restart torrents are gone from rtorrent.

My .rtorrent.rc
Code: Select all
s 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 = /c/media/temp/download/

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

# 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

# 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-6990

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

# 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 = yes

# Set whetever 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 = require,enable_retry,prefer_plaintext
encryption = require

# 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 = disable

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

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

# chmod rwx for everybody
system.umask.set = 0000

# Schedules to watch folders
schedule = watch_directory_1,11,20,"load_start=/c/media/temp/default/*.torrent,d.set_custom1=/c/media/default/"
schedule = watch_directory_2,12,20,"load_start=/c/media/temp/music/*.torrent,d.set_custom1=/c/media/Music/"
schedule = watch_directory_3,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_4,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_5,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_5,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_6,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_7,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_8,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_9,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_10,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_11,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"
schedule = watch_directory_12,12,20,"load_start=/c/media/temp/tv/xx/*.torrent,d.set_custom1=/c/media/Tv/xx/"


# Move completed downloads to preset target
system.method.set_key = event.download.finished,move_complete,"d.set_directory=$d.get_custom1=;execute=mv,-u,$d.get_base_path=,$d.get_custom1="
#
# Do not modify the following parameters unless you know what you're doing.
#
# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10
wizzard
ReadyNAS Newbie
 
Posts: 19
Joined: Thu Jul 05, 2012 4:14 am
ReadyNAS: Ultra

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Dewdman42 » Thu Jul 05, 2012 8:54 am

It sounds suspiciously to me that the session dir is not being used. Did you make sure to create the following directories before starting rtorrent:

Code: Select all
/c/.rtorrent/session/
/c/media/temp/download/


Also, your watch configuration looks off, you have tv/xx repeated a bunch of times?
Dewdman42
Advanced ReadyNAS User
 
Posts: 137
Joined: Sun May 06, 2012 10:13 pm

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby wizzard » Thu Jul 05, 2012 12:42 pm

I missed some permissions, this guide helped me: http://www.readynas.com/forum/viewtopic.php?f=36&t=62668&p=351300&hilit=configure+rtorrent#p351300

the xx is just censored information. Things seam to work now.

Next up is to find a RSS torrent downloader thats works with this setup.

Edit: I saw now the I missed a # at line 1. This was not related.
wizzard
ReadyNAS Newbie
 
Posts: 19
Joined: Thu Jul 05, 2012 4:14 am
ReadyNAS: Ultra

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Dewdman42 » Thu Jul 05, 2012 1:16 pm

There are a few little quirks. For example I have found with the watch feature that if you remove the .torrent files after they've been collected that when it finishes it will get into some kind of stuck state for that torrent and won't start seeding it right. So I plop them in the watch dir, I wait until they have been swept up, then I remove them. There is supposedly a .rctorrent.rc script floating around that will move the torrent files after they are swept up, automatically, but I haven't had time to pursue it.
Dewdman42
Advanced ReadyNAS User
 
Posts: 137
Joined: Sun May 06, 2012 10:13 pm

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Vatoe » Sun Jul 08, 2012 10:40 pm

I have a problem. When I try to download a torrent (from torrent file) I get "Bad response from server: (500 [error,list]) Link to XMLRPC failed. May be, rTorrent is down?". Does anyone know what this means and how I can fix the problem?? After this error message, nothing works, I get thios message: "09.07.2012 15:42:24] Bad link 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." Restarting the service on the NVX just reproduces all the same problems..and as I have indicated elsewhere, I cant seem any torrent client to run, including Transmission (which used to work) and I even tried the uTorrent which doesnt work.

edit: fixed by reinstalling the ReadyNAs firmware.
Vatoe
Advanced ReadyNAS User
 
Posts: 104
Joined: Wed Jun 25, 2008 1:42 am
Location: NSW, Australia
ReadyNAS: NVX

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Vatoe » Mon Jul 09, 2012 10:40 pm

Is there any way making the 'settings sticking process' easier? I have tried to follow the instructions above, but got lost..
Vatoe
Advanced ReadyNAS User
 
Posts: 104
Joined: Wed Jun 25, 2008 1:42 am
Location: NSW, Australia
ReadyNAS: NVX

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Dewdman42 » Mon Jul 09, 2012 11:04 pm

you need a session
Dewdman42
Advanced ReadyNAS User
 
Posts: 137
Joined: Sun May 06, 2012 10:13 pm

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby Vatoe » Tue Jul 10, 2012 12:19 am

Ok I think I have most of the bits done. I'm just not clear on how to get the rutorrent service to automatically start when the NAS powers on...

edit: never mind it does auto starts - just takes a bit longer :D

edit2: It starts automatically some of the times?

edit3: The times it does start, I actually need to to stop and start the service via frontview, so I dont get the "Bad link 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" error message. On restarting it, everything is fine...

edit4: I actually have worked out, it is not starting automatically, even though on some occasions frontview gives the impression (green dot checked box) that it has. If I click on apply in this state ( green dot and checked box) it reports that the service is started and I can then connect as normal. What do I do to get it started automatically - this is the only thing not working for me now??

edit5: Last edit, I promise :D To finish this story, I just ended up uninstalling ruTorrent, then reinstalling it, which broke it and Transmission, I then uninstalled Transmission, reinstalled NVX firmware, and then reinstalled Transmission. Both were then working. I edited and set up all the necessary files for ruTorrent, and tested a restart of the NAS several times - ruTorrent starts automatically and also maintains it settings etc. All seems well now, both Transmission and ruTorrent work without a problem and that hopefully will be the end of my 'saga' and I can start enjoying some automatic downloading...... :rofl: Thanks to all the people that posted there steps here.
Vatoe
Advanced ReadyNAS User
 
Posts: 104
Joined: Wed Jun 25, 2008 1:42 am
Location: NSW, Australia
ReadyNAS: NVX

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby invader980 » Wed Aug 01, 2012 1:53 pm

^^^^ Glad u got urs up and running lol it can be frustrating when ur confused lol


Is there (what would be ) a command to auto COPY what was downloaded to a static dir , but keeps the original files in-tact ON COMPLETION ???? if there r ne configuration experts out there lol ( i am actively googling now and if i find and answer ill post here also) i figure were all on the same page on this thread someone here should know lol

ive worked it down to this particular command in the rc file id like to mod :

Code: Select all
# Move completed downloads to preset target
system.method.set_key = event.download.finished,move_complete,"d.set_directory=$d.get_custom1=;execute=mv,-u,$d.get_base_path=,$d.get_custom1="

could it be as simple as changing "execute=mv" to "execute=cp" ??? wishfullthinking :) that way it will download to the download dir and copy to the move dir ?




***** Found the command ( i was almost right ;) lol )

code was modified as:
Code: Select all
system.method.set_key = event.download.finished,move_complete,"execute=cp,-R,$d.get_base_path=,/c/media/TESTING"

/c/media/TESTING being ur own dir ..... Like i explained this simply makes a copy of the content (on torrent completion) and leave it in a static dir of ur choice eg:/c/media/TESTING
invader980
ReadyNAS User
 
Posts: 52
Joined: Mon Aug 08, 2011 7:25 am
ReadyNAS: Ultra

Re: ruTorrent 3.3 + rTorrent by WhoCares

Postby widde » Thu Oct 18, 2012 2:22 am

Any ideas if you can block IPs somehow in this version? I know the new version of rTorrent have native IP Blocking.
Or are there any other solutions for IPfilter on ReadyNas Ultra?
widde
ReadyNAS Newbie
 
Posts: 6
Joined: Tue Sep 18, 2012 2:42 am
ReadyNAS: Ultra

PreviousNext

Return to General Discussion on ReadyNAS Add-ons



Who is online

Users browsing this forum: Exabot [Bot] and 10 guests