Transmission 1.31

[shouriken]

I had the bad idea to do ipkg update && ipkg upgrade today and I found out that transmission is not working anymore.

It seems that transmission.conf, the cgi script and the watchdog disappeared.

The previous version 1.22 does not exist anymore on http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/

What can I do ?

[mancub]

If you look around on the forums for WL-500gP you can find the transmission.cgi, albeit modded versions which are even nicer. :)

There are .conf files around as well probably...

[shouriken]

transmissiond ( the daemon) is not there either.

I renamed transmission-daemon to transmissiond, but it doesn't works.

I've also get the transmission-watchdog, transmission.cgi from the svn (version 1.22), but they doesn't work with 1.31

[andersos]

That old stuff doesn't work with 1.31 because transmission now uses other methods (JSON) for communication. Use transmission-daemon with the bundled web-ui or the transmission-remote command. Read man for the daemon as theer are many new options now, for example authentication.

But 1.31 had a big bug so private trackers banned it. So now 1.32 is out. Would be nice with new optware package :)

[shouriken]

Can anyone upload somewhere the 1.22 ipk ?

[xflake]

Did the same thing, but launch "transmission-daemon" and browse to http://localhost:9091. Here you have prefs and the (web)-GUI is much better then 1.22.

/flake

[shouriken]

Thank you xflake :)

How do you resume the torrents you were seeding?

And how do you start to download a new torrent?

[andrewgl]

And how do you launch "transmission-daemon"?

[wpte]

right...
I did launch the stuff (done in putty, just type "transmission-daemon" and hit enter)

then I went to the interface at the new port 9091... and I get a link to somewhere but it doesnt take me anywhere, it just keeps waiting:S

[kaizen]

somewhere but it doesnt take me anywhere, it just keeps waiting:S

It works for me
http://routerIP:9091/transmission/web/

Daemon has a few nice switches :)
Options:
-h --help Display this help page and exit
-a --acl <list> Access Control List. (Default: +127.0.0.1)
-b --blocklist Enable peer blocklists
-B --no-blocklist Disable peer blocklists
-f --foreground Run in the foreground instead of daemonizing
-g --config-dir <path> Where to look for configuration files
-p --port <port> RPC port (Default: 9091)
-t --auth Require authentication
-T --no-auth Don't require authentication
-u --username <username> Set username for authentication
-v --password <password> Set password for authentication
-w --download-dir <path> Where to save downloaded data

But - how to move old source, work and target directories to 1.32?

[GoldDigger]

Here is my experience with this new beauty after 9 hours of testing. :D I have upgraded my transmission to 1.31 late last night and I have to confess, I was blown away by the features right after the magical ipkg update && ipkg upgrade.

First off all, the modern web 2.0 look fits in nicely and honestly this is what I have been waiting for. It's simply great. I can't wait to get more aquainted with it, and who knows, maybe add a feature or two to it.

Secondly, the pressure and work load put on Asus is much lesser compared to the previous 1.22 version. I was trying to download a 16GB torrent with 1.22 and Asus couldn't handle it properly. Even with swap on an external usb hdd, sysload was averaging about 2 and speeds weren't too good. However, after the update sysload decreased to 1.1 whereas speeds got roof high, which means even with huge torrents Transmision is maxing out my connection (4mbit). I'm not so sure about any changes in CPU and memory usage. I believe they haven't changed noticeably.

That's it for now. All in all, guys at transmissionbt did a great job once again.

P.S. If you want daemon to start automatically, you can add it to post-boot script.

P.S.2 There is no other way to resume you previous downloading or seeding torrents instead of just moving directories from work to transmission 1.31+ download dir and then starting the correspondent .torrent files. I'm pretty sure they will get recheked and started again.

[GoldDigger]

I apologie for another post. Though here is a screenshot of how it looks like to those, who still hesitate whether or not to upgrade. http://img401.imageshack.us/img401/8710/tr131zy1.jpg

The setup is even more full-proof as there is no more a need for httpd to run web interface. Transmission-daemon comes with its own. This is definetely easier to setup.

On the downside, however, new AJAX interface and transmission-daemon lacks couple of handy features that existed in previous version (1.22, at least). Main thing that it lacks is, a queue system. Right now torrent gets started as soon as added, because there is no option to control the number of active torrents. Traffic/sysload graph is also missing.

[morfy]

what the configuration file of this new transmission? And how do I do run at?

[shouriken]

1.32 is out and is accepted by some private trackers.

I managed to resume seeding torrents by moving the files existing in

/tmp/harddisk/torrent/.config/transmission/resume
and
/tmp/harddisk/torrent/.config/transmission/torrents

to
/tmp/local/root/.config/transmission-daemon/resume
and
/tmp/local/root/.config/transmission-daemon/torrents

and restarting transmission-daemon.

I did not have currently downloading torrents, but I think it should work in the same way.

[wpte]

It works for me
http://routerIP:9091/transmission/web/

Daemon has a few nice switches :)
Options:
-h --help Display this help page and exit
-a --acl <list> Access Control List. (Default: +127.0.0.1)
-b --blocklist Enable peer blocklists
-B --no-blocklist Disable peer blocklists
-f --foreground Run in the foreground instead of daemonizing
-g --config-dir <path> Where to look for configuration files
-p --port <port> RPC port (Default: 9091)
-t --auth Require authentication
-T --no-auth Don't require authentication
-u --username <username> Set username for authentication
-v --password <password> Set password for authentication
-w --download-dir <path> Where to save downloaded data

But - how to move old source, work and target directories to 1.32?

that helped me out a bit, now I did this:

transmission-daemon -p 8008 -w /mnt/torrent -a 192.168.2.

well... it now linked me forward and guess what!
look at the screenshot... not supported browser
:confused: whaat? they support every other browser apart from IE that is being used more than anything...... it doesnt make that big difference I think, the only trouble IE has is with some java based sites, but something plain looking like I saw on the screenshot posted here should be handeled by IE easily:mad:
I guess it's time for me to go and look for a different torrent client:rolleyes:

