A noob question: Now I installed 1.50. I wanted to enter it by web interface and got the message that my browser does not support this. I use internet explorer. I could not find this info in this forum thread so am I doing something wrong?
If not, there's no use for me of using this so is there a simple way of deleting only this transmission install or do I have to reainstall the complete firmware/nmt programms as mentioned?
My other question is, the ip adres:8883/torrent/bt.cgi is still available. I suppose this means I now have two torrent clients on my NMT, is that two different versions of the same client? Can I uninstall the other one or just delete the .btpd dir (hidden)?
Last question: can I delete the hidden transmission.nmt directory as the content seems to be the same as the unhidden one?
I also have the same request. I searched the forum and I can't find an easy way to do this. I'm a complete noob, how can I do it?
Thanks!!!
(02-19-2009 09:27 AM)kamuranmulayim Wrote: [ -> ]Helle I am using Transmission 1.50 and downloading to internal HD. Some torrent files downloaded are in .rar format. What is the easy and quick way to unrar does files in to same HD. I tried to run winrar in my laptop it works but takes a long time. Is there an easy way to this internally (PCH)
(02-19-2009 09:27 AM)kamuranmulayim Wrote: [ -> ]Helle I am using Transmission 1.50 and downloading to internal HD. Some torrent files downloaded are in .rar format. What is the easy and quick way to unrar does files in to same HD. I tried to run winrar in my laptop it works but takes a long time. Is there an easy way to this internally (PCH)
1. You need to install telnetd on PCH
2. Telnet into PCH
3 Navigate to the folder where your RAR file(s) are
4. run the following command
\mnt\syb8634\unrar x *.rar
hey all.
I am running Transmission 1.50 on my PCH A110, and for the most part it works pretty well, however I've noticed that if I am downloading from lots of very fast peers, the web interface becomes completely unresponsive.
when logged into the PCH via telnet, I can see the download is still progressing, and my shell is still reasonably snappy.
when this happens, the transmission-daemon process uses quite a bit of CPU, fluctuating between 10% to 35%. when the torrent has finished downloading, the web interface is responsive again as it should be.
in settings.json I tried setting max-peers-global: 20 and max-peers-per-torrent: 4 but after restarting Transmission and hitting the web interface (before it died), it said "Downloading from 15 of 17 peers", so I don't know if those options are being honoured.
downloading from a larger number of slower peers doesn't seem to trigger this issue, only fast peers.
I'm at a loss to explain why this is happening. has anyone else come across this before, or have any other ideas?
grant.
edit: I should add that by downloading from "fast peers" I mean peers that can easily flood my internet connection, which is not particularly fast (1.5mbps).
(02-16-2009 11:18 PM)Ger Teunis Wrote: [ -> ]Hi bhaviksoni, welcome to the NMT community!
That is a required step for it to install correctly.
I think the best way for you get going the fastest is installing the Community Software Installer. That will allow you to install this transmission client with just a few mouse click!
http://www.networkedmediatank.com/showth...?tid=13161
Ger, have you been able to build this "quick fix" version of Transmission that could fix the CPU usage issue ?
http://trac.transmissionbt.com/ticket/1829
That quickfix isn't a fix.
A quote here "Oops, spoke too soon there. After a couple of hours running I'm back up to a fairly constant 95-100% CPU with odd dips to ~20%. Memory usage seems to creep up over time and d/l speeds seem to drop off. Anything I can do to help? Dave"
I am willing to patch the current 1.50 with that fix with no stripping though so somebody can use gdb on it.
Nice to see that charles is picking up this issue!
.
For anyone interested: the trunk build revision 7929 is available for download
http://members.tele2.nl/ger.teunis/downl...nk-nmt.zip
(non stripped; 5mb)
(02-20-2009 06:02 AM)grb Wrote: [ -> ]hey all.
I am running Transmission 1.50 on my PCH A110, and for the most part it works pretty well, however I've noticed that if I am downloading from lots of very fast peers, the web interface becomes completely unresponsive.
when logged into the PCH via telnet, I can see the download is still progressing, and my shell is still reasonably snappy.
when this happens, the transmission-daemon process uses quite a bit of CPU, fluctuating between 10% to 35%. when the torrent has finished downloading, the web interface is responsive again as it should be.
in settings.json I tried setting max-peers-global: 20 and max-peers-per-torrent: 4 but after restarting Transmission and hitting the web interface (before it died), it said "Downloading from 15 of 17 peers", so I don't know if those options are being honoured.
downloading from a larger number of slower peers doesn't seem to trigger this issue, only fast peers.
I'm at a loss to explain why this is happening. has anyone else come across this before, or have any other ideas?
grant.
edit: I should add that by downloading from "fast peers" I mean peers that can easily flood my internet connection, which is not particularly fast (1.5mbps).
I get the same as this, although my CPU usuage is 90-95%. When download speed is >500Kbs it crashes my PCH after about 2-3 mins. v1.42 never caused it to crash.
Same CPU issue here - 95% usage most of the time (although it's sometimes transmission-da using all that, and sometimes php is using half). The web UI is totally unresponsive when it's like this, and the unit is unusable (long delays when browsing files through my TV and watching movies is impossible whilst downloads are running). When downloading/uploading, I'm also getting a lot of constant noise from the hard drive - normally it's a little trickle now and then, but it's constantly churning now.
My current routine for watching a film is:
Telnet to popcorn
Reboot
I then have a couple of minutes before the CPU usage ramps up - I log into the Web UI and pause my downloads.
I can then watch a movie
I then resume the downloads again afterwards
On the positive side, my download speed has increased dramatically with this release - 300k+ instead of the usual 60-70k.
I'm looking forward to getting a patch for this CPU usage issue though.
darren
Okay guys. We got some attention from the transmission developers.
Regarding the load: please limit the download speed for the time being.
A crashing NMT is serious because not transmission is the root cause but the high cpu load is. This can mean that the cpu is getting way to hot and causes the nmt to become unstable.
I have come across the same issue. Nothing bad about transmission because i am generally really pleased with this app.
Ger, are you sure that limiting the dl speed will prevent it from using so much cpu?
I've had a similar performance issue on my PC, which i fixed by limiting the number of concurrent connections
HI,
Like subbase i'd like to know if is still possible to have access to the "light" webui from the network. Unfortunately the "standard" one is not viewable in my blackberry. One of the things I appreciate most from the transmission client that comes with the latest version of the nmt firmware was that both webui where accesible form the network.
(02-20-2009 05:53 PM)Ger Teunis Wrote: [ -> ]Okay guys. We got some attention from the transmission developers.
Regarding the load: please limit the download speed for the time being.
A crashing NMT is serious because not transmission is the root cause but the high cpu load is. This can mean that the cpu is getting way to hot and causes the nmt to become unstable.
limiting the download speed makes no difference for me. it "feels" like a problem with the number of very fast peers, but the configuration options to limit the number of peers don't seem to work...
I never tried this with 1.42 (didn't realise it was there by default until after I'd installed 1.50, actually).. I'll see how the trunk build goes first.
(02-21-2009 12:36 PM)grb Wrote: [ -> ]limiting the download speed makes no difference for me. it "feels" like a problem with the number of very fast peers, but the configuration options to limit the number of peers don't seem to work...
I never tried this with 1.42 (didn't realise it was there by default until after I'd installed 1.50, actually).. I'll see how the trunk build goes first.
same problem with trunk rev 7929.
I went back to 1.42 and it works perfectly, so there must be some regression between 1.42 and 1.50.
Does the new version of transmission work with the new firmware's gaya torrent interface? The standard 1.22 install can be handled by the web services 'torrent' entry or via pc on port 8883 - basically an exact replacement for btpd...but after installing 1.50 the NMT shows the service as stopped, or 'starting'. if I play around I can get it to the stage where it thinks it is running, but browsing to the web interface on 8883 shows the 'bittorrent is not running' message - presumably the stop/start detection is based around 1.22?
(02-21-2009 09:43 AM)jolveira Wrote: [ -> ]Like subbase i'd like to know if is still possible to have access to the "light" webui from the network. Unfortunately the "standard" one is not viewable in my blackberry. One of the things I appreciate most from the transmission client that comes with the latest version of the nmt firmware was that both webui where accesible form the network.
(02-22-2009 10:34 AM)Squeek Wrote: [ -> ]Does the new version of transmission work with the new firmware's gaya torrent interface? The standard 1.22 install can be handled by the web services 'torrent' entry or via pc on port 8883 - basically an exact replacement for btpd...but after installing 1.50 the NMT shows the service as stopped, or 'starting'. if I play around I can get it to the stage where it thinks it is running, but browsing to the web interface on 8883 shows the 'bittorrent is not running' message - presumably the stop/start detection is based around 1.22?
They have modified the 'blue' webinterface and the gaya (on popcorn) interface to connect to transmission 1.22. After version 1.22 a lot (and I mean a lot!) has changed, using those interfaces is not an option on the 1.50 version. You will have to do with the current gaya interface (via webservices) and the standard transmission webui.