Downgrading from Transmission 1.41b 3

Summary:

Optware installation

Downgrading from Transmission 1.41b 3

gjgjgj 15 Dec 2008 20:10

Can anyone tell me the procedure of downgrading my Transmission installation 1.41b3 to version 1.40 using optware.

I recently updated my list of packages using the command "ipkg update" and then installed transmission using the command

ipkg install transmission.

Is there any way to go back to version 1.40.

Thanks in advance,
Seeker

Re: Downgrading from Transmission 1.41b 3

alephsmith 15 Dec 2008 23:10

In order to downgrade, you will need to get the ipkg for 1.40. If I remember correctly Optware doesn't keep archives of old builds.

Hopefully someone here has kept a copy of the old version they may be able to share with you.

Re: Downgrading from Transmission 1.41b 3

DarkWan 18 Dec 2008 22:42

Yes, it is the only way if you don't want to recompile.
Please, tell us why you need to downgrade: after ipkg update I start receiving 401: Unauthorized IP Address error message.
With non changes in confog file, different conditions blocked me to access. If someone else is in the same situation, I resolved with
explicit IP authorization

# cat /.config/transmission-daemon/settings.json
{
    "blocklist-enabled": 0, 
    "download-dir": "\/shares\/internal\/PUBLIC\/torrent\/", 
    "download-limit": 10, 
    "download-limit-enabled": 0, 
    "encryption": 1, 
    "max-peers-global": 200, 
    "peer-port": 51413, 
    "pex-enabled": 1, 
    "port-forwarding-enabled": 1, 
    "rpc-access-control-list": "127.0.0.*,192.168.1.*", 
    "rpc-authentication-required": 0, 
    "rpc-enabled": 1, 
    "rpc-password": "", 
    "rpc-port": 9091, 
    "rpc-username": "", 
    "rpc-whitelist": "127.0.0.1,192.168.1.*", 
    "upload-limit": 10, 
    "upload-limit-enabled": 1
}

Re: Downgrading from Transmission 1.41b 3

bzhou 16 Dec 2008 06:09

Could you try the suggestion on http://trac.transmissionbt.com/wiki/HeadlessUsageNsluTwo#LibeventIssuesonSpecificSystems ?
Run it like "EVENT_NOEPOLL=1 transmission-daemon"
See also http://forum.qnap.com/viewtopic.php?f=16&t=10016&start=0&st=0&sk=t&sd=a

Last edited on 16 Dec 2008 15:56 by bzhou Show more

Re: Downgrading from Transmission 1.41b 3

emmebiITA 20 Dec 2008 19:33

myboxproject.net installs V1.34 (the only one I saved :)

Re: Downgrading from Transmission 1.41b 3

Yoda83 20 Dec 2008 19:09

Hello,
I experiment the same problem as everyone here. (Unauthorized IP adress when I try to connect on the Web GUI).
I have tested the bzhou's solution with no changes.

Anyone found a solution ? (maybe the Optware archive of Transmission 1.40 ? )

Thanks.

Re: Downgrading from Transmission 1.41b 3

bzhou 21 Dec 2008 02:06

Looks like the transmission-daemon by default only allow 127.0.0.1 (localhost) to connect to Web UI. There's a parameter

-a --allowed      <list>      Allowed IP addresses.  (Default: 127.0.0.1)

So you can use that. Don't know the exact syntax for subnet, don't know whether this can be configured somewhere.

Re: Downgrading from Transmission 1.41b 3

alephsmith 21 Dec 2008 06:26

DarWan's advice worked for me. It is configured in settings.json add the following keys:

"rpc-access-control-list": "127.0.0.*,192.168.1.*",
"rpc-whitelist": "127.0.0.1,192.168.1.*",

adjust for your network

Re: Downgrading from Transmission 1.41b 3

Mikee21 21 Dec 2008 19:14

This works, thanx

Re: Downgrading from Transmission 1.41b 3

teros 24 Dec 2008 05:54

i get the same issues as above but whenever i change my settings.json under /.config/transmission-daemon/settings.json whenever i change the "rpc-whitelist" field changes back to 127.0.0.1 any ideas how to correct?

cat /root/.config/transmission-daemon/settings.json
{
"blocklist-enabled": 0,
"download-dir": "\/shares\/internal\/PUBLIC\/Downloads",
"download-limit": 100,
"download-limit-enabled": 0,
"encryption": 1,
"max-peers-global": 200,
"peer-port": 51413,
"pex-enabled": 1,
"port-forwarding-enabled": 0,
"rpc-access-control-list": "127.0.0.*,192.168.0.*",
"rpc-authentication-required": 0,
"rpc-password": "",
"rpc-port": 9091,
"rpc-username": "",
"rpc-whitelist": "127.0.0.1",
"upload-limit": 15,
"upload-limit-enabled": 1
}
[root@Teros transmission-daem

Re: Downgrading from Transmission 1.41b 3

gaabika 28 Dec 2008 22:31

Hi,
This happened with me too. I realized that the problem was that transmission-daemon was running when I edited the config file. Not sure if that's the problem, but it's worth a try.

Oh, by the way I made a mistake… upgraded to 1.42. Since it's not a beta release, I thought there shouldn't be any new bugs in it, but actually there is one big in it: it keeps CPU usage above 80-90% constantly, with only a few torrents running. If anyone could help out with an earlier optware version -even betas, 1.41b4 was working pretty good for me - I would really appreciate it. Thanks in advance!

Last edited on 28 Dec 2008 22:36 by gaabika Show more

Re: Downgrading from Transmission 1.41b 3

khantpr 01 Jan 2009 03:51

I just upgraded to version 1.42 and CPU usage is about 80-90% constantly with only 1 torrent running. I would also want to downgrade to earlier version. Let me know if there is a way to downgrade without going through lot of trouble.

Re: Downgrading from Transmission 1.41b 3

gaabika 01 Jan 2009 15:49

Downgrading is as easy as installing a new version, the only problem is that the .ipk file of the earlier version is needed.
Please, did anyone save this file from an earlier version?
If there won't be a new (beta) release of transmission soon, I'll have to look for another torrent client :S The high CPU usage renders the MB barely usable :(

Re: Downgrading from Transmission 1.41b 3

JuStAdsor 31 Dec 2008 02:25

Don't need to downgrade.
Adjust your transmission startup script like this:

/opt/bin/transmission-daemon -a *.*.*.* —auth -u username -v password -w yourdownloadingdir