[morfy]

Transmission hours work, but once you start the daemon, and disappears rrdtool webpage rrdtool not be reached. What is wrong?

[GoldDigger]

that helped me out a bit, now I did this:
well... it now linked me forward and guess what!
look at the screenshot... not supported browser
:confused: whaat? they support every other browser apart from IE that is being used more than anything...... it doesnt make that big difference I think, the only trouble IE has is with some java based sites, but something plain looking like I saw on the screenshot posted here should be handeled by IE easily:mad:
I guess it's time for me to go and look for a different torrent client:rolleyes:

There is no chance (yet?) to get Transmission WebUI running functionally on IE due Explorer not following standards once again. Check out this forum thread: http://forum.transmissionbt.com/viewtopic.php?f=8&t=4907&p=23707

[wpte]

There is no chance (yet?) to get Transmission WebUI running functionally on IE due Explorer not following standards once again. Check out this forum thread: http://forum.transmissionbt.com/viewtopic.php?f=8&t=4907&p=23707

hmm... right, it still sux I have to use a different browser...
I mean I hate firefox because the one time I tried it, it cought a virus and after norton removed it I couldn't start or remove firefox anymore...:(
and opera seems to have problems on showing updated content on websites, you really need to hit the update button to see it:confused:

but for opera it works fine so far, it looks modern this way...
but I dunno, it still looks a bit like windows vista, it's pimped up but I still kinda miss some functionality that has been lost...:rolleyes:

it has great preformance tho... I get 500kb/s all the time:eek:
normally it was about 70kb/s:confused:

[Kenny]

P.S.2 There is no other way to resume you previous downloading or seeding torrents instead of just moving directories from work to transmission 1.31+ download dir and then starting the correspondent .torrent files. I'm pretty sure they will get recheked and started again.

true, moving .torrent files to /tmp/local/root/.config/transmission-daemon/torrents will do the trick

But i have a question:
I inserted transmission-daemon into post-boot but it does not start at boot, why?

[oleo]

