DSM-G600, DNS-3xx and NSA-220 Hack Forum

Hm.
What exactly happens when you try to acess the web interface? Does it timeout? Nothing comes up? Do you get an error?

Did you change the RPC port? The integrated web server uses the same port, so you have to specify it in the browser as well.
Also, try accessing the site using the tool wget, a command-line web crawler. If that works, the problem is somewhere on your network (maybe a firewall?).

KyleK
Planning a release Transmission 1.76 ?

revert wrote:

It just says loading, I'm using google chrome after about 2 minutes it downloads an unknown file type.

this is what i get when i try wget
root@dlink-12735B:~# wget http://192.168.1.5:9091/transmission/web/
Connecting to 192.168.1.5:9091 (192.168.1.5:9091)
wget: no response from server

Try 127.0.0.1, or "localhost" as server IP (that is when you execute wget directly on the NAS, via SSH/Telnet).

Also in the SSH/Telnet shell, type "netstat -ltp | grep trans". Two ports should show up, 9091 for the RPC interface, and another for the actual bittorrent connection.



Do you use the startup script (/ffp/start/transmission.sh) to start and stop Transmission?

this is what i get when i run netstat


root@dlink-12735B:~# netstat -ltp | grep trans
tcp        0      0 0.0.0.0:9091            0.0.0.0:*               LISTEN      30072/transmission-


and yea, i use the start-up script...

i just re-installed again using 1.76...same thing.

root@dlink-12735B:~# netstat -ltp | grep trans
tcp        0      0 0.0.0.0:9091            0.0.0.0:*               LISTEN      28342/transmission-

arghhh

Anyone have issues where transmission web front end will take a long time to load/doesn't load. I've had this happen twice already and I've had to restart the service through ssh.... it's kinda annoying..

Tnx for compiling the latest version of transmission.

I've tried it some months ago, but I returned to mldonkey for the lack of http proxy support, is now included this function? Or only socks support?

Hi Kylek!

I've been using dsn 323 for 2 months now but onl for keeping files.  I had installed the transmission by following this thread with no error encountered (nothing I noticed).  When I added torrents in Transmission Web Interface it doesn't start.  It successfully download using Vuze.  Please help me in making this work. I have checked other sites to no avail.  THanks.

mushisushi wrote:

obveron wrote:

yup, its usually because the CPU is pegged at 98-100%.  next time it happens, go into ssh, type "top" (no quotes), you'll see your CPU usage.
not sure what's causing it, i know it didn't happen to me with old versions.  it doesn't appear to affect most other platforms, so developers are less concerned.

Thanks obveron, I'll definitely take a look tonight to see if that's what's happening. I wonder if the dev team knows about this issue.....

Update: Yup... transmission is pegged at 100%.. it drops to ~80% once in a while, but jumps right back...

The reason for this is the current implementation of peer management. It's not optimized at all, which causes performance problems on embedded devices such as our NAS.
This happens mostly with torrrents with a very large number of peers and seeds.
To contain it somewhat, I suggest turning off DHT and PEX for the time being.
Also keep the number of torrents to a reasonable amount (I'd say 4-5) at any given time. Performance should be acceptable then.

Other than that, you can't really do much but wait :(

rootsntips wrote:

Hi Kylek!

I've been using dsn 323 for 2 months now but onl for keeping files.  I had installed the transmission by following this thread with no error encountered (nothing I noticed).  When I added torrents in Transmission Web Interface it doesn't start.  It successfully download using Vuze.  Please help me in making this work. I have checked other sites to no avail.  THanks.

That isn't nearly enough information to know what's going on.
What version of Transmission do you use?
If you start Transmission with the startup script(/ffp/start/transmission.sh), there will be a logfile at /mnt/HD_a2/.transmission-daemon/transmission-daemon.log. What does it say?

Check the Transmission status with:

$ transmission-remote -l

Any torrent which encountered an error has a '*' on the left side next to its ID. You can get a detailed report via:

$ transmission-remote -t <ID> -i

Replace <ID> with the number of the torrent.

Well, there can be multiple reasons.
1. The port isn't properly opened, i.e. your firewall (or your router) blocks incoming connections. You can use this site, to find out: http://www.seemyport.com/
2. Try a well-seeded torrent, like an Ubuntu ISO or OpenOffice. Both companies offer torrent downloads from their website. These files are my usual test to see if the network is properly configured. They should max out your line. If not, something's wrong (see 1.)
3. 10.000 peers is a lot of data, and Transmission might have a problem handling those. I suggest turning off DHT and PEX for the time being, see if speeds improve. Transmission also might choke on the incredibly large sizes of your torrents (the first and the last, at least).
4. uTorrent just might be the better client Transmission doesn't do caching, its peer-selection algorithm might not be as optimized, etc.

I wanted to suggest an Ubuntu ISO from here, but I see you already have that in your queue.
Transmission doesn't get a response from the tracker, neither for an announce nor for a scrape. That's why nothings coming in: Transmission doesn't know any other peers that have the same data.
This is somewhat strange, because announce and scrape happen via HTTP protocol on port 80, which should be open.
Can you access any web site at all?
Try pinging one, or downloading something from a website:

$ ping mininova.org
$ wget http://releases.ubuntu.com/9.10/ubuntu-9.10-alternate-i386.iso.torrent

If these give an error, there is your problem.

If not, first update your Transmission to 1.76.
Also, make sure you have a recent version of libcurl installed (a link is in the first post of this thread).
If the problem now still persists, I'll need some more logs. Use these commands:

$ export TR_CURL_VERBOSE=1
$ transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon 2>&1 | tee transmission.log

Let it run for a minute or so, then press Ctrl-C to shut down Transmission.
There should now be a transmission.log. Please send that to me (best via private message here on the forums).

Maybe then I can figure out what is going on.