Transmission 1.31

Printable View

Show 40 post(s) from this thread on one page

21-08-2008, 08:31
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:

Code:

#! /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
21-08-2008, 10:38
GHS

Removing files

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.
21-08-2008, 18:53
wpte

Quote:

Originally Posted by 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:

Code:

#! /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;)
21-08-2008, 20:21
shouriken

Quote:

Originally Posted by wpte

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.
21-08-2008, 21:22
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...
22-08-2008, 08:28
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
23-08-2008, 11:41
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)?
23-08-2008, 16:13
calebz

Quote:

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.
24-08-2008, 16:57
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
24-08-2008, 17:06
kaizen

Quote:

Originally Posted by 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.

Have you read previous pages?

Where you’ve put your config (using start parameters for transmission-daemon)?
24-08-2008, 18:07
calebz

So theres no config file like the one mentioned on nslu wiki page just the switches for startup of the daemon ?
25-08-2008, 04:44
harrym

Transmission 1.33-1

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).
25-08-2008, 11:36
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

Code:

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
25-08-2008, 15:28
Trailblazer

Went back to 1.22

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
25-08-2008, 21:17
harrym

low priority

Hi,

Quote:

nice transmission-daemon

is good idea, much better response from router.
26-08-2008, 20:59
velcrow

Can you explain what the "nice" does?
26-08-2008, 21:12
gstadler

nice

Quote:

Originally Posted by velcrow

Can you explain what the "nice" does?

http://www.google.com/search?hl=en&q...=Google+Search
27-08-2008, 00:48
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
27-08-2008, 11:35
Kenny

Quote:

Originally Posted by 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

Code:

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.
27-08-2008, 21:24
dclagoa

Quote:

Originally Posted by 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

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 ;-)
28-08-2008, 00:40
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" :)
28-08-2008, 17:36
dclagoa

@velcrow
In that case, you'll indeed notice an increase in the performance ;-)
28-08-2008, 18:18
harrym

New transmission

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.
28-08-2008, 19:03
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
29-08-2008, 11:10
Kenny

is there a string that let you forward transmission incoming port with upnp in the "settings.json" configuration file?
29-08-2008, 14:57
harrym

[tra] <defunct>

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

I have still problems...:(

Quote:

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
29-08-2008, 18:35
wpte

Quote:

Originally Posted by 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.

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
29-08-2008, 19:12
harrym

Quote:

Originally Posted by wpte

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.
29-08-2008, 19:21
samura

Does anyone got problems with adding torrents with more than 35 gigs? I just can't add them...
30-08-2008, 14:26
wpte

Quote:

Originally Posted by samura

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.;)
30-08-2008, 23:45
samura

Thanks for your help!
01-09-2008, 08:49
Valentin

Firewall help needed

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.
01-09-2008, 16:42
Rebel

Log's

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

Any ideas ?
03-09-2008, 14:41
ecori

Hi Guys,
I found a forum where someone created a script to manage transmission, see
http://mybookworld.wikidot.com/forum...ed#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
04-09-2008, 01:50
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.
04-09-2008, 22:03
harrym

Quote:

Originally Posted by 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.

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...
08-09-2008, 10:56
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

Code:

/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)
13-09-2008, 11:40
Silkmann

Quote:

Originally Posted by 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.

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?
16-09-2008, 16:01
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:(
17-09-2008, 08:44
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)

Show 40 post(s) from this thread on one page

All times are GMT +1. The time now is 22:43.