Transmission was splitted into two packages with changeset 8882 (http://trac.nslu2-linux.org/optware/changeset/8882).

Clutch package now depends on 1.22 transmisisond package until next upgrade.

[ocelivise]

I completely reinstalled everything on my router including transmission1.32, it works fine but I have few questions:
1. When I rebooted my router(i was forwarding ports), transmission simply forgot all torrent that I was seeding. How can I shutdown transmission before rebooting to avoid this?
2. Where does he put torrent files?
3. Where is configuration file for transmission?

[bogd_A]

A few issues I have with the new transmission:
- transmission-daemon won't start at reboot, I have transmission-daemon in my post-boot
- after a router restart all the settings I made in "Preferences", from the transmission web page are reset
- I had one torrent seeding, with the new transmission, but after a router restart it dissapeared
- compared with the previous ver the downloading speed is smaller, It may be something about the connection with the tracker using the new transmission

How can I reinstall the previous version of transmission?

[lyxes]

I have followed wengi's how to install . Everything was Ok until
vi /opt/etc/transmission.conf the file doesn't exist. The install of transmission was without error . Please help... THANKS !:o



[admin@ASUS root]$ ipkg list_installed
c-ares - 1.5.2-2 - C library that performs DNS requests and name resolves asynch ronously
cron - 4.1-7 - Standard vixie cron, with cron.d addition
e2fslibs - 1.41.0-1 - Ext2 Filesystem Libraries
e2fsprogs - 1.41.0-1 - Ext2 Filesystem Utilities
expat - 2.0.1-1 - XML Parser library
fontconfig - 2.5.0-0 - Font configuration library
freetype - 2.3.6-1 - Free truetype library
gconv-modules - 2.2.5-7 - Provides gconv modules missing from the firmware. The se are used by glibc iconv() implementation.
glib - 2.12.13-1 - The GLib library of C routines.
gnuplot - 4.2.3-1 - Command-line driven interactive data and function plotting u tility
ipkg-opt - 0.99.163-10 - The Itsy Package Manager
libcurl - 7.18.2-3 - Curl is a command line tool for transferring files with URL syntax, supporting FTP, FTPS, HTTP, HTTPS, GOPHER, TELNET, DICT, FI
libgd - 2.0.35-2 - An ANSI C library for the dynamic creation of images
libjpeg - 6b-2 - collection of jpeg tools
libpng - 1.2.29-1 - Portable Network Graphics Libraries
libuclibc++ - 0.2.2-8 - C++ standard library designed for use in embedded system s
logrotate - 3.7.5-2 - Rotates, compresses, removes and mails system log files.
mc - 4.6.1-3 - Midnight Commander File Manager
ncurses - 5.6-3 - NCurses libraries
openssl - 0.9.7m-4 - Openssl provides the ssl implementation in libraries libcry pto and libssl, and is needed by many other applications and librari
popt - 1.14-1 - A C library for parsing command line parameters.
readline - 5.2-2 - The GNU Readline library provides a set of functions for use by applications that allow users to edit command lines as they are
slang - 2.1.3-1 - S-Lang is a multi-platform library designed to allow a develop er to create robust multi-platform software.
transmission - 1.32-1 - lightweight BitTorrent client and daemon
uclibc-opt - 0.9.28-13 - micro C library for embedded Linux systems
zlib - 1.2.3-3 - zlib is a library implementing the 'deflate' compression system .
Successfully terminated.

[ocelivise]

ipkg remove transmssion
ipkg install http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/transmissiond_1.22-1_mipsel.ipk

I also had same problems, also my router became unstable and after many reboots I installed 1.22:(

[andersos]

A few issues I have with the new transmission:
- transmission-daemon won't start at reboot, I have transmission-daemon in my post-boot
- after a router restart all the settings I made in "Preferences", from the transmission web page are reset
- I had one torrent seeding, with the new transmission, but after a router restart it dissapeared
- compared with the previous ver the downloading speed is smaller, It may be something about the connection with the tracker using the new transmission

How can I reinstall the previous version of transmission?

About why it dowsn't start at reboot - I found out that you have to start it with -g option to show where it's "home" is, ie. where settings file etc. are.

[EdSki]

Hi,

Look at this topic, and you get your answer:

http://wl500g.info/showthread.php?t=15562


Ed

[wpte]

when I reboot my torrents are gone... is this the asus download manager after all?:eek:

[kaizen]

when I reboot my torrents are gone... is this the asus download manager after all?:eek:

I’ve found solution for this problem (but I’ve lost some of .torrent files :( ).

It might be because config, .torrent and temp are stored in flash memory, so you have to lashfs etc. to store them before reboot.

Try to move all folders and files from /tmp/local/root/.config/transmission-daemon to /tmp/harddisk/torrent/.config/

Then start transmission with parameters (last two are user and password to acces web interface - remove or change xxxx and yyyy)



transmission-daemon -p 8008 -g /tmp/harddisk/torrent/.config -w /tmp/harddisk/torrent -t --auth -u xxxxxxxx -v yyyyyyyyy


So far it works. After manual start with parameters uploaded .torrent files are stored in /tmp/harddisk/torrent/.config/torrents folders and thera are still there after reboot.

But I have still problem with starting transmission automatically.



nano /usr/local/sbin/post-mount

flashfs save && flashfs commit && flashfs enable && reboot


Doesn't work.

How to start transmission automatically?

[glenn]

Hi

Im new(bie) to this so I followed wengi's guide for setting up the router just yesterday.

Was wondering if someone could explain exactly which of the transmission install/setup steps that should be changed/replaced?

[bogd_A]

ipkg remove transmssion
ipkg install http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/transmissiond_1.22-1_mipsel.ipk

I also had same problems, also my router became unstable and after many reboots I installed 1.22:(

Thanks,

I also returned to 1.22 transmission, but something seems to be wrong.
You can seed your torrents? It seems that i can seed torrents only when they are downloading and are marked as ACTIVE, when they are marked as SEEDING ... nothing happens.

[dclagoa]

@shouriken
Remove package transmission and install package transmissiond

EDIT: Sorry, shouriken i thougt your message was the last :-/ This "show last message first" configuration is killing me :)

[kaizen]

I think, that I've found solution for all my problems with Transmission 1.32

1. Install 1.32
2. Put into post-mount


nano /usr/local/sbin/post-mount


line



/opt/bin/transmission-daemon -p 8008 -g /tmp/harddisk/torrent/.config -w /tmp/harddisk/torrent -t --auth -u USER -v PASSWORD


3. Move all folders and files from /tmp/local/root/.config/transmission-daemon to /tmp/harddisk/torrent/.config/

4. I've got corrupted downloads afer reboot. To close transmission nicely chanve pre-shutdown:



nano /usr/local/sbin/pre-shutdown


Add lines (correct me, if there is better way).



killall transmission-daemon

sleep 30s


5. Save this all


flashfs save && flashfs commit && flashfs enable && reboot


Open http://YOURIP:8008/transmission/web

Change preferences (bottom left corner), save them. To make sure everything warks - restart the router and check, if changes in preferencess was saved.

And one note - change port number to old one or edit post-firewall to accept connections on this port.

[bogd_A]

Transmission was splitted into two packages with changeset 8882 (http://trac.nslu2-linux.org/optware/changeset/8882).

Clutch package now depends on 1.22 transmisisond package until next upgrade.

Hy

Is there a way to put also the 1.22-2 transmissiond on the server?
It was, for me, the best working transmission, with 1.22-1 I have an issue regarding the SEEDING of torrents: It doesn'work, and I had the same issue when the available transmission was the 1.22-1, that untill it was upgraded by the 1.22-2 and everything worked.

Thank you

[glenn]

Im using 1.32, and no matter how many seeders there are i cant connect to more than afew, 12-14 at the max.
How is it with other using 1.32?

Edit: Is there a way to make the web interface prompt for a password if you want to be able to access it from outside your local net?

[rootpuppet]

Please build 1.33 because it support UTF-8
http://forum.transmissionbt.com/viewtopic.php?f=1&t=5697

[oleo]

done with r8927 (http://trac.nslu2-linux.org/optware/changeset/8927)

[iGz]

1.32 is out and is accepted by some private trackers.

I managed to resume seeding torrents by moving the files existing in

/tmp/harddisk/torrent/.config/transmission/resume
and
/tmp/harddisk/torrent/.config/transmission/torrents

to
/tmp/local/root/.config/transmission-daemon/resume
and
/tmp/local/root/.config/transmission-daemon/torrents

and restarting transmission-daemon.

I did not have currently downloading torrents, but I think it should work in the same way.

Hi,
If I did this, and after that when I type to command line

flashfs save && flashfs commit && flashfs enable

I get this error >

tar: Names longer than 100 chars not supported.

And after restart torrent-deamon is in default state with no torrent added. :(

How can I correct this ? :rolleyes:

[rootpuppet]

done with r8927

Awesome! It works much better, simultaneously fix another leaks. Really thanks for fast build!

[iGz]

Hi,
If I did this, and after that when I type to command line

flashfs save && flashfs commit && flashfs enable

I get this error >

tar: Names longer than 100 chars not supported.

And after restart torrent-deamon is in default state with no torrent added. :(

How can I correct this ? :rolleyes:

I solved this. Just changed path for config files by adding --config-dir option for transmission to startup script, and now transmission works great :)
I`m just starting with linux, so i`m newbie :)

[Trailblazer]

I followed Kaisen's advice and now it works great! The only thing I did different is I put it in /opt/torrent which is where my 1.x transmission was. Works like a charm. Thanks for the help!

[shouriken]

Using the idea of wpte presented here

http://wl500g.info/showpost.php?p=107759&postcount=8

I created /opt/etc/init.d/S99trans with the following content:



#! /bin/sh

case $1 in
start)
/opt/bin/transmission-daemon -w /tmp/harddisk/torrent/target -g /tmp/harddisk/torrent/config
;;
stop)
if [ -n "`pidof transmission-daemon`" ] ; then
echo "stopping transmission-daemon"
killall transmission-daemon
fi
;;
restart)
$0 stop
sleep 5
$0 start
;;
*)
echo "usage: $0 (start|stop)"
exit 1
esac


where -w and -g options define the download and the configuration directories.

This way rc.unslung can start/stop the transmission-daemon auto-magically.

Don't forget to

chmod 755 /opt/etc/init.d/S99trans

[GHS]

Any idea on how to deselect unwanted files in torrent, in order that transmission won't download them? Because i have a torrent with about 10 Imax movies of 45 GB, but I want to download only one movie form them, and I couldn't find how to unselect the other movies.

[wpte]

Using the idea of wpte presented here

http://wl500g.info/showpost.php?p=107759&postcount=8

I created /opt/etc/init.d/S99trans with the following content:



#! /bin/sh

case $1 in
start)
/opt/bin/transmission-daemon -w /tmp/harddisk/torrent/target -g /tmp/harddisk/torrent/config
;;
stop)
if [ -n "`pidof transmission-daemon`" ] ; then
echo "stopping transmission-daemon"
killall transmission-daemon
fi
;;
restart)
$0 stop
sleep 5
$0 start
;;
*)
echo "usage: $0 (start|stop)"
exit 1
esac


