Questions on the use of Transmission

[oleo]

I have upgraded to latest Transmission daemon 0.82+ (r3376) and it looks like the 2GB problem is solved. There are also other substantial changes like libevent that replaced threading model, encryption, peer banning, ...
But after two days of r3376 testing I am a little suspicious that this libevent is not very effective. On one tracker I am getting Tracker: Error - No response from tracker -- will keep trying. that stops download after while. So if someone is willing to test this and report his finding here I've prepared Oleg ipkg at http://oleo.ath.cx/tmp
I will upgrade optware feeds if positive results will be reported.

[leniviy]

Installed this new version. slow file growth stuck at 2139226112 bytes (1.99 Gb)
and then T started download nevertheless.

[admin@router mandriva-linux-2008.0-free-rc2.i586]$ cat /opt/var/log/messages | grep transmissiond
Oct 15 22:03:57 transmissiond[5640]: Transmission daemon 0.82+ (r3376) started - http://transmission.m0k.org/
Oct 15 22:03:59 transmissiond[5640]: Starting torrent /tmp/harddisk/torrent/work/mandriva-linux-2008.0-free-rc2.i586 -'mininova.org'-/mandriva-linux-2008.0-free-rc2.i586 -'mininova.org'-.torrent
Oct 15 22:08:59 transmissiond[5640]: 1192471739 1 dl 70.40 ul 0.00 ld 0.32
Oct 15 22:10:29 transmissiond[5640]: 1192471829 1 dl 54.40 ul 0.00 ld 0.51
Oct 15 22:11:17 transmissiond[5640]: 1192471877 1 dl 50.40 ul 0.00 ld 0.60
Oct 15 22:16:17 transmissiond[5640]: 1192472177 1 dl 48.00 ul 0.00 ld 0.64
Oct 15 22:21:17 transmissiond[5640]: 1192472477 1 dl 52.00 ul 0.00 ld 0.58
Oct 15 22:22:56 transmissiond[5640]: 1192472576 1 dl 32.80 ul 0.00 ld 0.50
Oct 15 22:27:56 transmissiond[5640]: Tracker: Error - Tracker error 3
Oct 15 22:27:56 transmissiond[5640]: 1192472876 1 dl 49.60 ul 0.00 ld 0.59
Oct 15 22:28:17 transmissiond[5640]: 1192472897 1 dl 43.20 ul 0.00 ld 0.68
Oct 15 22:33:17 transmissiond[5640]: 1192473197 1 dl 49.60 ul 0.00 ld 0.69

[mitraku]

It seems that Transmission 0.90 has been released. Can you update the optware feeds with this new version ?

[Aramaki]

Can't remove active torrent. Says

Can only remove suspended torrents! Edit transmission.conf to FORCE_REMOVE.

I uncommented this value in transmission.conf and restarted router, but it still doesn't work and keeps saying the same.

Why's that?

[Oyabun]

Can't remove active torrent. Says
I uncommented this value in transmission.conf and restarted router, but it still doesn't work and keeps saying the same.
Why's that?

Please read back, it is a documented feature. You can remove only suspended torrents.

[Aramaki]

Please read back, it is a documented feature. You can remove only suspended torrents.

I've read docs. I thought that it normaly can remove only suspended and with option on it can do it even without it. My bad ^_^

[oleo]

Can't remove active torrent. Says



I uncommented this value in transmission.conf and restarted router, but it still doesn't work and keeps saying the same.

Why's that?

Due to some mistakes this FORCE remove should be "YES" and not "yes" to work. So If you have troubles with that, just change the case.

[zgfrd]

I have upgraded to latest Transmission daemon 0.82+ (r3376) and it looks like the 2GB problem is solved. There are also other substantial changes like libevent that replaced threading model, encryption, peer banning, ...
But after two days of r3376 testing I am a little suspicious that this libevent is not very effective. On one tracker I am getting Tracker: Error - No response from tracker -- will keep trying. that stops download after while. So if someone is willing to test this and report his finding here I've prepared Oleg ipkg at http://oleo.ath.cx/tmp
I will upgrade optware feeds if positive results will be reported.

this work with OpenWrt and X-wrt?
I use latest Transmission 0.82-3 package from /optware/ddwrt/cross/stable and the same problem files above 2GB (generic I/O error). My safe try it?

[oleo]

Transmission 0.9 does not solve 2GB limit. But it works after two days of testing. I will commit this version in a day or two and then seek for the 2GB bug.

This bug may be uclibc related and all firmwares (X-wrt, OpenWrt, dd-wrt, Oleg, ... ) are affected!

[emes]

I've just setup my wl500gp according to wengis tutorial. Everything seems to work smoothly except that:

Using transmission daemon-

torrents freeze (dl only) after some time (can be after 10mins or 2hours). Everything else is still functional. Except, in a few instances, I could no longer access the web interface.

The folder .../torrents/work becomes inaccessible, i.e. can't do ls or touch

I throttled the upload since otherwise I can't access my network folders using samba2.

[tj_spark]

The folder .../torrents/work becomes inaccessible, i.e. can't do ls or touch

I had the same problem.

It was triggered because the 3rd partition (which is an ext3 type and mounted to /tmp/harddisk like the tut says) was eventually automounted by the router as a vfat type partition to /tmp/harddisk.

At first I thought I had fixed the problem by doing an "umount /tmp/harddisk" before the actual "mount /tmp/harddisk" in my post-mount script.

But after some time the router does the above mentioned automount as vfat again :-(

The problem vanished after I removed a specific nvram setting by unset'ing it.

Try the following on a console as one command:

nvram show | grep -i usb | grep "/tmp/harddisk"

There should be an entry like:

usb_disc0_...=/tmp/harddrive

Then unset this entry:

nvram unset usb_disc0_...

(the points are not part of the name you must write down everything before the "=" sign from the "nvram show" output)

Then you have to save the settings before rebooting:

nvram save


I hope this helps you fix the problem.

TJ

[emes]

thanks for the prompt reply, however, unfortunately this doesn't seem to be the problem.

>> nvram show | grep -i usb | grep "/tmp/harddisk" 
size: 13585 bytes (19183 left)

i.e., there is no entry "/tmp/harddisk", further

>> nvram show | grep -i usb | grep "usb_disc0"
size: 13585 bytes (19183 left)
usb_disc0_port=0
usb_disc0_index=0
usb_disc0_fs_path0=
usb_disc0_fs_path1=
usb_disc0_fs_path2=
usb_disc0_fs_path3=
usb_disc0_fs_path4=
usb_disc0_fs_path5=
usb_disc0_fs_path6=
usb_disc0_dev=
usb_disc0_path0=
usb_disc0_path1=
usb_disc0_path2=
usb_disc0_path3=
usb_disc0_path4=
usb_disc0_path5=
usb_disc0_path6=

[emes]

Looking at the log, one becomes very suspicious of:

GET unknown message '20'

What exactly is this and how do I prevent it from freezing up my torrents as well as not being able to access .../torrent/work?

This problem occurs only when downloading, not when seeding.


see attached: problem_log.png

[oleo]

I suspect problem with disk with such report. Please umount your disk and do
e2fsck -f -y /dev/disk/... on your partitions. If this does not help and you see
SCSI errors when you type /bin/dmesg when system freezes than connect USB disk to the PC with linux and do w2fsck there.

[emes]

YES!

e2fsck -f -y /dev/discs/disc0/...

did the trick.

It's been working very nicely so far, nice!

And thanks for the help