August 27, 200916 yr I've got UnRaid working on an old IBM NetVista machine I had lying around. I have UnRaid 4.4.2 and BubbaRaid 0.01.17b on the memory card which I believe are the latest versions. I have the array set up and can connect to the server. However when I go to start the rtorrent server I get a popup window saying Starting rTorrent daemon... (this will take a few seconds) .... rTorrent daemon did not restart, and reported error: The paths in .rtorrent.rc are correct and present ( I made them manually ) so what have I missed ?
August 27, 200916 yr Perhaps post the contents of the mentioned files so that we can take a look at them and make sure they look correct. Can you start any of the other services (Slimserver, uNotify, NzbGet)? if not then there might be a problem with the bubbaRAID install. I think we have had a couple reports of peoples flash drives being the problem. Either using another flash drive fixed it, or a complete format with the HP flash drive format tool and a reinstall of everything seemed to work.
August 27, 200916 yr Author I can start all the other services fine. The .rc file is below. # This is the resource file for rTorrent. # BubbaRaid expects this file to be in /root/.rtorrent.rc # # Based on original .rtorrent.rc file from http://libtorrent.rakshasa.no/ # Modified by Bubba for BubbaRaid # # This assumes the following directory structure: # # /mnt/disk1/torrents/downloading - Temporaray location for torrents while downloading (see "directory") # /mnt/disk1/torrents/complete - Torrents are moved here when complete (see "on_finished") # /mnt/disk1/torrents/auto - The 'autoload' directory for rtorrent to use. Place a file # in here, and rtorrent loads it automatically. # # /mnt/disk1/torrents/downloading/rtorrent.session - for storing rtorrent session information # # 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 = 50 # Default directory to save the downloaded torrents. directory = /mnt/disk1/torrents/downloading # Default session directory. Make sure you don't run multiple instance # of rtorrent using the same session directory. Perhaps using a # relative path? session = /mnt/disk1/torrents/downloading/rtorrent.session # Watch a directory for new torrents, and stop those that have been # deleted. schedule = watch_directory,5,5,load_start=/mnt/disk1/torrents/auto/*.torrent schedule = untied_directory,5,5,stop_untied= # Close torrents when diskspace is low. */ #schedule = low_diskspace,5,60,close_low_diskspace=100M # Stop torrents when reaching upload ratio in percent, # when also reaching total upload in bytes, or when # reaching final upload ratio in percent. # example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0 #schedule = ratio,60,60,stop_on_ratio=200,200M,2000 execute_log = /var/log/rtorrent.log # When the torrent finishes, it executes "mv -n <base_path> ~/Download/" # and then sets the destination directory to "~/Download/". (0.7.7 ) on_finished = move_complete,"execute=mv,-u,$d.get_base_path=,/mnt/disk1/torrents/complete/ .set_directory=/mnt/disk1/torrents/complete/" # 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 # Set up XMLRPC port same as in lighttpd config scgi_port = 127.0.0.1:5000 # 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 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 = allow_incoming,enable_retry,prefer_plaintext # # 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 # Max number of files to keep open simultaniously. #max_open_files = 128 # Number of sockets to simultaneously keep open. #max_open_sockets = <no default> # Example of scheduling commands: Switch between two ip's every 5 # seconds. #schedule = "ip_tick1,5,10,ip=torretta" #schedule = "ip_tick2,10,10,ip=lampedusa" # Remove a scheduled event. #schedule_remove = "ip_tick1"
August 27, 200916 yr have you actually created the folders you specified in the .rtorrent.rc file? you have to create them exactly how the structure is laid out in that file or rtorrent won't know what to do. you will have to create: 1. The folder torrents at /mnt/disk1/ 2. The folder downloading at /mnt/disk1/torrents/ 3. The folder complete at /mnt/disk1/torrents/ 4. The folder auto at /mnt/disk1/torrents/ 5. The FILE rtorrent.session at /mnt/disk1/torrents/downloading/ You will have to create these as i do not think rtorrent itself does.
August 27, 200916 yr Author Yeah I manually created all the folders / files before. I have double checked and they are all correct. The rtorrent.session file is just a blank file.
August 27, 200916 yr Yeah I manually created all the folders / files before. I have double checked and they are all correct. The rtorrent.session file is just a blank file. how did you create those folders? the rtorrent daemon might not have privileges to write to those folders and the file. Do a chmod 777 on the /mnt/disk1/torrents folder and everything inside it to see if that helps. Do some googling on chmod if you need the command to do it.
Archived
This topic is now archived and is closed to further replies.