where -w and -g options define the download and the configuration directories.

This way rc.unslung can start/stop the transmission-daemon auto-magically.

Don't forget to

chmod 755 /opt/etc/init.d/S99trans

ah that is fantastic:D
I'm not really good at writing those scripts:p
I had some problems starting the stuff, but I think that was because of the "start" parameter? because it did work when I ran it manually:confused:
thanks;)

[shouriken]

ah that is fantastic:D
I'm not really good at writing those scripts:p
I had some problems starting the stuff, but I think that was because of the "start" parameter? because it did work when I ran it manually:confused:
thanks;)

I've only tried to write something that is similar to the other scripts in /opt/etc/init.d.

The thanks must go to wengi and the others that contributed the "how to" threads.

[iGz]

Hi, I just want to ask you. How much Transmission loads your CPU on WL500gp v2 with private and public torrents ? When i was downloading 1.2 GB torrent from private tracker, transmission ate approx. 40 % of CPU. I know, this isn`t serious test, but I`m just curious :)
Thanks...

[ecori]

I finally got it working, thanks to all the hints in this thread. I must say, I like it compared to the old 1.22 version. However, I miss the graphical history information, it would be great if this could be available in some way. Also, is it necessary to use cron for scheduling this new transmission? Thanks to Oleo I managed to use cron to unpause transmission, in case I forgot to resume the torrents. Is this possible with this version too? I could not find .paused files, I guess transmission is completely rewritten....
Thanks to Oleo (and others involved of course) for all your great work!:)
Regards,
Ecori

[calebz]

Hey

I also moved to the 1.32. I use OpenWrt with the ipkg-opt Ive upgraded it and it seems to work after starting the daemon.

I read a lot changed on nslu wiki.

Currently I started it manually and it seems to work ok but I cant find the config file and also the script seems to be buggy :
It refreshes and works ok for a while and after that 'hangs up' but the torrent is being leeched. After a moment it refreshes a few time and goes back to 'hang up' state.

Should there still be a cron job for it or its enough to start it once ?
What else should I configure (besides firewall ofcourse)?

[calebz]

Aug 23 16:40:36 (none) user.warn kernel: NET: 9 messages suppressed.
Aug 23 16:40:36 (none) user.warn kernel: ip_conntrack: table full, dropping packet.



Can anybody please tell me where do I find the cfg for this ?
Can more options be adjusted in the cfg file so it doesnt kill the router with such high loads and conntrack? I used 1.0x before and I didnt get this message.

Ive found root@OpenWrt:~/.config/transmission-daemon#
But there are only directories inside without the settings.json file.

[velcrow]

Ok the move from 1.22 to 1.32 is complete - my final bug is that the preferences are not being saved after reboot.

Any help?

Velcrow

[kaizen]

Ok the move from 1.22 to 1.32 is complete - my final bug is that the preferences are not being saved after reboot.

Have you read previous pages?

Where you’ve put your config (using start parameters for transmission-daemon)?

[calebz]

So theres no config file like the one mentioned on nslu wiki page just the switches for startup of the daemon ?

[harrym]

I am very happy for the newest evolution of transmission!!:p

I am newbie, I have ASUS WL-520gU (cheaper and much smaller brother of WL-500gP) couple of days, I try older classical transmission 1.22 ( newly named "transmissiond"), but it was very unstable...
I think, that using cron for watchdog awakening isnt good idea for stability. With 1.22 I have strong problems, mainly web router configuration don't recognise correctly the redirected SYSLOG, and upon few hours router hangs up, totally.

