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

I have some small problem to get started (Have NSA-220 plus). I think I've installed the program corectly, and when I use my Windows-computer to open the web/index.html I can see the torrent-client in the web-browser, but it says: "Could not connect to the server. You may need to reload the page to reconnect."

I browsed me into the ffp/bin folder and wrote:
su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u <username> -v <password> -a 127.0.0.1,192.168.*.*" (where I wrote root instead of "<username>" and "<password>". Nothing happened.

Then I did what you said earlier, and wrote: ls -alh
I got this:

lrwxrwxrwx    1 root     root            7 Apr  6 12:47 tr -> busybox
lrwxrwxrwx    1 root     root            7 Apr  6 12:47 traceroute -> busybox
-rwxr-xr-x    1 root     root       426.0k Mar 15 19:36 transmission-daemon
-rwxr-xr-x    1 root     root       451.1k Mar 15 19:36 transmission-remote
-rwxr-xr-x    1 root     root       418.6k Apr 15  2008 troff
lrwxrwxrwx    1 root     root            7 Apr  6 12:47 true -> busybox

I guess this means that the owner of the folder is root, not nobody?
Therefore I tried to write "root" in stead of nobody:

su root -c "transmission-daemon -f -g /mnt/HD_a2/.tran
smission-daemon -t -u root -v root -a 127.0.0.1,192.168.*.*"

Now I think the program started. Here is what it wrote:

[12:28:29.342] Transmission 1.92 (10386) started (session.c:616)
[12:28:29.343] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:772)
[12:28:29.343] RPC Server Adding address to whitelist: 192.168.*.* (rpc-server.c:772)
[12:28:29.343] RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:945)
[12:28:29.344] RPC Server Whitelist enabled (rpc-server.c:949)
[12:28:29.344] RPC Server Password required (rpc-server.c:952)
[12:28:29.344] External Done Command set to: (null) (session.c:829)
[12:28:29.345] External Done Command enabled: no (session.c:849)
[12:28:29.345] DHT Generating new id (tr-dht.c:369)
[12:28:29.346] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:67)
[12:28:29.346] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:67)
[12:28:29.346] Using settings from "/mnt/HD_a2/.transmission-daemon" (daemon.c:423)
[12:28:29.347] Saved "/mnt/HD_a2/.transmission-daemon/settings.json" (bencode.c:1645)
[12:28:29.347] transmission-daemon requiring authentication (daemon.c:427)
[12:28:30.348] Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.1.254:80/upnp/control/igd/wanpppcInternet" (upnp.c:105)
[12:28:30.348] Port Forwarding (UPnP) Local Address is "192.168.1.72" (upnp.c:107)
[12:28:31.354] Port Forwarding (UPnP) Port forwarding through "http://192.168.1.254:80/upnp/control/igd/wanpppcInternet", service "urn:schemas-upnp-org:service:WANPPPConnection:1".  (local address: 192.168.1.72:51413) (upnp.c:194)
[12:28:31.355] Port Forwarding (UPnP) Port forwarding successful! (upnp.c:197)
[12:28:31.355] Port Forwarding State changed from "Not forwarded" to "Forwarded" (port-forwarding.c:87)
[12:28:55.867] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:234)

I did a new attempt to start the index.html, but still get the "Conection faild" error.


Then I tried to change the owner from root to anybody. I wrote what you said earlier:

chown -R nobody:nobody /mnt/HD_a2/.transmission-daemon

It still says following:

lrwxrwxrwx    1 root     root            7 Apr  6 12:47 traceroute -> busybox
-rwxr-xr-x    1 root     root       426.0k Mar 15 19:36 transmission-daemon
-rwxr-xr-x    1 root     root       451.1k Mar 15 19:36 transmission-remote
-rwxr-xr-x    1 root     root       418.6k Apr 15  2008 troff

Any idea what I can do next?

Btw: Thank you for your wonderfull job
Please let me know if I wrote something you did not understand.

Last edited by r2d290 (2010-04-09 14:36:01)

Verry well. Now it works to run the program in the foreground, and I have downloaded my first torrent with this prog

But, I was unable to start the program in the background. I write: /ffp/start/transmission.sh start and then I got the message: "Starting transmission-daemon".

