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

try creating a script for example transstop.sh with the command within it for example

#!/bin/sh

/mnt/HD_a2/ffp/start/transmission.sh stop

and get cron tab to run the transstop.sh script
This will ensure that the parameters are getting passed correctly. you can also test the script in isolation of cron which may help.

Last edited by index monkey (2009-02-03 12:19:09)

romanl wrote:

KyleK wrote:

That cron entry only logs stdout messages, add '2>&1' to also log stderr. Maybe it'll provide helpful information as to why it doesn't work as expected.

It seems I've found the rootcause - stderr tells: "/mnt/HD_a2/ffp/start/transmission.sh: line 42: killall: not found"

killall sits in /ffp/bin. You can change the script accordingly. Just add the full path to line 29 of transmission.sh

I can't get transmission to work. Firmware 1.06, fun_plug 0.5, Transmission-1.42-1.tgz. Transmission is running, I can access the GUI and add torrents. But nothing is downloading. No other services are running then default for this setup (and no other BT client).

# ps | grep transmission
1758 nobody   /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon
1772 nobody   /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon
1773 nobody   /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon

# cat transmission-daemon.log
Transmission 1.42 (7500) started
RPC Server: Adding address to whitelist: 127.0.0.1
RPC Server: Adding address to whitelist: 192.168.1.*
RPC Server: Serving RPC and Web requests on port 9091
RPC Server: Whitelist enabled
Port Forwarding: Opened port 51413 to listen for incoming peer connections
Searching for web interface file "/home/nobody/.local/share/transmission/web/javascript/transmission.js"
Searching for web interface file "/ffp/share/transmission/web/javascript/transmission.js"
Outlander[2008]DvDrip-aXXo: Couldn't read resume file
Outlander[2008]DvDrip-aXXo: Queued for verification
Outlander[2008]DvDrip-aXXo: Verifying torrent
Outlander[2008]DvDrip-aXXo: Trying tracker "http://tracker.bitreactor.to:2710/announce"
Outlander[2008]DvDrip-aXXo: Trying tracker "http://tracker.bittorrent.am/announce"
Outlander[2008]DvDrip-aXXo: Trying tracker "http://tracker.prq.to/announce"

... and it goes on with trying trackers.

# strace transmission-daemon -f
nanosleep({1, 0}, Couldn't bind port 51413: Address already in use
Port Forwarding: Couldn't open port 51413 to listen for incoming peer connections (errno 98 - Address already in use)

Portforwarding is working properly, I've checked it. I can't imagine which other service could be using port 51413.

Any ideas how to solve this? Help is much appreciated as I'm at a loss.

KRH wrote:

downloading of copyrighted software is not leagl..

Try download some free software from bittorrent to see if your ISP might be blocking the pirate download.

No that can't be the problem. I've been using various clients on my network for quite some time without any problems.

I'm so happy that transmission works on some PT again since 1.42.
And now 1.50 is coming......

Kylek, thanks for your great work. You rocks!

Hello!

I'm starting to have a problem with clutch using Transmission 1.4. The gui is loading slower and slower. It now takes minutes for it to load. Requests are only done on my LAN and the loading speeds for clutch has been ok earlier. I've rebooted my router as well and nothing else on my LAN is noticable slow. The load on the NAS isn't remarkable high either, using "top" I see that transmission is using about 40-50% of cpu. I have removed finished torrents also, so there's only a couple of current torrents. Anyone having an idea of the hell has gone bananas with clutch? Could it be some kind of cache that I could try deleting somewhere? Advise are welcome

Hi, using Transmission 1.42 I've noticed some problems seeding torrents on a private tracker. The private tracker has a website where you can see how many torrents you are seeding. As I noticed the number of seeding torrents were dropping over time, I checked the Transmission web interface, and nothing there seemed to be wrong (although afaik one cannot see tracker status).

I then ran ps from a telnet session to the dns_323 and there were loads of instances of "/ffp/bin/sh", none of which could be killed.
After rebooting the dns-323, transmission was seeding perfectly again. Any ideas of what causes this?

I have 10 torrents seeded, no downloads in progress. No torrents have been paused.

Just a bit of info on the Transmission development:

I'm currently in a bit of a tough spot: Transmission 1.42 (the official, stable version) has known issues, which have been fixed already. Version 1.50 was supposed to come out at the end of December, but unfortunately, new bugs have surfaced and the dev team apparently has trouble pinpointing the causes.

I stated several times that I won't provide funplug packages of Transmission betas, because they often cause more problems than they solve. This is also the case with the latest beta (1.50b5). It performs fast, downloads fast, has several neat additions, but crashes randomly

Many of the recent questions are very Transmission-specific and I would normally urge those people to ask them at the Transmission forum instead. But since the latest version has been in development for several months, they'll only tell you to upgrad to the latest svn version.

I just want you to know that I follow the development closely, and will provide new packages as soon as stable versions are available.
So, just be a bit more patient. The next version looks really promising, and I'm certain the devs will be able to squash the critical bugs soon.

Hi,

I've upgraded from 1.22 to 1.42, but actually the performance is rather poor. I need to restart the daemon few times a day. Lot of time it is downloading, but with little speed, after restart it jumps to the normal, expected speed. It seems, that it has problems updating the torrent tracker. I will most likely move back to the 1.22 to see, weather it will change, but since I did not had these issues, I think it is because of the version change... So I pretty stuck with the same issue, than the others...

Tóni

Hi KyleK,

First: a very big thank to provide transmission for the DNS. I used the 1.22, that you provided and followed the instructions that were perfect. Also the 1.42 installed flawlessly, had virtually nothing to do with it, just copy/paste your lines and it is working as well.
Second: I hope that you keep up providing these packages as there is a clear development of transmission (transmission gui, integrated clutch with easy password set up, selectable which file I want to download, etc.) and i love to use it (I moved from mldonkey, that is also great, but transmission is more easy and user friendly).
Third: I just wrote the comments, so that if anybody following this thread is about upgrading or installing transmission, should know about, what problems others have. That was not totally clear for me before, so I would have been happy to know about it.

So, thank again, and please don't take it as a critic against your work, as both the package and the instructions are perfect. I just raised my voice, so others know, that they should not delete the 1.22 and clutch directories (as I did), since latter they probably want to move back :-)

Tóni

ps: can you give an estimate when the next stable version will be out? I would love to use that, if it is rather in days than in weeks/months...

I know, I know
It's already compiled, but I'm off to a party. I'll post it tomorrow.

Cheers.