Transmission 1.31

[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...

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>
Abnormal terminated transmission?

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...

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
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
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

[harrym]

it's weird to hear all these bad stories
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
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

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...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

[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.