rtorrent


Recommended Posts

Looks like it should work, what is in the rtorrent.install directory?

 

 

All the file listed in this first post:

 

curl-7.19.6-i486-1_slack12.2.tgz* 

libtorrent-0.12.4-i486-1.tgz*

libidn-1.5-i486-1.tgz*           

rtorrent-0.8.4-i486-1.tgz*

libsigc++-2.0.18-i486-1.tgz*     

xmlrpc-c-1.11.00-i486-1.tgz*

 

Link to comment
  • Replies 91
  • Created
  • Last Reply

Top Posters In This Topic

I do not have an answer for you.

 

What you can try doing is capturing stdout/stderr to a log file for review.

 

put the following lines in front of all the output you want to capture.

 

exec 1>/var/log/go

exec 2>&1

 

This will redirect stdout (&1) to a file /var/log/go

and redirect stderr to stdout which would go to /var/log/go.

 

Start up the system, after it's done login and do a

less /var/log/go and see what it says.

 

Link to comment

Two things I see...

 

First, you did not delay after invoking emhttp before starting rtorrent.  It it is expecting the array to be on-line, it will fail...

 

You can put something like

sleep 30

before the remaining commands.  It takes some time to start the array and mount the drives... you may not be giving it the time it needs.

 

Next, the PATH has not yet been set to include the current directory.  If your install scripts need it, they will fail.

Once you log on, the PATH in your telnet session looks like this:

/usr/local/sbin:/usr/sbin:/sbin:./:/usr/local/bin:/usr/bin:/bin

 

I strongly suggest you only put the current directory at the end of the path, as it is defined by default in the unRAID distribution, it breaks every security guideline in existence.

 

Put a line like this in place prior to the lines you use to install and start the "screen" process.

PATH=/bin:/usr/bin:/usr/local/bin:/usr/local/sbin:.

Link to comment

I do not have an answer for you.

 

What you can try doing is capturing stdout/stderr to a log file for review.

 

put the following lines in front of all the output you want to capture.

 

exec 1>/var/log/go

exec 2>&1

 

This will redirect stdout (&1) to a file /var/log/go

and redirect stderr to stdout which would go to /var/log/go.

 

Start up the system, after it's done login and do a

less /var/log/go and see what it says.

 

 

sorry weebotech, I don't understand what I need to do.

 

I've put: exec 1>/var/log/go screen -d -m rtorrent

 

In my go file... but where do I type exec 2>&1? after the command? anything I type for that yields no results.

 

 

 