With 1.33 I have not problems yet. Only one. When I reboot router, or another intervention, operating panel of transmission (http://192.168.1.1:8008/transmission/web) is very..., very lazy. > Often I would think, that transmission hangs up, but not...:o


Hmmm, I have next problem.
How can I effectively hibernate transmission, e.g. I need CPU power for another application, e.g. SAMBA, etc?
I use "Pause All" for torrents (no torrent downloading or seeding), but CPU usage is still too high, above 80%!!!
I dont need "killall transmission-daemon", but hibernate (minimal CPU usage and swapped from RAM).

[velcrow]

@ kaizen

Thanks - Have read the previous posts the issue seems to be with just the preferences...the status of existing torrents is kept.

I am assuming that the preferences are stored in the JSON settinngs file. So when I change these using the web interface and save them they are kept but on reboot they are reset.

ONLY the preferences that are not set using the initial command are reset



transmission-daemon -p 8008 -g /tmp/harddisk/torrent/config -w /tmp/harddisk/torrent -t --auth -u xxxxxxxx -v yyyyyyyyy


e.g. the web port and the -w ( working directory are kept)

but the upload /download limit etc. are reset to a default?

Velcrow

[Trailblazer]

I didn't want to go back to 1.22, but I had to since I had too many lockup problems with 1.32 and 1.33. I really like the new interface and will try it again, but for now, 1.22 is working famously.

To install 1.22, there is a special package:

ipkg install transmissiond

worked like a charm. thanks as always oleo!:D

[harrym]

Hi,


nice transmission-daemon

is good idea, much better response from router.

[velcrow]

Can you explain what the "nice" does?

[gstadler]

Can you explain what the "nice" does?

http://www.google.com/search?hl=en&q=linux+command+nice&btnG=Google+Search

[velcrow]

Thanks for the google link -

No really - thanks :rolleyes:

I was more interested in the "real-world" effect this has on Transmission 1.32 and the cpu load of the WL-500gp etc...

But thanks for your input

[Kenny]

@ kaizen

Thanks - Have read the previous posts the issue seems to be with just the preferences...the status of existing torrents is kept.

I am assuming that the preferences are stored in the JSON settinngs file. So when I change these using the web interface and save them they are kept but on reboot they are reset.

ONLY the preferences that are not set using the initial command are reset



transmission-daemon -p 8008 -g /tmp/harddisk/torrent/config -w /tmp/harddisk/torrent -t --auth -u xxxxxxxx -v yyyyyyyyy


e.g. the web port and the -w ( working directory are kept)

but the upload /download limit etc. are reset to a default?

Velcrow

I store my config in /tmp/mnt/harddisk/.config, i start transmission only with -g option, my settings are all there after every reboot. The only problem i encounterd is the torrent checking after reboot. Often i have to delete the "resume" folder into the settings directory and check again every torrent to make it work.
nice transmission-daemon works good for me, really low cpu usage.
Using transmission 1.33b1 right now.

[dclagoa]

Thanks for the google link -

No really - thanks :rolleyes:

I was more interested in the "real-world" effect this has on Transmission 1.32 and the cpu load of the WL-500gp etc...

But thanks for your input

Hey velcrow, there is no such thing as general "real-world" effect. When you set "nice transmission-daemon" you are assigning transmission a priority number of 10. If another process with a lower priority id is running, the system will provide that process with more cpu-time. If only transmission is running, you will not notice anything new, the cpu load will be the same.

On the other hand, if transmission is running, and for example you start a ftp transfer, the system will prioritize the ftp server (supposing it has higher priority), and assign the cpu to the ftp server. When the ftp transfer is complete, then transmission daemon will have the cpu for itself. the cpu load will be the same, but the ftp process will finish earlier.

You can't foresee what the effects will be on your router. Maybe you notice an increase in the performance or maybe not. Because there are a lot of factors which have influence on the cpu load: the services you have installed, the tasks running on the router....The only thing that you can take for granted is that if transmission and another process are battling for cpu, transmission is going to lose ;-)

[velcrow]

@ Kenny

Thanks

Going to remove the "hard coded" settings and see what happens - Is there a setting to control the seeding time as there was in 1.22

@ dclagoa

Thanks

This could be very useful as I use the router to run Twonky media server and when transmission is running (especially 1.32) it responds poorly.

Time to start being "nice" :)

[dclagoa]

@velcrow
In that case, you'll indeed notice an increase in the performance ;-)

[harrym]

I tested transmission 1.3x for a couple last days.
I have not good experiences... :confused:

My transmission session don't survive for 24 hours first and last, yet - it crashed soon (e.g.: I run transmission at 8:00 PM, morning at 6:00 AM is still all OK (running), but at 6:00 PM - return from work - is router locked up or in damaged condition = I must restart it)

I don't know a reason, but with running trasmission is router very labile, much more unstable.

[ecori]

Well, no stability problems here, running for days now without any lockup. I asked a question couple of days ago, concerning how to unpause transmission 1.33. Today I found the solution (I think).
The command is:

transmission-remote -n username:password -tall -s

If this is used as a cron job, all torrents will be resumed automatically at the time you scheduled it. The switch -n username:password is only necessary if you need to login to access transmission, the switch -s means start tall (all torrents).
For me (a noob) it took awhile to figure it out, possibly someone else will find it usefull too
Ecori

[Kenny]

is there a string that let you forward transmission incoming port with upnp in the "settings.json" configuration file?

[harrym]

What is [tra] <defunct>:eek:
Abnormal terminated transmission?:eek:

