Transmission 1.80 headless going backwards

[nicob]

Just tried the 1.83.., same thing here with a nslu2 unit running usnlung 6.10..
I would like to know why ethanheadlongjr and short2ground seemingly have no problems with the 1.83 after compiling it themselves..

I am running also unslung 6.1 on a NSLU2 device. So it might be a dependancy thing?
It sure looks like it if it is really working for ethanheadlongjr and short2ground...

[short2ground]

I did go back to unslung 6.08 and have had no issues since compiling 1.83. Unslung 6.10 seemed to have booting issues. I followed the guide here: http://mybookworld.wikidot.com/forum/t- ... pendancies using steps 1-3 then used the ./configure string from http://trac.transmissionbt.com/wiki/HeadlessUsage/NSLU2

[bushbrother]

Has anyone tried the patch here : http://trac.transmissionbt.com/ticket/2858 ?

[bassie112]

Hi,

I have exactly the same problem. This is my first try with Linux/NSLU2/Transmission/Optware... and I think it went ok. I setup Transmission 1.93 and the corresponding config file to my needs. However when I try to download a random torrent it downloads for a few seconds at good speed (>1.5MB/s) up to around 5% and then the progress goes backwards to almost 0 together with the download speed.

I tried to change some lines in settings.json with no success:
rename-partial-files: true/false
download-dir: dir on my USB HD (port 1) or on the USB-microSD (port 2) with the system-files
incomplete-dir-enabled: true/false
watch-dir-enabled: true/false
"preallocation: 0" is needed because with the "preallocation: 1" my NSLU2 freezes when downloading

I also tried to lower the speeds with no success.

Does anyone know what the problem is or how to fix it? I also don't know how to use the above mentioned patch or which file to edit on the NSLU2... so I can't give any feedback about that.


My Setup:
My NSLU2 (Unslung 6.10 Beta with a 2GB USB-microSD on port 2) perfectly shares my 1.5TB USB HD (port 1) over the network and I can telnet into the device to install packages. I can however not download any packages from http://ipkg.nslu2-linux.org/feeds/optwa ... ss/stable/ (server down?), so I used the ftp-mirror found on ftp://ftp.osuosl.org/pub/nslu2/feeds/op ... oss/stable to install all the asked-for packages separately.

[bassie112]

1.76 seems to work fine, except I cannot use the "incomplete directory" option and theoption to add ".part" to incomplete files (or at least they don't work for me). So probably I have to wait for a new version (>1.93) and maybe that one works...

[bassie112]

Version 2.00 still has the same problem for me. Anyone a fix? (blocklist, encryption, dht, peer exchange, local peer discovery, upnp don't seem to make any difference)

UPDATE:
I noticed that all the data I'm downloading is not valid. This is independant for tracker, file, size, download speed etc..

For example: I downloaded 100MB of a 1GB file (10% done) and 0 bytes are valid. The respons to this is that the 10% progress is deleted as the data is not registered as valid and therefore the progress drops back to 0%! After this the whole process repeats itself. This always happens within a minute or so (probably the time needed to check the data). Looks like the same problem frosty is having...

So my question is: does anyone know what has been changed since version 1.76, which works excellent in terms of downloading, in comparison to newer builds? Were there no hash-checks before, or are any changes made to the hash-check?

[ruchir70]

I am using the latest build of Transmission2.01 for Optware. And I face the same problem where the downloaded pieces are failing the checksum. Is there no way to disable checking of checksum for Transmission?

[Rolcol]

I am using the latest build of Transmission2.01 for Optware. And I face the same problem where the downloaded pieces are failing the checksum. Is there no way to disable checking of checksum for Transmission?

Why would you want to disable the checking of data? The reason it's being rejected means that the data you're getting is BAD. Sounds like someone is poisoning your swarm. i.e. There is a computer or intentionally bad person that messed with the contents of the torrent and is sending it to everyone in an attempt to make your download fail.

[bassie112]

I am using the latest build of Transmission2.01 for Optware. And I face the same problem where the downloaded pieces are failing the checksum. Is there no way to disable checking of checksum for Transmission?

Why would you want to disable the checking of data? The reason it's being rejected means that the data you're getting is BAD. Sounds like someone is poisoning your swarm. i.e. There is a computer or intentionally bad person that messed with the contents of the torrent and is sending it to everyone in an attempt to make your download fail.

Well, since version >1.76 it happens for all downloads. So I don't think the problem is that someone is poisoning the swarm. 1.76 is working flawlessly, but this version misses some nice features like the watch-dir, move when complete, deleting torrent-files, and rename partially completed files. Ofcourse shutting off the hash-check is not the way of solving the problem. But something must have changed since the latest stable build, which is 1.76 for many of us. I tried to fiddle around with the options but nothing seems to work, so my best guess is a failing hash-check, but why...

[bassie112]

2.03 same problem...

[bassie112]

2.04 the same

[bushbrother]

Same issue for me since 1.76 on my QNAP TS-201 ... discussion with developer here https://trac.transmissionbt.com/ticket/2858

[bassie112]

Just to let ya all know, the new version 2.10 downloads ok and appears to download correct data. Although after completion the data is not! Also rechecking of data shows that no data is correct, however it is correct because it was downloaded with 1.76!

Strange... but I have the idea a working version is getting closer.

[buggsy2]

Similar or same problem with 2.11. I hadn't upgraded my Unslung for a long time and found this problem. No news?
Edit: I read through the long but informative bug tracking thread...is the consensus still that it's a packaging issue? Anyway I'm willing to go back to 1.76 but I don't know how, can someone advise?

[bassie112]

Similar or same problem with 2.11. I hadn't upgraded my Unslung for a long time and found this problem. No news?
Edit: I read through the long but informative bug tracking thread...is the consensus still that it's a packaging issue? Anyway I'm willing to go back to 1.76 but I don't know how, can someone advise?

Just use "ipkg remove transmission" in telnet and install the 1.76 package by placing the package in the root and using "ipkg install 'file'". Do not use ipkg upgrade or it will update to 2.11 again.