Then I open my browser and inserts: http://192.168.1.72:9091/transmission/web/
(this is exactly what I wrote when I run the prog in the foreground, and that worked exelent. Now I only get the standardmessage from firefox saying: "This page is not awaylable" (or something like that. I'm running norwegian languagepack on FF).

Any sugestions?

So, first you want me to start the program in the background, then browse to the ffp/start folder and type: ps ux | grep transmission
?

If so, here is the result:

root@nsa220plus:/ffp/start# /ffp/start/transmission.sh start
Starting transmission-daemon
root@nsa220plus:/ffp/start# ps ux | grep transmission
8133 root     grep transmission
root@nsa220plus:/ffp/start#

then I tried the transmission-remote -si command. Here is the result:

root@nsa220plus:/ffp/start# transmission-remote -si
[17:16:41.747] transmission-remote: (localhost:9091) Couldn't connect to server
root@nsa220plus:/ffp/start#

I could not find any logfiles:

root@nsa220plus:/mnt/HD_a2/.transmission-daemon# ls
blocklists     resume         stats.json
dht.dat        settings.json  torrents
root@nsa220plus:/mnt/HD_a2/.transmission-daemon#

Thanks for your time. I realy appreciate it

zuluwalker wrote:

Isildur wrote:

Running in screen version 1.92-1 of Transm (not dbg) gave me "killed" string in bash window. Now trying to catch that error with debug build in screen...

Ok. I got that "Killed" after ~2 hours of seeding (last time it worked about one day).
KyleK, I PMed you coredump file.

Where can this "coredump" file be found? Is it really named "coredump", or by some other filename? I have little experience in looking for files using find or locate, but I do know enough to find my way around... :-P

If you also experience crashes with Transmission 1.92, it'd might really make a difference if you could provide a corefile for me.

First, you'll need the debug version of Transmission from post #1040.

Then, enable the creation of corefiles with the command 'ulimit -c 2048'. Please note that this is a bash setting, so once you close a shell and reconnect it won't be set again! If you want to enable it permanently, add the line to your .bashrc or .profile file.

You can also specify where corefiles ought to be saved with this command:

$ echo "/ffp/tmp/core_%e-%p" > /proc/sys/kernel/core_pattern

(This is not session-specific but probably won't survive a reboot.)

After this, all corefiles are written to /ffp/tmp with the executable's name (%e) and the process ID (%p).

Let me know how it goes :)

Hi there,

I wanted to try out transmission because I'm not really satisfied with mldonkey, so far (too confusing user interface; not able to select for specific files within a single torrent etc.).

The introduction on the first page says one should check for previous installments of curl and uclibc. So dumb question: How do I do that? Seems like funpkg doesn't have an option for listing already installed packages and other package management like apt-get is not available.

Thanks in advance,
slyght

Thank you for the fast reply! I just installed it and it works very well.

Btw: is it actually needed to forward the TCP port for incoming connections on my router (not the one for web interface). I didn't and it seems to work well whereas I actually thought I'd have to enable it first.

Last edited by slyght (2010-04-11 14:34:37)

KyleK. Any sugestion to my problem (2010-04-09 17:23:31) ?

That gave me the error that the us-folder does noet excist:

root@nsa220plus:~# /ffp/bin/us nobody -c "/ffp/bin/transmission-daemon -f -g /mn
t/HD_a2/.transmission-daemon >/mnt/HD_a2/.transmission-daemon/transmission-daemo
n.log 2>&1 &"
-sh: /ffp/bin/us: not found
root@nsa220plus:~#

I can't get what I'm doing wrong :S

KyleK wrote:

First, you'll need the debug version of Transmission from post #1040.

Got it!

KyleK wrote:

Then, enable the creation of corefiles with the command 'ulimit -c 2048'. Please note that this is a bash setting, so once you close a shell and reconnect it won't be set again! If you want to enable it permanently, add the line to your .bashrc or .profile file.

You can also specify where corefiles ought to be saved with this command:

Code:

$ echo "/ffp/tmp/core_%e-%p" > /proc/sys/kernel/core_pattern

(This is not session-specific but probably won't survive a reboot.)

After this, all corefiles are written to /ffp/tmp with the executable's name (%e) and the process ID (%p).

Let me know how it goes

Will do! I have to backup my .transmission-daemon folder first just in case something breaks. By any chance does the crashes have to do with having too many "open" (i mean seeding) torrents at once? I have about 200 torrents listed with my client with about half of them seeding, and only about 4-5 downloading. I've set my files open to 32 and max total connections to 240 (and 40 max per torrent) but was running happily with 64/480/48 happily before...

Last edited by zuluwalker (2010-04-12 19:54:55)

The program startet when I used that command, and it's still runing after I exit putty. I hope this is a good sign? Here is what I got. Are there anything interesting here?

root@nsa220plus:/mnt/HD_a2/.transmission-daemon# /ffp/bin/su nobody -c "/ffp/bin
/transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon >/mnt/HD_a2/.transmis
sion-daemon/transmission-daemon.log 2>&1 &"
root@nsa220plus:/mnt/HD_a2/.transmission-daemon# ps ux | grep transmission
8564 root     transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u r                                       2d290 -v ***** -w /mnt/HD_a2/Downloads -a 127.0.0.1,192.168.*.*
8565 root     transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u r                                       2d290 -v ***** -w /mnt/HD_a2/Downloads -a 127.0.0.1,192.168.*.*
8566 root     transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u r                                       2d290 -v ***** -w /mnt/HD_a2/Downloads -a 127.0.0.1,192.168.*.*
8567 root     transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u r                                       2d290 -v ****** -w /mnt/HD_a2/Downloads -a 127.0.0.1,192.168.*.*
27324 root     grep transmission
root@nsa220plus:/mnt/HD_a2/.transmission-daemon# transmission-remote -si
Unexpected response: <h1>401: Unauthorized</h1>Unauthorized User
root@nsa220plus:/mnt/HD_a2/.transmission-daemon#

edit: This is wierd. I tried to restart my computer, and now I can't even start the program in the foreground.

root@nsa220plus:/# su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmiss
ion-daemon -t -u r2d290 -v aPassword -w /mnt/HD_a2/Downloads -a 127.0.0.1,192.16
8.*.*"
root@nsa220plus:/#

so, I tried to do what you said about "starting from scratch" again, but not even that worked :S

root@nsa220plus:/# /ffp/start/transmission.sh stop
Stopping transmission-daemon
killall: transmission-daemon: no process killed
root@nsa220plus:/# rm -rf /mnt/HD_a2/.transmission-daemon
root@nsa220plus:/# su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmiss
ion-daemon -t -u r2d290 -v aPassword -w /mnt/HD_a2/Downloads -a 127.0.0.1,192.16
8.*.*"
root@nsa220plus:/#

Is there any way to start "more" from scratch than this? Uninstall everything and start even more from the beginning?

Last edited by r2d290 (2010-04-13 12:21:25)

Could you guys meet me on IRC later today (in maybe 2 hours)? I'd like to get to the bottom of this.

zuluwalker wrote:

Will do! I have to backup my .transmission-daemon folder first just in case something breaks. By any chance does the crashes have to do with having too many "open" (i mean seeding) torrents at once? I have about 200 torrents listed with my client with about half of them seeding, and only about 4-5 downloading. I've set my files open to 32 and max total connections to 240 (and 40 max per torrent) but was running happily with 64/480/48 happily before...

After upgrading to version 1.9.2 from 1.7.1 I've had problems similar to what you described, e.g. the 'Killed' message when running in foreground. Like you I had a few torrents at various stages of completion in the queue. Mine didn't last 2 hours though, it consistently crashed within minutes of starting up.

My guess was that there was some incompatibility with the resume data,  so to start with a clean slate I simply renamed my transmission-daemon direcotry, started/stopped the daemon in the foreground to generate a new config directory and then replaced the default config file with my existing one.  The torrents that were active are also in the transmission-daemon dir and can then simply be requeued. I'm still crossing my fingers in determining if this is 'the'* fix but so far I've managed to download a torrent succesfully and verify/restart one that hadn't completed downloading.

Unlike you I had only 2 incomplete and 5 seeding torrents none of which I mind not seeding anymore. In your case it will probably mean a good few hours of reverification to reseed all those files again. 

hth,

ABCC


*  I've had similar issues with torrents not restarting properly in the past and solved it by deleting the contents of the transmission-daemon/resume and transmission-daemon/torrents directories, which achieves the same result. (don't forget to backup your torrents if you wish to requeue/resume your downloads....)

Last edited by ABCC (2010-05-08 04:21:23)