I have still problems...:(




USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
admin 1 94.4 0.4 10556 68 ? R 07:36 448:46
admin 2 0.0 0.0 0 0 ? S 07:36 0:00 [keventd]
admin 3 0.0 0.0 0 0 ? RN 07:36 0:10 [ksoftirqd_CPU]
admin 4 0.0 0.0 0 0 ? S 07:36 0:09 [kswapd]
admin 5 0.0 0.0 0 0 ? S 07:36 0:00 [bdflush]
admin 6 0.0 0.0 0 0 ? S 07:36 0:00 [kupdated]
admin 7 0.0 0.0 0 0 ? S 07:36 0:02 [mtdblockd]
admin 59 0.0 2.4 1940 348 ? S 07:36 0:13 httpd vlan1
admin 60 0.0 0.0 1936 0 ? Ss 07:36 0:01 nas /tmp/nas.la
admin 64 0.0 0.8 2700 120 ? S 07:36 0:00 syslogd -m 0 -O
admin 65 0.0 0.0 0 0 ? Z 07:36 0:00 [klo] <defunct>
nobody 67 0.0 1.2 960 176 ? S 07:36 0:00 [dnsmasq]
admin 68 0.0 0.0 0 0 ? S 07:36 0:00 [khubd]
admin 76 0.0 0.0 804 0 ? Ss 07:36 0:00 p9100d -f /dev/
admin 83 0.1 0.0 0 0 ? S 07:36 0:45 [usb-storage-0]
admin 84 0.0 0.0 0 0 ? S 07:36 0:00 [scsi_eh_0]
admin 114 0.0 0.9 1452 128 ? Ss 07:36 0:00 infosvr br0
admin 115 0.0 2.1 2376 300 ? Ss 07:36 0:08 watchdog
admin 116 0.0 0.3 2368 44 ? Ss 07:36 0:00 ntp
admin 124 0.0 0.9 1752 132 ? S 07:36 0:00 dropbear
admin 146 0.0 0.0 0 0 ? S 07:36 0:00 [kjournald]
admin 147 0.0 0.0 0 0 ? S 07:36 0:00 [kjournald]
admin 149 0.0 0.0 0 0 ? Zs 07:36 0:19 [nmb] <defunct>
admin 151 0.0 0.0 0 0 ? Zs 07:36 0:00 [smb] <defunct>
admin 162 0.0 0.7 968 100 ? Ss 07:36 0:00 /opt/sbin/cron
admin 168 0.0 5.9 8904 836 ? SN 07:36 0:00 [transmission-]
admin 169 0.0 0.0 0 0 ? ZN 07:36 0:00 [tra] <defunct>
admin 170 1.0 0.0 0 0 ? ZN 07:36 5:10 [tra] <defunct>
admin 171 2.9 5.9 8904 836 ? SN 07:36 13:53 [transmission-]
admin 193 0.0 4.9 2732 688 ? Ss 08:02 0:00 /usr/sbin/nmbd
admin 195 0.0 2.9 3080 416 ? Ss 08:02 0:00 /usr/sbin/smbd
admin 210 0.0 0.0 0 0 ? ZNs 08:02 0:00 [tra] <defunct>
admin 211 0.0 0.0 0 0 ? ZN 08:02 0:00 [tra] <defunct>
admin 221 10.0 4.7 1824 656 ? Ss 15:30 0:01 dropbear
admin 222 10.0 3.9 2736 548 pts/0 Ss 15:30 0:00 -sh
admin 225 0.0 3.6 1448 512 pts/0 R+ 15:30 0:00 ps aux

[wpte]

I tested transmission 1.3x for a couple last days.
I have not good experiences... :confused:

My transmission session don't survive for 24 hours first and last, yet - it crashed soon (e.g.: I run transmission at 8:00 PM, morning at 6:00 AM is still all OK (running), but at 6:00 PM - return from work - is router locked up or in damaged condition = I must restart it)

I don't know a reason, but with running trasmission is router very labile, much more unstable.

it's weird to hear all these bad stories:confused:
apart from I have to use a different browser, I really like this thing
it might be a bit slow on adding new torrents, or starting up
but after that happend, it downloads way more stable than the last version, wich made my ping go sweep around from 50 to 200 in games. this new transmission gives me a steady ping of 70, I like:D
I'm now using the startup script mentioned earlier in this topic, it kinda was my idea, but I didn't make a good script:p

[harrym]

it's weird to hear all these bad stories:confused:
apart from I have to use a different browser, I really like this thing
it might be a bit slow on adding new torrents, or starting up
but after that happend, it downloads way more stable than the last version, wich made my ping go sweep around from 50 to 200 in games. this new transmission gives me a steady ping of 70, I like:D
I'm now using the startup script mentioned earlier in this topic, it kinda was my idea, but I didn't make a good script:p

My router don't lock up now (upgrade from 1.33-1 to 1.33-2), but I have problems with xxx <defunct> (see my post before)...
After a couple of hours transmission is totally zombied(? = defuncted).


I have not more apetit for next tests, I "ipkg remove transmission".
I am waiting for rock-stable version.

[samura]

Does anyone got problems with adding torrents with more than 35 gigs? I just can't add them...

[wpte]

Does anyone got problems with adding torrents with more than 35 gigs? I just can't add them...

you probably got the problem that it doesnt respond for a long time?
what transmission does is, open the torrent file and read wich files are in, how big they are and some hashes for integrity checks.
now it knows that it'll write the files in full size with zero's
if you add a file to download, it'll be 700mb instantly (by example), without it even be finished.

so before it can download, it's going to write a full 35gigs to your hdd.
since usb disks are slow... it takes some time.

quick math:
35000mbyte / 3.6mb/s / 3600 = 2.7 hours
so, it'll take 2.7 hours to write it down, before it can download.

I would recommend something like azereus or bitcomet if you want to download something this large.;)

[samura]

Thanks for your help!

[Valentin]

Hi there!

I'm using WL500GP V1 with the latest stable transmission, and downloading works for me fine, no crash, it is stable. I too find problems with web interface. For example when starting it the firs time, it takes time starting for it, and eats up cpu for a couple of minutes till it recognizes the torrents loaded. My solution for this is the transmission-remote -l that lists the paused torrents. If you start your browser after that, it's faster, no hanging. Starting your paused torrents eats cpu for a couple of minutes too, but -remote won't help this time. So this is a time you have to wait. My problem is, that seeding won't start, however I opened the ports, and canyouseeme.org says my port is open. Can anyone who has working settings help me, where he set his settings that worked for him? I mean is it better to open the port from webinterface, or better to open with iptables? If I download other torrents than it uploads from the seedable torrents too. But if only seeding then no upload at all. I think it might be a problem with communicating with the tracker or sg like that. Is there any possibility to check if the tracker can fully communicate with transmission? Thank's for any help in advance.

[Rebel]

Hi,
I have a Asus WL500gP with Olegs firmware and i am trying to set up transmission logs.

Any ideas ?

[ecori]

Hi Guys,
I found a forum where someone created a script to manage transmission, see
http://mybookworld.wikidot.com/forum/t-79778/transmission-1-31-released#post-251810
This script enables you to manage the torrents (moving finished torrents, or adding torrents via a source directory as with the previous version), but also finish torrents when it reaches a certain ratio or seeding time. The script even allows you to send an email if it finishes a job. I think it is a worthwhile addition to the router setup!
Regards,
Ecori

[ma_lav]

Hi guys,
There is one big problem with current transmission version (1.33): After 1.5-2 day of seeding/downloading transmission exit or crashed. I did't found any log information (sytem log does't have any records about it). So does anyone have same problem, because another guy had same problem, but after HD change this problem dissapear. I've check HD for error's and did't found anything, SMART is green, filesystem check every reboot (always fix something (jurnal for ex.), but i don't think it's a big problem). HD has external power supply and work without any problem.

