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

I just installed 2.12 latest on a clean funplugged system and everything worked out of the box except for deleting the files when I do a "remove torrent and data" action. User rights seems to be fine (directory & files al nobody:501). Is this a bug?

From my experience, Transmission is slowly consuming memory.
I have a DNS-323 with the v1.08 firmware, ffp and transmission. I'm seedding ~400 torrents, mostly private with Transmission. This happens even when I'm not making any changes. I'm not adding new torrents, not downloading anything new. Just seeding those torrents.

When Transmission starts, it uses ~47% of memory, but this number slowly (but surely) rises over a period of a week/week-and-a-half to ~80%. This reduces the amount of available memory to smb, which considerably reduces read/write speeds to about 3-5MB/s (from ~8-10MB/s) over my (currently 100mbit) network.
I first noticed that with Transmission 2.10, and now I'm using 2.12. What I do is restart it every week or so.

Are any of you experiencing a similar thing? How do you deal with it?

scaramanga wrote:

From my experience, Transmission is slowly consuming memory.
I have a DNS-323 with the v1.08 firmware, ffp and transmission. I'm seedding ~400 torrents, mostly private with Transmission.

wow 400 torrent didnt know that was possible with so little memory ive always tried to keep it less than 30 guess i can seed some more then

curl-7.19.4-1.tgz http://www.mediafire.com/download.php?s1xqtvwkphebclk
Transmission-2.12-2.tgz http://www.mediafire.com/download.php?l47urd8et0f98lt
Transmission-2.13-1.tgz http://www.mediafire.com/download.php?9v7mss0dl4pw44i
Automatic-0.6.4-1.tgz http://www.mediafire.com/download.php?lcb1ed2rfbpkefr

Last edited by FunFiler (2010-12-11 06:34:02)

There's one "Reduce memory footprint caused by tr_history" bug that was squashed. Crossing fingers hoping it sorts that memory issue I'm experiencing (asked about it a few posts back).

Edit: Should've used the opportunity and thank you, KyleK.

Last edited by scaramanga (2010-12-10 23:29:53)

scaramanga wrote:

There's one "Reduce memory footprint caused by tr_history" bug that was squashed. Crossing fingers hoping it sorts that memory issue I'm experiencing (asked about it a few posts back).

Edit: Should've used the opportunity and thank you, KyleK.

I've talked with charles from the dev team about this before, as I encountered it as well. He tested with Valgrind but could not find any memory leaks. It could be a fragmentation problem, maybe. I'm not really sure.
We're the only ones affected, I guess, because our NAS has so little memory :)

graffix wrote:

Soprano wrote:

Something is wrong with the latest update. I was running 1.92 for along time with no issues, once I upgraded to 2.12, Every torrent from a few private trackers and public trackers error out with "Announce error: tracker did not respond - Today 09:33:58 PM
Next announce in 31 min 45 seconds"

I did get it to work after rebooting my router, but any newly added torrents gave this same error. I even tried downgrading back to 1.92, and I still have this issue. Any ideas?

I have this exact issue too.  Did you find anything that works Soprano?

Thanks,

Dave

Edit: Actually I get 404 errors.

Sorry for the delayed response. I did finally figure out what my problem was. I was having a DNS issue. The weird thing is, this started the exact same time as my Transmission upgrade. To fix it, I changed my DNS from my router (192.168.1.2) to a Google public DNS (8.8.8.8 and 8.8.4.4) on the NAS. It started working immediately after doing this.

Assuming that Transmission is configured correctly (i.e. BT port is forwarded through your firewall and accessible from the outside. You can test this on the console with 'transmission-remote -pt'), my guess is that the NAS is simply not capable of any higher download speeds due to its limited resources. The underpowered CPU of the DNS-323 simply might not be able to handle all the I/O at such high speeds.

Have you tried with a public torrent such as the latest Ubuntu ISO or OpenOffice? These are generally incredibly fast, and you could use it to rule out problems on the tracker side.

hanog wrote:

I have 80/25 Mbit/s internet connection. On the pc I running uTrorrent 2.2 the download speed is 9-10 MByte/sec and the upload speed is 2,5-3 MByte/s.

I envy these speeds :-)

RaNd wrote:

For those who are having high CPU usage on transmission preventing samba copies etc.. :

vi /ffp/start/transmission.sh

change ->>  command="/ffp/bin/$name"  to -->>  command="nice -n 10 /ffp/bin/$name"

This will starts transmission with a lower priority (default is 0 )

When Transmission start it does hog all CPU usage (scraping a ton of torrents) but after a while it sattles. The problem I'm experiencing is that its memory usage slowly but surely grows from ~45% to 80% and more over a period of a week. Restarting the daemon sorts this out. For a week, at least.

Can you test if the same happens with the web interface? Just to figure out if the issue is with Transmission, or Remote-GUI.

What version were you using previously?

Anyway, if you don't have any torrents running/seeding, your best bet is to rename the current settings folder (default: /mnt/HD_a2/.transmission-daemon) to something else and set up Transmission from scratch.

KyleK, First thank you so much for maintaining this package for the DNS-323.  It's been so awesome using Transmission on the NAS.  I'm trying to upgrade to the newest version, but cannot download 2.13 from your server.  Is it down at the moment? And is this file hosted on another mirror?

Thank you so much!