Transmission 1.31

[harrym]

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

WL-5x0gX are good routers, but only routers...

[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

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

[Silkmann]

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.

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?

[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

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

[andersos]

Since I started using rpc enabled versions I see "Connection failed" message quite often. Some times it shows directly after ui is loaded and before torrents are displayed, some times it shows after torrents are displayed and I can still do f.ex. resume or stop on torrents. This happens on local network. Seems to me that it must be a timeout problem.

1.34 is released btw.

[alxndrv]

andersos
It mostly happens when the bandwidth is used by torrent traffic, so I think too, it might be time-outs.
Do you know how to manage them in transmission rpc?

[andersos]

I don't think it's possible to affect timeouts through any settings. Would be best to discuss with the devs on irc. I didn't do it yet because I don't currently need the web ui myself. But I think I'll soon mention the problem there.

Btw., 1.34 seems to be very nice. Thanks oleo!

[alxndrv]

I recently have discovered one strange feature of new transmission: it downloads twice less than the old version. So, the time to download e.g. one 700MB movie dropped from appr. 4 hours with old transmission downto 7-8 hours with new version (with my 512Kbit dsl). Does anyone have the same problem?
P.S. I don't have download limitations set in transmission configuration. It reports appr. 52KB/s download speed, so it must download 52*3600*4>700MB in 4 hours but in reality it downloads only appr. 400MB!

[wpte]

still the weird problems I guess...
don't know why everybody has problems, it works perfectly fine for me
for downloading 700mb movies, it now only takes half an hour for me, instead of a whole day
alltho it connects to a lot less peers, I download a lot quicker

[ocelivise]

I recently have discovered one strange feature of new transmission: it downloads twice less than the old version. So, the time to download e.g. one 700MB movie dropped from appr. 4 hours with old transmission downto 7-8 hours with new version (with my 512Kbit dsl). Does anyone have the same problem?
P.S. I don't have download limitations set in transmission configuration. It reports appr. 52KB/s download speed, so it must download 52*3600*4>700MB in 4 hours but in reality it downloads only appr. 400MB!

Yes!!! I have same problem, I even reinstalled everything today and problem is still there.
It's showing ~90 kb/s speed,but speed recorded on tracker is ~35kb/s
It simply uses 90kb/s of my bandwidth but effectively donwloading at 2x,3x less!!!!
Downloaded amount in the inspector is also weird, sometimes it is going backwards. It shows 55.3Mb and few seconds later it is showing 55.2MB

I think that that problem started when I upgraded from 1.33 to 1.34

[andersos]

andersos
It mostly happens when the bandwidth is used by torrent traffic, so I think too, it might be time-outs.
Do you know how to manage them in transmission rpc?

It seems that after they changed to using evhttpd yesterday Clutch works well again No more errors for me at least. I now run trunk revision 6804.

[jrosado]

I've been running 1.33-2 for about 30 days without a single hiccup

Best transmission i ever seen running on my asus

[Kenny]

I'm encoutering a problem with the WebUI: it keeps telling me

Connection Failed
Could not connect to the server. You may need to reload the page to reconnect.

and i cannot manage my torrents.
Running transmission 1.34

[wpte]

I'm encoutering a problem with the WebUI: it keeps telling me
and i cannot manage my torrents.
Running transmission 1.34

what browser do you use, and how do you connect?
wireless, via wan, via lan