[harrym]

Hi guys,
There is one big problem with current transmission version (1.33): After 1.5-2 day of seeding/downloading transmission exit or crashed. I did't found any log information (sytem log does't have any records about it). So does anyone have same problem, because another guy had same problem, but after HD change this problem dissapear. I've check HD for error's and did't found anything, SMART is green, filesystem check every reboot (always fix something (jurnal for ex.), but i don't think it's a big problem). HD has external power supply and work without any problem.

I had the same problem.
I deinstall transmission and instead, I actually reduce my cheap "Asus eee 701" in stand-alone fanless x86 server (only 8 Watt power usage).

That is rock-stable solution of transmission...:p

WL-5x0gX are good routers, but only routers...

[velcrow]

I was going back to 1.22 but after some tweaking - things are improving

Its amazing what we will do for nice graphics :)

My tweaks were as follows -

"Nice" the transmission-daemon



/opt/bin/nice transmission-daemon -p 8008 -g /yourdirectory/torrent/config -w /yourdirectory/torrent -t --auth -u xxxxx -v xxxxx


Turn Off "Bandwidth Management" in Oleg's latest firmware - (in the web interface - it's Off by default)

These have really improved the stability and the remote access to the web interface...

( before what was happening is that transmission was taking 95 - 97 % of the cpu so when the http request came in for the web interface it responded poorly)

[Silkmann]

I tested transmission 1.3x for a couple last days.
I have not good experiences... :confused:

My transmission session don't survive for 24 hours first and last, yet - it crashed soon (e.g.: I run transmission at 8:00 PM, morning at 6:00 AM is still all OK (running), but at 6:00 PM - return from work - is router locked up or in damaged condition = I must restart it)

I don't know a reason, but with running trasmission is router very labile, much more unstable.

I have the same problem. After upgrading from 1.22 to 1.31 my router hangs up every day. I doubt it is a problem of big torrents, because files I download basically remain the same.

I am still investigating, but just in case... what is the way to downgrade the transmissiond package?

[ocelivise]

@Silkman Remove the transmission, and in previous pages there is link to the transmission 1.22.

I have question about rpc. I opened the port in iptables so I can access transmission webui from the internet. Then I tried to set the password. I changed in settings.json
from: "rpc-access-control-list": "+127.0.0.1",
"rpc-authentication-required": 0,
"rpc-password": "",

to: "rpc-access-control-list": "+127.0.0.1",
"rpc-authentication-required": 1,
"rpc-password": "MYPASSWORD",

But where is username defined? I tried admin/MYPASSWORD but access is denied:(

[alxndrv]

ocelivise
There should be also "rpc-user": "user", but I think it's better to set user/password using -t key for transmission-daemon since it creates a new file called thpasswd with something looks like hash.

ALL
Does anyone has a problem with "Connection failed" in transmission web-ui right after it was loaded? I have it when I connect from the external network. (with internal network its ok)

[andersos]

Since I started using rpc enabled versions I see "Connection failed" message quite often. Some times it shows directly after ui is loaded and before torrents are displayed, some times it shows after torrents are displayed and I can still do f.ex. resume or stop on torrents. This happens on local network. Seems to me that it must be a timeout problem.

1.34 is released btw.

[alxndrv]

andersos
It mostly happens when the bandwidth is used by torrent traffic, so I think too, it might be time-outs.
Do you know how to manage them in transmission rpc?

[andersos]

I don't think it's possible to affect timeouts through any settings. Would be best to discuss with the devs on irc. I didn't do it yet because I don't currently need the web ui myself. But I think I'll soon mention the problem there.

Btw., 1.34 seems to be very nice. Thanks oleo!

[alxndrv]

I recently have discovered one strange feature of new transmission: it downloads twice less than the old version. So, the time to download e.g. one 700MB movie dropped from appr. 4 hours with old transmission downto 7-8 hours with new version (with my 512Kbit dsl). Does anyone have the same problem?
P.S. I don't have download limitations set in transmission configuration. It reports appr. 52KB/s download speed, so it must download 52*3600*4>700MB in 4 hours but in reality it downloads only appr. 400MB!

[wpte]

still the weird problems I guess...
don't know why everybody has problems, it works perfectly fine for me:confused:
for downloading 700mb movies, it now only takes half an hour for me, instead of a whole day:rolleyes:
alltho it connects to a lot less peers, I download a lot quicker:D

[ocelivise]

I recently have discovered one strange feature of new transmission: it downloads twice less than the old version. So, the time to download e.g. one 700MB movie dropped from appr. 4 hours with old transmission downto 7-8 hours with new version (with my 512Kbit dsl). Does anyone have the same problem?
P.S. I don't have download limitations set in transmission configuration. It reports appr. 52KB/s download speed, so it must download 52*3600*4>700MB in 4 hours but in reality it downloads only appr. 400MB!



Yes!!! I have same problem, I even reinstalled everything today and problem is still there.
It's showing ~90 kb/s speed,but speed recorded on tracker is ~35kb/s
It simply uses 90kb/s of my bandwidth but effectively donwloading at 2x,3x less!!!!
Downloaded amount in the inspector is also weird, sometimes it is going backwards. It shows 55.3Mb and few seconds later it is showing 55.2MB

I think that that problem started when I upgraded from 1.33 to 1.34

[andersos]

andersos
It mostly happens when the bandwidth is used by torrent traffic, so I think too, it might be time-outs.
Do you know how to manage them in transmission rpc?

It seems that after they changed to using evhttpd yesterday Clutch works well again :) No more errors for me at least. I now run trunk revision 6804.

[jrosado]

I've been running 1.33-2 for about 30 days without a single hiccup :D

Best transmission i ever seen running on my asus ;)

[Kenny]

I'm encoutering a problem with the WebUI: it keeps telling me

