Transmission 1.80 headless going backwards

[ethanheadlongjr]

I'm running transmission 1.8 headless on a NSLU2 through unslung 6.2

Torrents will add and begin to download but seem to go backwards at random intervals, never getting above 5%.

It's incredibly frustrating, is there a fix or a configuration setting that I'm missing?

[ethanheadlongjr]

Also, I'm not uploading despite there being no speed limits set.

[short2ground]

Same deal here. Running unslung 6.10 and tried 6.08, same result. Currently unslung to 4gb sdhc card via usb adapter.

[ethanheadlongjr]

No offence but that's not particularly helpful, the current optware package is 1.8, 1.83 isn't available through optware and there is no way to roll it back to 1.73 that I can see.

I'm not good enough with Linux to build and install 1.73 from source, especially when you factor in all the tweaks necessary to get it working on an unslung NSLU2.

Is there a way to roll back to 1.73 using ipkg?

[ethanheadlongjr]

Sorted, I managed to build and install 1.83 with a little help from the walkthrough here:

http://mybookworld.wikidot.com/forum/t- ... pendancies

There's still no uploading happening, but at least the downloads are running.

[short2ground]

Got mine built and installed also. Uploads ok. Using transmission 1.83, unslung 6.10 to usb hard drive.

[short2ground]

Antbingley, I had the same errors you are having. it seemed that the command "export PKG_CONFIG_PATH=/opt/lib/pkgconfig" was not taking at all. Funny, when I logged out of telnet and started using ssh (putty from an xp laptop) I entered that command, then the configure string, and it just took off! Go figure...

Good luck

oh yeah...I ignored the libiconv error, too

[antbingley]

Finally got it sorted, thanks. I switched to using Putty which got me further, but still got the "no acceptable C compiler in the PATH". After a bit of digging on the 'net, turns out I needed to install crosstool-native and that did the trick.

So big thanks to short2ground, I'm up and running again!

[short2ground]

Big thanks to x190. The whole "teach a man to fish" thing. Now I'm gonna sit in a boat and drink beer all day.

[bushbrother]

I have the same issue but on a QNAP TS-201 NAS. I upgraded from 1.76 to 1.80 and now my torrents get to about 1% then "go backwards" to like 0.2% then up and down, like it cannot save the first chunk. No errors I can see

I compiled the 1.83 tarball and that version does the same, in the end I had to compile 1.76 and go back. Now all is working ok.

Is it something to do with these new ".part" files? Any help appreciated ...

[frosty]

I upgraded from 1.76 to 1.80 and now my torrents get to about 1% then "go backwards" to like 0.2% then up and down, like it cannot save the first chunk. No errors I can see

I also started to experience difficulties after upgrading to 1.80.. I still have to find the time to compile a new packages (or the old one for that matter..).
However, since the 1.80 finally gives an error output to the messages file in /var/log you can at least see what's wrong...the downloaded parts evidently never pass the hash check. You can also see this output in the transmission remote gui error field (at least in my case). For every MB that has been downloaded, the same amount is failing the hash check. It seems that the 0.8 percent, or 0.2 % or whatever is actually the amount of data that is being downloaded the second BEFORE it gets to the hash check - which it fails... that's why it never peaks over 2-3 mb...

I personally don't think it has something to do with the .part files, i mean, they're just being renamed, that's all...nothing changes the way transmission handles them..they've been there before, just didn't have the .part bit attached to them.

And yeah, I have also been amazed by x190s ability to NOT be useful whatsoever....

[bushbrother]

Seems you looked a little deeper than me Unfortunately whatever has changed to cause these hash check fails is still the same in 1.83 ... do we now post this as a bug?

[nicob]

Seems you looked a little deeper than me Unfortunately whatever has changed to cause these hash check fails is still the same in 1.83 ... do we now post this as a bug?

I also have this problem... I asked one of the optware developers to update it to 1.83, and they did, yesterday.... But It does not seem resolve the upload or going backwards in size bug.

It might be a good idea to create a ticket on trac. Because it does not seem to fit the profile of Transmission crashes randomly on ARM-based Synology NAS ticket

[bushbrother]

Ticket added ... http://trac.transmissionbt.com/ticket/2858

[frosty]

I also have this problem... I asked one of the optware developers to update it to 1.83, and they did, yesterday.... But It does not seem resolve the upload or going backwards in size bug.

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