Joe L.: Thank you for contributing, I have attempted putting the sleep but it still fails. This only fails within the script, if i manually type "screen -d -m rtorrent" everything works just fine, I don't see an installation being a problem. I don't understand though what you are referring to about "Path" (I'm a newbie when it comes to linux, I quite literarily started it when I signed up in this forum to learn more about unraid - about 3 weeks).

 

When i type $PATH, I get the following:

 

root@Tower:~# $PATH

-bash: /usr/local/sbin:/usr/sbin:/sbin:./:/usr/local/bin:/usr/bin:/bin: No such file or directory

 

It seems liek they are already set without needing to put the line you added, unless I am missing something.

Link to comment

 

Try these mods for your go script

 

#!/bin/bash^M
# Start the Management Utility^M
/usr/local/sbin/emhttp &^M

echo "Pausing 30 seconds for array to come online"
sleep 30
exec 1>/var/log/go
exec 2>&1 

#We will now start Unraid-Web
installpkg /boot/unraidweb.tgz

#Install rtorrent
installpkg /boot/rtorrent.install/*

#Install Screen
mkdir /var/log/wtmp
installpkg /boot/screen/*

#Test for copying screenrc
#cp /boot/screenrc /etc/screenrc

#Make symbolic link of rtorrent.rc
ln -s /boot/rtorrent.rc /root/.rtorrent.rc

#Run rtorrent under a screen
/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent

Link to comment

it doesn't seem to give any errors, i even tried moving around what gets installed when, but i always get the same outcome.. it seems to be fine

 

I won't bore you with the text because it's all the installation stuff, and this is how it ends:

 

"Installing package xmlrpc-c-1.11.00-i486-1...

PACKAGE DESCRIPTION:

Executing install script for xmlrpc-c-1.11.00-i486-1..."

 

Basically the installation of the last package. I don't thing it should say anything else below that considering that there is normally no output when i run screen -dmS.

 

BUT, I just tested my rutorrent, and it seems to be able to properly connect to rtorrent... which means it's running.

 

When I go do a screen -ls though, nothing comes up... so I don't know how to control rtorrent.

 

 

Link to comment

ok so just to update.

 

this line did not work for some reason:

 

ln -s /boot/rtorrent.rc /root/.rtorrent.rc

 

But your screen -dmS rtorrent rtorrent -n -o import=/boot/rtorrent.rc does the same thing so no biggy.

 

While everything works though, the socket gets created on /.screen instead of ~/.screen for some reason.

 

But again not a big deal, I just have in my go script to "ln -s /.screen /root/" and I can invoke the screen if I need to.

 

So all in all, thanks to all of your help, because I got it working :)

Link to comment

hey Flixx,

 

I was wondering if you could grab a screenshot of rutorrent for me? Particularly, I'm interested in the Options > Preferences > Advanced section.

 

Heck, might not even need a screenshot, if you can confirm that I can change the bt.transp_disposition, that would be fantastic. Here's a screencap of the option from uTorrent.

 

utorrent.png

Link to comment

BUT, I just tested my rutorrent, and it seems to be able to properly connect to rtorrent... which means it's running.

 

How did you get rutorrent working? Did you use the unRaidWEB package?

 

ok so just to update.

this line did not work for some reason:

ln -s /boot/rtorrent.rc /root/.rtorrent.rc

But your screen -dmS rtorrent rtorrent -n -o import=/boot/rtorrent.rc does the same thing so no biggy.

 

You might want to consider the custom addon directory structure on your /boot flash.

 

I.E. using

 

/boot/custom/etc/  for your etc and config files.

 

http://lime-technology.com/wiki/index.php/Third_Party_Boot_Flash_Plugin_Architecture

 

Link to comment

BUT, I just tested my rutorrent, and it seems to be able to properly connect to rtorrent... which means it's running.

 

How did you get rutorrent working? Did you use the unRaidWEB package?

 

ok so just to update.

this line did not work for some reason:

ln -s /boot/rtorrent.rc /root/.rtorrent.rc

But your screen -dmS rtorrent rtorrent -n -o import=/boot/rtorrent.rc does the same thing so no biggy.

 

You might want to consider the custom addon directory structure on your /boot flash.

 

I.E. using

 

/boot/custom/etc/  for your etc and config files.

 

http://lime-technology.com/wiki/index.php/Third_Party_Boot_Flash_Plugin_Architecture

 

 

Thanks Weebotech, I was going to clean up my files now that I got it all working the way I want to. I'm glad there is some structure defined.

 

I was using BubbaRaid with RUtorrent installed, but rtorrent was outdated for my private trackers. I had to resort to Unraid-Web with this custom rtorrent package and the web interface.

 

I like rutorrent because of the rss feature very similar to Utorrent.

 

 

KewJoe: That option doesn't exist in RUtorrent

Link to comment

Thanks for checking :)

 

From what I can tell, that merely controlls what protocol the BitTorrent engine uses, TCP or UDP. If you're trying to work around ISPs throttling your connection, there are better (but more advanced) ways of doing so. Did you try the firewall approach?

 

I'm currently using uTorrent on my W7 box. I'm using the method i mentioned above and its working. I'm exploring moving my torrenting to my unRAID box. I will check out that link you sent, thanks!

Link to comment
  • 2 weeks later...
  • 3 weeks later...

I haven't advanced far enough to need BubbaRaid (yet), but I want to use rutorrent on my unRaid. Does lightpd need to be installed to run ruTorrent?

 

You'll need 'a' web server with scgi and php support.

 

The path of least resistence is to use the 'unweb' package.

 

http://lime-technology.com/forum/index.php?topic=3354.0

 

I'm using this, with rutorrent installed and running against my build of rtorrent from the first post. All seems ok.

Link to comment
  • 1 month later...

I have the following 'go' script.

but neither screen nor rtorrent are started

 

Yet, I can start them manually just replicating the line from the 'go' script:

/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent

Why?

 

 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

# cache directories
/boot/cache_dirs -w

# S.M.A.R.T. monitor
pushd /boot/smart
smarthistory
popd


# We will now start Unraid-Web
installpkg /boot/unraidweb/*


# Install TCP/IP Bandwidth Meter
installpkg /boot/bwm-ng/*


# run sleep S3 script
/boot/s3_notHrHdTcpIp.sh &


# Install rtorrent
installpkg /boot/rtorrent/*


# Install Screen
mkdir /var/log/wtmp
installpkg /boot/screen/*


# Test for copying screenrc
#cp /boot/screenrc /etc/screenrc


# Make symbolic link of rtorrent.rc
ln -s /boot/rtorrent.rc /root/.rtorrent.rc


# Turn off ^S and ^Q as rtorrent uses these keys
stty stop undef
stty start undef

export TERM=linux

# Run rtorrent under a screen
/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent

 

Link to comment

I have the following 'go' script.

but neither screen nor rtorrent are started

 

Yet, I can start them manually just replicating the line from the 'go' script:

/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent

Why?

 

 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

# cache directories
/boot/cache_dirs -w

# S.M.A.R.T. monitor
pushd /boot/smart
smarthistory
popd


# We will now start Unraid-Web
installpkg /boot/unraidweb/*


# Install TCP/IP Bandwidth Meter
installpkg /boot/bwm-ng/*


# run sleep S3 script
/boot/s3_notHrHdTcpIp.sh &


# Install rtorrent
installpkg /boot/rtorrent/*


# Install Screen
mkdir /var/log/wtmp
installpkg /boot/screen/*


# Test for copying screenrc
#cp /boot/screenrc /etc/screenrc


# Make symbolic link of rtorrent.rc
ln -s /boot/rtorrent.rc /root/.rtorrent.rc


# Turn off ^S and ^Q as rtorrent uses these keys
stty stop undef
stty start undef

export TERM=linux

# Run rtorrent under a screen
/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent

 

 

The array might not be online quite yet so that last line does not quite work try switching that line to:

echo "/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent" | at now + 2 minutes

 

that should delay the start for 2 minutes after that line is run, and should be enough time to get it started properly

Link to comment

I have the following 'go' script.

but neither screen nor rtorrent are started

 

Yet, I can start them manually just replicating the line from the 'go' script:

/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent

Why?

 

 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

# cache directories
/boot/cache_dirs -w

# S.M.A.R.T. monitor
pushd /boot/smart
smarthistory
popd


# We will now start Unraid-Web
installpkg /boot/unraidweb/*


# Install TCP/IP Bandwidth Meter
installpkg /boot/bwm-ng/*


# run sleep S3 script
/boot/s3_notHrHdTcpIp.sh &


# Install rtorrent
installpkg /boot/rtorrent/*


# Install Screen
mkdir /var/log/wtmp
installpkg /boot/screen/*


# Test for copying screenrc
#cp /boot/screenrc /etc/screenrc


# Make symbolic link of rtorrent.rc
ln -s /boot/rtorrent.rc /root/.rtorrent.rc


# Turn off ^S and ^Q as rtorrent uses these keys
stty stop undef
stty start undef

export TERM=linux

# Run rtorrent under a screen
/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent

 

 

The array might not be online quite yet so that last line does not quite work try switching that line to:

echo "/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent" | at now + 2 minutes

 

that should delay the start for 2 minutes after that line is run, and should be enough time to get it started properly

 

I see both screen and rtorrent in the process list (ps -A), but when I try to run 'screen -list' or 'screen -x rtorrent' I get nothing and an error for the last: "There is no screen to be attached matching rtorrent."

Link to comment

I see both screen and rtorrent in the process list (ps -A), but when I try to run 'screen -list' or 'screen -x rtorrent' I get nothing and an error for the last: "There is no screen to be attached matching rtorrent."

 

I would try rearranging the lines a little bit.  To make it a little more clean.  Like putting the two rtorrent related lines closer to each other in the script so that you can edit and change them when you need to.  Anyway i would "remove" your two sections and do something like this:

 

# Install rtorrent and attach screen
echo "installpkg /boot/rtorrent/*" | at now + 2 minutes
echo "/usr/bin/screen -T linux -dmUS rtorrent /usr/bin/rtorrent" | at now + 4 minutes

 

rtorrent can take a while to start if you have a few torrents and stuff in it, so this might help with the issue.

Link to comment

This is what I still receive

 

root@VAULT:~# screen -list
No Sockets found in /root/.screen.

 

 

If add the the other line advised here with symbolic link, I get another error when running 'screen -list' that it cannot access the file.

 

I attached the monitor to Lime, I removed the job scheduling commands (now), and I did not see any errors.

But I still see screen & rtorrent in the Air, and nothing happens. It is kind of ziombie..

 

Let's forget this screen. As I ran it from the command line, I do not think this is the way I shall go.

I am like going 20 years back to the BBS era..

 

 

What about installing web UI? I tried to install rutorrent with unraidweb, the the last one crashed each time I try to configure its www directory to rutorrent

 

 

[ Jesus.. I install mtorrent on Windows in 5 minutes. This is my 2nd day.. ]

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.