Connection Failed
Could not connect to the server. You may need to reload the page to reconnect.and i cannot manage my torrents.
Running transmission 1.34

[wpte]

I'm encoutering a problem with the WebUI: it keeps telling me
and i cannot manage my torrents.
Running transmission 1.34

what browser do you use, and how do you connect?
wireless, via wan, via lan

[Kenny]

what browser do you use, and how do you connect?
wireless, via wan, via lan
Using firefox/opera and connecting through lan and wireless (same result)

[alxndrv]

It seems that after they changed to using evhttpd yesterday Clutch works well again :) No more errors for me at least. I now run trunk revision 6804.

Can you please share this version of transmission?

[andersos]

Can you please share this version of transmission?

I cross-compiled it for my Maxtor Sharede Storage II. Don't know if it works on your machine.

But Clutch loads very fast now :) No error messages so far.

[alxndrv]

Ok, thanks, I can also compile it on my asus, thought you already have the binaries

[Silkmann]

@Silkman Remove the transmission, and in previous pages there is link to the transmission 1.22.


Unfortunately it is not available anymore
(http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/transmissiond_1.22-1_mipsel.ipk)

Can I still find it somewhere?

[andersos]

Ok, thanks, I can also compile it on my asus, thought you already have the binaries

And today, in r6820, they implemented compression of the json data and web ui data to further speed things up.

[ocelivise]

What about slow dl speed problem:(? Anyone:confused:

[andersos]

I never had reason to complain on dl speed.

[velcrow]

Hi All,

Have now returned to 1.22 (transmissiond) - Why

Stable, and a smaller cpu and memory footprint, the final reason was remote access - the graphics & ajax were nice but the fast responce of 1.22 is much better.

One other final reason is that I had segmetation faults ( now this might not be trans 1.3x fault) but all well since I reinstalled my old system.

Velcrow

[dzontra]

What about slow dl speed problem:(? Anyone:confused:

It's also slow (version 1.34 upgraded today; I had the same bug with 1.31) on my asus. It says 50KB/s but in real life it's very slow. About 1/2 or 1/3 of declared speed.
Transmission-remote and webUI declares same speed but it does not work like it says. For example I'm downloading 10% of my torrent and it says 75.2Mb. Then I have to wait for 10 seconds until it's changed to 75.3Mb, with declared 50MB/s speed.

I tried to turn off/on encryption, nothing changed. I don't use any other limitations in my config. RAM is almost full and asus is using 3Mb of swap.

Did anybody managed to solve this problem?

thanks

[TVadim]

It's also slow (version 1.34 upgraded today; I had the same bug with 1.31) on my asus. It says 50KB/s but in real life it's very slow. About 1/2 or 1/3 of declared speed.
Transmission-remote and webUI declares same speed but it does not work like it says. For example I'm downloading 10% of my torrent and it says 75.2Mb. Then I have to wait for 10 seconds until it's changed to 75.3Mb, with declared 50MB/s speed.

I tried to turn off/on encryption, nothing changed. I don't use any other limitations in my config. RAM is almost full and asus is using 3Mb of swap.

Did anybody managed to solve this problem?

thanks

It's fixed http://trac.transmissionbt.com/ticket/1305#comment:13.
We wait, when Oleo will compile transmission.

[dzontra]

It's fixed http://trac.transmissionbt.com/ticket/1305#comment:13.
We wait, when Oleo will compile transmission.

Great :) I can't wait to try.

[TVadim]

Great :) I can't wait to try.
Reduction max-peers-global to 10-15 in settings.json. This increase download to 60-80%.

[dzontra]

works significantly better :) Thanks for the advice.

[calebz]

where is settings.json !?

[dzontra]

where is settings.json !?

in config folder :)
Important: first turn off transmission, then change file. Otherwise the changes will be lost.

[calebz]

All i can see is transmission/web folder where there is no such file
Can you be more precise? Im running openwrt.

[dzontra]

I start transmission with following line:

/bin/nice /opt/bin/transmission-daemon -g /tmp/harddisk/share/torrent/config

My statup script says where is "config" folder.

regards

[vinyols]

compuarc@WL-001FC651356E root]$ /opt/etc/init.d/S90transmission-daemon start
updating blocklist, ~4MB
gunzip: Invalid magic
starting transmission
Transmission 1.41b4 (7408) http://www.transmissionbt.com/
A fast and easy BitTorrent client

transmission-daemon is a headless Transmission session
that can be controlled via transmission-remote or Clutch.

Usage: transmission-daemon [options]

Options:
-h --help Display this help page and exit
-a --allowed <list> Allowed IP addresses. (Default: 127.0.0.1)
-b --blocklist Enable peer blocklists
-B --no-blocklist Disable peer blocklists
-f --foreground Run in the foreground instead of daemonizing
-g --config-dir <path> Where to look for configuration files
-p --port <port> RPC port (Default: 9091)
-t --auth Require authentication
-T --no-auth Don't require authentication
-u --username <username> Set username for authentication
-v --password <password> Set password for authentication
-w --download-dir <path> Where to save downloaded data
/opt/etc/init.d/S90transmission-daemon: /opt/etc/init.d/S90transmission-daemon: 32: /tmp/harddisk/transmission/config: Permission denied
/opt/etc/init.d/S90transmission-daemon: /opt/etc/init.d/S90transmission-daemon: 32: /tmp/harddisk/transmission/download: Permission denied
[compuarc@WL-001FC651356E root]$

my change prmissions in 755 /tmp/harddisk/transmission/download and /tmp/harddisk/transmission/config

[swordfish77]

Hello everyone,
I install transmission and seems to be a good torrent program. I have a wd 500 GB HDD, but because of some things (HD movie..) i remain without space. Now i want to buy a 750 GB extern hdd and i want to attach to my wl500GP router ,to continue with downloads job. Can i connect a usb hub on my box, without interference between devices(i have a printer who looks very well and i want to keep it in a system) and how to setup the Oleg firmware to recognize the second hdd ? It's enough to format second hdd with one large ext3 partition?
Thank u very much, u do a great job here !!