I have a problem with transmission web gui stopping to respond and not opening in browser after few hours since I starting transmission.
I got MBWE. Anyone else had this problem or anyone with suggestions?
It happened just once to me. Just restarted it to fix. Apart from that episode, it is running fine.
Hi!
+1, same for me… :-(
Does the optware have an option where to download the *.ipk files before install it? I think we should turn this "feature" on to make a local archive repository of optware packages…
As the logs shows, I installed the transmission_1.91-1_arm.ipk package @ 25th Febr, but unfortunately I don't have the source ipk file…
Thanks and BR
Belabacsi
Budapest, Hungary
Also my Transmission 1.92 crash.
I need of transmission_1.91-1_arm.ipk for downgrade
Someone give me the link?
Thanks
Same happens to me, but only when it's downloading, and if it is downloading fast (500+kb/s) it happens quicker (less than ½ hour), and if I download slower (less than 100kb/s) it dosen't happen until a couple of hours have passed.
I'd like to know why this happens and if there is a solution to this.
Thanks.
I think there is a bug in 1.92 relase.
I want downgrade to 1.91 relase (stable for me) but dont'have transmission_1.91-1_arm.ipk file
Someone give me the link?
Thanks
Now I ended up to a situation where the web gui doesn't respond even if I just started transmission, seems that the process hangs right after I start it.
I have a similar problem. Transmission fires up and Web GUI takes a little while to respond, I add a download and after a little while it fails to respond. Restart brings it back to life, but only for a little while. Any fixes yet?
Cheers!
M
Hi everyone.
Is this related to how many torrents you have in the WATCH folder? Can any of you clean out your torrent files and start transmission? I'm curious if it will work better this way. I upgraded too but didn't have this problem YET. However, I have a rule that I only load maximum of 2 torrent files at any time on the NAS. So maybe the NAS just runs out of RAM when loading and checking the torrent files on startup? Also there are things you can do to set limits via the config file. Have any of you tried editing this file to slow down the transfers?
First, before messing with this, go ahead and make a backup the transmission config file:
#cp .config/transmission-daemon/settings.json .config/transmission-daemon/settings.json.bkup
Now, let's stop transmission:
#/etc/init.d/S91transmission stop
Now, it's time to edit!
#vi .config/transmission-daemon/settings.json
For an example, here is my config file. If you decide to make any changes to yours, BACK IT UP FIRST.
{
"alt-speed-down": 50,
"alt-speed-enabled": true,
"alt-speed-time-begin": 570,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": true,
"alt-speed-time-end": 1095,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": false,
"dht-enabled": true,
"download-dir": "\/shares\/internal\/PUBLIC",
"download-limit": 250,
"download-limit-enabled": 1,
"encryption": 1,
"incomplete-dir": "\/root\/.config\/transmission-daemon\/Incomplete",
"incomplete-dir-enabled": false,
"lazy-bitfield-enabled": true,
"max-peers-global": 100,
"message-level": 2,
"open-file-limit": 32,
"peer-limit-global": 240,
"peer-limit-per-torrent": 40,
"peer-port": 51413,
"peer-port-random-high": 65535,
"peer-port-random-low": 49152,
"peer-port-random-on-start": false,
"peer-socket-tos": 0,
"pex-enabled": true,
"port-forwarding-enabled": false,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2.0000,
"ratio-limit-enabled": false,
"rename-partial-files": true,
"rpc-access-control-list": "127.0.0.1,172.17.1.*",
"rpc-authentication-required": false,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{9fc8782ab9a88c38b43bcc55597e0528a4fcf24c43E9Y93E",
"rpc-port": 9091,
"rpc-username": "",
"rpc-whitelist": "127.0.0.1 172.17.1.*",
"rpc-whitelist-enabled": true,
"speed-limit-down": 150,
"speed-limit-down-enabled": true,
"speed-limit-up": 75,
"speed-limit-up-enabled": true,
"umask": 18,
"upload-limit": 100,
"upload-limit-enabled": 1,
"upload-slots-per-torrent": 14
}
Here is the line from above where you can customize for the location of the torrent files:
"download-dir": "\/shares\/internal\/PUBLIC",
Here is the line that is used to allow YOUR local network. The fist IP stays, and the second IP needs the first three octets filled with numbers from your network. I put the most common one in already for you:
"rpc-whitelist": "127.0.0.1 192.168.1.*",
If you're having problems with transmission crashing, try reducing its resources. First start with the values I have here and then try lowering these numbers in small steps . The numbers for speed are in KB/s, and all numbers are in the config file above. You just need to find them and try changing the values. REMEMBER, MAKE A BACKUP FIRST!
"download-limit": 250,
"max-peers-global": 100,
"peer-limit-global": 240,
"peer-limit-per-torrent": 40,
"speed-limit-down": 150,
"speed-limit-up": 75,
Then restart transmission and see if it is better. Remember that this NAS is lean on resources, so if you took a 486 computer and opened 12 or 15 files and started to download them from 30 different places each, you'd lock up the computer. That's probably the same thing that's happening here.
#/etc/init.d/S91transmission start
Remember, you have a backup, so if things go terribly wrong, just move the backup back into place like this:
cp .config/transmission-daemon/settings.json.bkup .config/transmission-daemon/settings.json
Enjoy! I hope this helps you guys fix your transmission problems! :-)
tyrelPL
Thanks for the tips, I'll have a play. Was only ever downloading 1 torrent though when mine died :(
Cheers!
M
tyrelpl,
Thank you for the advices but -
1.91 worked without any special tuning and limits. With full speed. Never crashed on me.
1.92 with exactly the same settings dies. With only single torrent.
And this is not about web or remote GUI - GUI dies because Transmission freezes (disk activity stops).
But it does not die because the processes are still running but not eating any CPU power.
I noticed also that when starting 1.92 fires up 5 processes while there were only 4 in 1.91.
More resource "gready"?
1.91 package will cure us all. If someone has it - please please post it here. For White Light in my case.
Thanks in advance!
Valery
Hi Guys !
[root@NAS ~]# ipkg info transmission
Package: transmission
Version: 1.92-1
Depends: openssl, libcurl, libevent, zlib
Status: unknown ok not-installed
Section: net
Architecture: arm
maintainer: oleo@email.si
MD5Sum: a83d0e7f0bc5c89f0e482bf92f4e964c
Size: 809228
Filename: transmission_1.92-1_arm.ipk
Source: http://mirrors.m0k.org/transmission/files/transmission-1.92.tar.bz2
Description: Lightweight BitTorrent client and daemon, with web interface bundled.
Package: transmission
Version: 1.91-1
Depends: openssl, libcurl, libevent, zlib
Status: install user installed
Architecture: arm
Successfully terminated.
maintainer: oleo@email.si
So you could send a request to oleo@email.si ;-)
Or you could also use the package done by TeinturMan =>
[root@NAS ~]# wget -q http://highlevelbits.free.fr/download-MBWEW/TRv1.91-1/Transmission.tar
[root@NAS ~]# tar -tvf Transmission.tar
drwx------ root/root 0 2010-03-24 22:11 Transmission/
-rw------- root/root 1148 2010-03-16 21:07 Transmission/_uninstall
-rw------- root/root 853179 2009-11-25 23:26 Transmission/transmission_1.61_r8420-1_arm.ipk
-rw------- root/root 19 2010-03-24 22:11 Transmission/_info
-rw------- root/root 1967 2009-04-19 10:01 Transmission/_.jpg
-rw------- root/root 810734 2010-03-24 21:58 Transmission/transmission_1.91-1_arm.ipk
-rw------- root/root 1193 2009-04-17 18:07 Transmission/install.jpg
-rw------- root/root 10593 2010-03-16 21:07 Transmission/Configure.sh
-rwx--x--x root/root 408 2009-07-17 00:25 Transmission/TR-watchdog2
-rw------- root/root 1587 2009-11-25 23:48 Transmission/settings.json
-rw------- root/root 927 2009-04-19 01:22 Transmission/S90transmission
-rw------- root/root 4057 2010-03-24 22:10 Transmission/_install
-rwx------ root/root 42756 2009-04-18 21:53 Transmission/cut
-rwx------ root/root 321 2010-03-16 21:04 Transmission/TR-watchdog
Thanks, JisSey.
I've reinstalled form TeinturMan package, sun is shining again! :)
Downgraded to 1.91 also. Seems to be ok now.
Also mw 1.91 work perfectly!!!
(I think that the 1.92 ipk have a bug).
This must be a white light / Transmission 1.92 bug. I have been running 1.92 on my blue rings for a week 24hrs/day with no problems at all. no crashes, nothing. I have been d/l'ing 150GB.
MyBookLive Duo 4T
FeaturesPacks, Twonky, ownCloud
Same story for me. A few private trackers I was using started banning 1.91 so I upgraded to 1.92 and haven't had a single issue. In fact I think it behaves slightly nicer with the windows transmission gui. I'm using Blue ring 1.5TB
Those on the white rings having issues might be worth sending any relevant crash logs etc to the transmission team so they can fix things… I know there were changes regarding how the watch dir and inotify were working in transmission, so this would probably be a first spot to look… i.e maybe try disablying the watch dir and see if that has any impact.
Yeah one of my private trackers also banned 1.91, so I HAVE to use 1.92. But unfortunately I have a whitey, and it crashes after 10 seconds, so no seeding for me at the moment…
Anybody got an update on this?
Hi All!
I have a WD MyBook WhiteLight and same problem with Transmission v1.92…
Could anyone please tell me how to downgrade to v1.91? I successfully downloaded the above mentioned .tar file, but I don't know what is the next step.
Maybe optware package removing? And in this case, what about Transmission configuration files and current downloads?
Thanks in advance,
Belabacsi
Hello Belabacsi,
if you have installed the Feature pack manager,
You can simply install the feature pack v1.91
by removing the current Transmission feature pack ( click uninstall)
then copy/paste the following url in the System_Configuration/FeaturePAcks menu/Install Featurepack from url
http://highlevelbits.free.fr/download-MBWEW/TRv1.91-1/Transmission.tar
Regards,
You have to use ipkg option "-force-downgrade install<pkg>". Hope this will help you:
~ # wget http://highlevelbits.free.fr/download-MBWEW/TRv1.91-1/Transmission.tar
~ # tar -xvf Transmission.tar
~ # cd Transmission/
~/Transmission # ipkg -force-downgrade install transmission_1.91-1_arm.ipk
Downgrading transmission on root from 1.92-1 to 1.91-1...
Configuring transmission
Successfully terminated.
~/Transmission # ipkg info transmission
Package: transmission
Version: 1.92-1
Depends: openssl, libcurl, libevent, zlib
Status: unknown ok not-installed
Section: net
Architecture: arm
maintainer: oleo@email.si
MD5Sum: a83d0e7f0bc5c89f0e482bf92f4e964c
Size: 809228
Filename: transmission_1.92-1_arm.ipk
Source: http://mirrors.m0k.org/transmission/files/transmission-1.92.tar.bz2
Description: Lightweight BitTorrent client and daemon, with web interface bundled.
Package: transmission
Version: 1.91-1
Depends: openssl, libcurl, libevent, zlib
Status: install user installed
Architecture: arm
Installed-Time: 1270066500
Successfully terminated.
Dear TeinturMan and schilea!
Thanks for Your help, I have just successfully downgraded Transmission to v1.91 :-)
The currently active downloads and the Transmission options seem to be OK!
Regards,
Belabacsi
As I said before, Transmission 1.92 is working fine in my MBWE White Light. It may be useful for you to know that once it happened that the web UI wasn't responding, just like the RPC interface. I suspected Transmission had crashed, but logging into it with SSH and doing a ps revealed that it was still running, although with quite high CPU usage (80-90%, instead of 5-10% in normal usage). So I tried to let it there without doing anything (so, I didn't restart it, I left it working) and came back after some hours: all was working fine then! Web UI ok, RPC ok, downloading files was going on.
So, in that case it was just a "temporary" freeze. Maybe it's the same problem at least for some of you. When you say that it crashes, you mean it really crashes or that it just seems frozen?
I don't know what Transmission was doing when it didn't respond, however when it finished to do that, it went on doing the right thing :-)
Waiting doesn't help for me.. I can see the process running, but it doesn't respond (Been running like this for a few days now, nothing changed)… Sucks really bad.
After downgrading to 1.91 check with "ipkg info transmission" and then put package transmission to hold with "ipkg flag hold transmission".
In this way when you do update/upgrade transmission will be held to current version and will not be updated.
If you want to change the state of package transmission (in case of a newer with no bug version) do "ipkg flag user transmission" to set transmission in a flag that can be updated.
I had the same problem with 1.92, since the downgrade it's just working fine, thanks a lot guys!!!
