rTorrent + ruTorrent

[Vallius Dax]

Hello,

I have everything setup and running fine, with the exception of a startup problem with lighttpd. I am having the same problem as the user reported on the first page of this thread. On a reboot of the server, it does not start by itself, and I always have to manually start it. Does anyone know why this might be happening?

thx

One interesting thing I noticed when working with the S80 file and the S90 file is, if you edit it with windows eg notepad or wordpad then the file format changes, I suggest making all the file alterations with nano or another linux based txt editor.

If you can't find one already installed then use.

Code: Select all

ipkg install nano

you can then edit the files like this.

Code: Select all

nano /opt/etc/init.d/S80lighttpd

Hope someone finds this useful, it really is noob stuff though.

[Vallius Dax]

I have a few questions: First, if I have active torrents seeing/leeching, should I allow them to finish/get rid of all of them before proceeding with the instructions, or can I just upgrade and allow my torrents to continue after the upgrade seamlessly?

Also, if I follow these instructions and install ruTorrent, am I still able to upgrade the firmware in the future (for example, when 3.0 comes out of beta)? If I do so, will ruTorrent still be there, or will I have to install and configure it all again?

Sorry if I sounds like a total noob when it comes to this kind of thing... but I kinda am one.

1.) Yes, you can migrate seemlessly, although you NAS doesn't have a very powerful processor, so maybe not a great idea for big torrents.

2.) Yes, you are still able to upgrade the firmware, this SHOULD only update the synology installed software, although, there is a remote chance that at some point they may release a big cumulative update that does wipe the existing system and installs a new one.

[spin2]

First of all thanks for the good tutorial.

installing and configuring rTorrent with ruTorrent as easy as possible, but i have a little problem/question.

How can i initate tracker request on rtorrent via ssh?

In the documentation of rtorrent their is this

t/T --- Initiate tracker request. Use capital T to force the request, ignoring the "min interval" set by the tracker.

Or is it even possible to change the interval in client to override the tracker interval?

[Paktas]

spin, not sure on interval changing, but according to manual, tracker request initiation works like a charm with capital T via CLI.

[siimuc]

create: Some functionality will be unavailable. rTorrent's user can't access external program (pgrep).

In Logger i have this error.
Is it serious? any ideas how to fix it?

[Paktas]

create: Some functionality will be unavailable. rTorrent's user can't access external program (pgrep).

siimuc, unless you are going to CREATE torrents, no worries on this message.
However if you do want to create, or simply make this message dissaper, go for:

Code: Select all

ipkg install procps

[Paktas]

Quick tip for those upgrading to DSM 3.0.
Applied new DSM update, after update and reboot ruttorent works like a charm.
Though I backuped rtorrent session data files (/opt/shares/torrent/session) just in case.

[siimuc]

create: Some functionality will be unavailable. rTorrent's user can't access external program (pgrep).

siimuc, unless you are going to CREATE torrents, no worries on this message.
However if you do want to create, or simply make this message dissaper, go for:

Code: Select all

ipkg install procps

i'll let it be for now but thanx for info!

[george@ASDA]

Hi guys, yesterday I followed instructions here and on the wiki to setup r/rutorrent and was very pleased at how quick and simple it was.

Unfortunately, this morning (following a reboot but I'm unsure if that's what started it) I can no longer access the /rutorrent webgui

I'm on a ds110j, and have checked the following:
rtorrent is running, with screen - I can connect to it fine through the cli
lighttpd is running, I can see the default 'lighttpd server is running.' message on port 8081.
when I open the folder /rutorrent (or even directly index.html) I get a browser error, could not find page etc.
the /rutorrent folder is still there in /opt/share/www/ - nothing's changed.

there are no errors/warnings in error.log or access.log for lighttpd (error only shows the server starting, access has no new records since yesterday when it worked)

any ideas??
cheers

[Paktas]

george, I know lighttpd fails to autostart sometimes after reboot and you have to do it manually:

Code: Select all

/opt/etc/init.d/S88lighttpd start

if someone knows how to fix it - speak up...

You can also check if it's really that instance of web server (lighttpd) running with:

Code: Select all

ps aux | grep lighttpd

or

Code: Select all

netstat -a -n | grep 8081

And lastly double check the IP/hostname you are trying on web is the right one

[george@ASDA]

Thanks Paktas, I certainly noticed at the time there were entries in ps and netstat... however coming back to my synology now - the web interface is working! I've no idea what happened.. which is slightly unnerving.

However now I have several other issues such as no windows file sharing, and I can only connect to the diskstation using it's ip, not the name I gave it (possibly a router/host system issue though there).. ah well I am new to all of this will delve deeper and may return to the forum for help!

thanks again.

[leejk]

Regarding the autostart lighttpd problem: I have no idea. I have experienced this since day 1 of installing it. Everything works fine except for when there is a reboot and lighttpd fails to start. Running ps | grep 'lighttpd' after a reboot only shows the Synology version of lighttps running. It's like the startup scripts in /opt/ect/intit.d fails to run or something. Can anyone suggest a way to troubleshoot this?

thx

[vossy]

Hi guys, I just got a ds210j a week ago (my first foray into NAS). Still trying to get the hang of the thing. I followed the tutorial on my DMS 3.0 install and it worked, but I think the problem with lighttpd may be that its getting killed by S86synodms in the /usr/syno/etc/rc.d directory. I haven't had a chance to poke around much but if the /opt/etc/init.d directory gets executed first at boot then this is probably the problem. Anyone know if this is the case and if so how to change the order of execution (couldn't see an inittab)? Will have a more of a play later.

Relevent code in S89synodms:

Code: Select all

      /usr/bin/killall -9 dms > /dev/null 2>&1
      /usr/bin/killall -9 lighttpd > /dev/null 2>&1
      
      DebugLevel=`/bin/get_key_value /etc/synoinfo.conf loglevel_mediaservice`
        echo "Starting Media Service ..."
      # lighttpd must be started after dms for getting ip from /var/run/dms.ip
      ${dms}
      if [ "x${DebugLevel}" != "x" ]; then
         /bin/mkdir -p ${lighttpdlog}
         ${lighttpd} -f ${httpdebug}
      else
         ${lighttpd} -f ${httpconf}
      fi


[vossy]

OK, looks like I was right, a bit of playing around showed /opt/etc/init.d gets run before /usr/syno/etc/rc.d
To get lighthppd to stick I did the following:

cp /opt/etc/init.d/S80lighttpd /usr/syno/etc/rc.d/S87lighttpd.sh

Note: it must run after S86synodms hence the S87 prefix. This is far less than ideal and would probably be removed with any DMS upgrade!
Any of you more experienced users got a better way?? I also noted that this doesn't work as a symbolic link "ln-s", is that because /opt is mounted yet???

[delapaco]

Just wanted to post a really BIG THANK YOU for this excellent guide. Finally I can go on seeding my hundreds of gigabyte torrents day and night ..