Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi!
I have a little problem with transmission 2.22 (and other versions). It's crashes:
dmesg:
...
Free pages: 7992kB (0kB HighMem)
Active:1391 inactive:1378 dirty:0 writeback:7 unstable:0 free:1998 slab:9605 mapped:5 pagetables:128
DMA free:8140kB min:1024kB low:1280kB high:1536kB active:5564kB inactive:5512kB present:65536kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: 838*4kB 554*8kB 15*16kB 1*32kB 1*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 8120kB
Normal: empty
HighMem: empty
Swap cache: add 3208496, delete 3208462, find 774037/1528220, race 0+6
Free swap = 1041584kB
Total swap = 1060208kB
Out of Memory: Killed process 29310 (transmission-da).
Out of Memory: Killed process 29311 (transmission-da).
Out of Memory: Killed process 29312 (transmission-da).
Out of Memory: Killed process 29313 (transmission-da).
top:
Mem: 60656K used, 1156K free, 0K shrd, 10788K buff, 4368K cached
CPU: 16% usr 3% sys 0% nice 0% idle 79% io 0% irq 0% softirq
Load average: 3.27 2.98 2.33
PID PPID USER STAT VSZ %MEM %CPU COMMAND
1575 1 root S 9052 15% 0% /web/webs
31509 31506 nobody D 7312 12% 19% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmissio
31507 31506 nobody S 7312 12% 1% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmissio
31505 1 nobody S 7312 12% 0% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmissio
31508 31506 nobody S 7312 12% 0% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmissio
31506 31505 nobody S 7312 12% 0% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmissio
1804 1 1000 S 5624 9% 0% /ffp/sbin/unfsd -e /ffp/etc/exports
...
May be we can minimize memory usage? Or use swap file?
Offline
Hm, that is strange. I've seen Transmission use 45% of system memory yet it never has crashed for me for that reason. Your dmesg shows tha swap is plenty available.
Are you sure Transmission is the cause for this?
Offline
Transmission, cleanboot installed and started... lighttpd, telnetd, unfsd started...
/mnt/HD_a2/ffp/pkg # ls -ls /ffp/start/
4 -rw-r--r-- 1 root root 52 Oct 25 2008 LOGIN.sh
4 -rw-r--r-- 1 root root 35 Oct 25 2008 SERVERS.sh
4 -rwxr-xr-x 1 root root 1401 Nov 2 2009 cleanboot.sh
4 -rw-r--r-- 1 root root 203 Sep 29 2008 inetd.sh
4 -rw-r--r-- 1 root root 229 Jan 23 2010 kickwebs.sh
4 -rwxr-xr-x 1 root root 223 Jan 23 2010 lighttpd.sh
4 -rw-r--r-- 1 root root 267 Apr 15 2008 mediatomb.sh
4 -rw-r--r-- 1 root root 1468 Apr 15 2008 nfsd.sh
4 -rw-r--r-- 1 root root 526 Mar 2 2009 ntpd.sh
4 -rw-r--r-- 1 root root 160 Apr 16 2008 portmap.sh
4 -rw-r--r-- 1 root root 224 Mar 3 2009 rsyncd.sh
4 -rw-r--r-- 1 root root 971 May 20 2009 sshd.sh
4 -rw-r--r-- 1 root root 383 Sep 29 2008 syslogd.sh
4 -rwxr-xr-x 1 root root 169 Sep 29 2008 telnetd.sh
4 -rwxr-x--- 1 root root 767 Feb 20 2010 transmission.sh
4 -rwxr-xr-x 1 root root 998 Feb 26 2009 unfsd.sh
Last edited by Elmor (2011-04-21 13:32:40)
Offline
Can you attach your Transmission's settings.json (don't forget to remove any auth info ?
Also, what usage are we talking about (how many torrents loaded/downloading/seeding)?
Offline
about 15 stopped torrents
1-2 checking
1-2 downloading
Offline
What would you say is the maximum recommended amount of torrents (active/seeding) in Transmission on a DNS-320?
I'm using both the webgui and the "Transmission Remote GUI", and they are becoming more and more unresponsive as my torrent count has increased, and is now around 80.
Thanks
Edit: Rebooting (41 days since the last reboot) actually helped significantly, now Transmission is very responsive again. Memory leak, or what could cause this?
Last edited by ckarv (2011-04-27 23:09:17)
Offline
Hi all.
I've just tried to download the client, but the kylek.is-a-geek server appears to be down. Is that temporary or should I try to look elsewhere to get the client for my dns-323 ?
Thanks
Offline
It's only temporary, the DynDNS host seems not up-to-date. Just wait a while, it should work again soon (in ~4 hours at the latest, when I'm able to do the reset manually).
Offline
Ok, will do.
Thanks
Offline
If you don't want to wait, I've posted links to an alternative site earlier in the thread.
Check post #1644
Last edited by FunFiler (2011-05-06 19:47:42)
Offline
I have the same problem like Elmor.
The dsmeg says:
Free pages: 1444kB (0kB HighMem)
Active:1799 inactive:3593 dirty:0 writeback:60 unstable:0 free:361 slab:8867 mapped:2633 pagetables:76
DMA free:1444kB min:1024kB low:1280kB high:1536kB active:7196kB inactive:14372kB present:65536kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: 107*4kB 115*8kB 0*16kB 1*32kB 1*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 1444kB
Normal: empty
HighMem: empty
Swap cache: add 1360013, delete 1357480, find 297146/633332, race 0+0
Free swap = 505184kB
Total swap = 530104kB
Out of Memory: Killed process 1693 (transmission-da).
Out of Memory: Killed process 1707 (transmission-da).
Out of Memory: Killed process 1708 (transmission-da).
Out of Memory: Killed process 1712 (transmission-da).
top:
Mem: 60392K used, 1420K free, 0K shrd, 10556K buff, 5712K cached
CPU: 45% usr 27% sys 0% nice 0% idle 27% io 0% irq 0% softirq
Load average: 3.99 3.85 3.57
PID PPID USER STAT VSZ %MEM %CPU COMMAND
13787 13786 nobody R 17524 28% 44% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-da
13790 13786 nobody R 17524 28% 29% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-da
13785 1 nobody S 17524 28% 0% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-da
13788 13786 nobody S 17524 28% 0% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-da
13786 13785 nobody S 17524 28% 0% /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-da
1430 1 root S 8932 14% 0% /web/webs
13778 1167 root S 5124 8% 0% smbd -D
13798 1710 root S 5084 8% 0% sshd: root@pts/0
1167 1 root S 4828 8% 0% smbd -D
1169 1167 root S 4828 8% 0% smbd -D
1170 1 root S 2968 5% 0% nmbd -D
1532 1 root S 2964 5% 0% pure-ftpd (SERVER)
1710 1 root S 2464 4% 0% /ffp/sbin/sshd
1505 1 root S 1600 3% 0% crond
1 0 root S 1596 3% 0% init
1469 1 root S 1596 3% 0% -sh
13800 13798 root S 1368 2% 0% -sh
13803 13800 root R 1356 2% 0% top
1214 1 root S 1180 2% 0% xmldb -n config
1458 1 root S 1156 2% 0% op_server 3 3 3
1560 1 root S 1044 2% 0% lpd Waiting
1404 1 root S 920 1% 0% chkbutton
1594 1 root S 728 1% 0% apkg
1452 1 root S 700 1% 0% fancontrol 0
1593 1 root S 700 1% 0% mserver
1548 1 root S 496 1% 0% atd
What is the optimal settings of the settins.json file? I did not change anything in the connections part.
Is it a solution if I would use a pendrive to extend the swap file?
It is a DNS-323.
Last edited by Cirip (2011-05-09 22:22:36)
Offline
Elmor, Cirip,
If transmission crashes repeatedly, especially soon after start up, it will be because of it choking on one of the incomplete torrents its trying to verify. If you're quick you may be able to remove the torrent with the webUI before transmission crashes, otherwise remove the relevant torrent in the configdir/torrents (and perhaps the partial download in the incomplete directory) when transmission isn't running and restart.
Offline
After upgrading from 2.04 to 2.22 it seems the script I've written to run upon torrent completion is no longer executed. According to the changelog of 2.20: "Improve support for running scripts when a torrent finishes downloading", so perhaps something was broken. Has anyone else encountered this and/or have a working torrent-done script in v2.22?
Offline
I have been running a script on torrent completion for some time. I had no issues when I upgraded to v2.22. Sorry, it seems to work fine for me.
Offline
Cheers for confirming that it ought to work. I went back to my old test script and confirmed it didn't work even though the log showed it was being called. After a downgrade to 2.11 and seeing it working I did some stubble scratching then wandered off to make some coffee. No sooner had I reached the kitchen that it dawned on me. Ran back, added a shebang to the top of my test script, upgraded, downloaded the same ebook for the 10th time et voila, my test script actually did what it was supposed to.
So, as of 2.20ish you've got to have a shebang for your script to run.
Thanks again.
Offline
Good to hear you got it working. I'm surprised it worked without the shebang to begin with.
Offline
ABCC wrote:
Elmor, Cirip,
If transmission crashes repeatedly, especially soon after start up, it will be because of it choking on one of the incomplete torrents its trying to verify. If you're quick you may be able to remove the torrent with the webUI before transmission crashes, otherwise remove the relevant torrent in the configdir/torrents (and perhaps the partial download in the incomplete directory) when transmission isn't running and restart.
Thanks ABCC the answer!
But I think the program doesn't crash just not enough memory.
dmesg says:
..
Out of Memory: Killed process 1693 (transmission-da).
Out of Memory: Killed process 1707 (transmission-da).
..
All torrents I am downloading is working. No problem with verifying.
Are you any other hint?
Best Regards:
C.
Offline
Hi Cirip,
You're right in saying it's not a crash but an out of memory error. The operating system has killed transmission to ensure that both it and all the other applications can keep running. Usually this is caused by a memory leak in the app that was killed, on an overloaded server however it's possible that the app that consumes the most memory rather than the one that's causing the problem is the one to be killed.
The only time I've had transmission exit due to the OOM-Killer is due to there being 'something' wrong with a particular torrent. Normally it takes a while for me to notice it. Keeping an eye on the verifying process after a restart usually shows up which torrent causes the problem, deleting it provides the solution.
Perhaps a better method for finding out which torrent is the problem is to simply pause them all and then finish them one by one. If one really is bad it'll crash transmission quite consistently so it's quite noticeable.
As for other ideas, occasionally transmission gets stuck when i download a very well seeded file or many files at the same time. Eventhough I use bandwith limits to ensure transmission doesnt use up all of my bandwith the download rate can make transmission completely unresponsive or even crash.
Unless you're simply overloading your NAS with transfers my suspicion is that one of your torrents has somehow gone wrong. As such it's now ruining it for all the torrents by having transmission-daemon wiped out by the OOM-killer*. Deleting it and requeueing it will prove to be the solution, which one it is however is up for you to find out. Pause them all, restart half and let them finish. Repeat til it crashes, pause them all then restart half of the ones that were running. Repeat til you find the broken torrent.
Or maybe it's time to pull the drives out and run fsck on them....?
HTH,
ABCC
* http://linux-mm.org/OOM_Killer
Last edited by ABCC (2011-05-15 22:29:22)
Offline
It's time for a new Transmission release. v2.30 is up and running.
As always, check the first post for the download link and Changelog.
I made some minor changes to the start script. Please let me know if you run into problems starting/stopping Transmission.
Also, of course, I'd like to know how the new version is working out for you
Cheers!
Offline
KyleK wrote:
It's time for a new Transmission release. v2.30 is up and running.
As always, check the first post for the download link and Changelog.
I made some minor changes to the start script. Please let me know if you run into problems starting/stopping Transmission.
Also, of course, I'd like to know how the new version is working out for you
Cheers!
Muchas gracias!
Offline
I have a problem to stop trans:
# ffp/start/transmission.sh stop Stopping transmission-daemon [22:15:22.865] transmission-remote: (http://localhost:9091/transmission/rpc/) Timeout was reached
And when transmission is run - cpu load is 0%.
WEB GUI don't reacheble. But "top" command is show that transmission is run
# /ffp/start/transmission.sh stop Stopping transmission-daemon Unexpected response: <h1>401: Unauthorized</h1>Unauthorized User
Ufffffff O_o
I can stop trans only via
killall -9 transmission-daemon
Last edited by Logrus (2011-05-17 21:41:58)
Offline
KyleK wrote:
It's time for a new Transmission release. v2.30 is up and running.
As always, check the first post for the download link and Changelog.
I made some minor changes to the start script. Please let me know if you run into problems starting/stopping Transmission.
Also, of course, I'd like to know how the new version is working out for you
Cheers!
Hi Kylek, I have the following error message when I try to stop Transmission 2.30 on DNS 323:
Unexpected response: <h1>401: Unauthorised</h1>Unauthorised User
Offline
No issues here, but I used my saved scripts to stop/start as I've adjusted them a bit to suit my needs.
Offline
caps111 wrote:
Hi Kylek, I have the following error message when I try to stop Transmission 2.30 on DNS 323:
Unexpected response: <h1>401: Unauthorised</h1>Unauthorised User
Bah! You're right, I didn't consider people with active authentication.
To explain: Since a few versions ago, you can use 'transmission-remote --exit' to tell the daemon to quit, which I think is much nicer and cleaner than send a 'kill' signal.
Of course, if you activate authentication, the above command needs to be changed accordingly.
I've updated the package in the first post with a new start script that reverts to the old "stop" command.
Offline
The Transmission crew released v2.31 today, but I won't make a package of it.
The difference between v2.30 and v2.31 is miniscule and I incorporated the cange into my build of v2.30.
In short: My Transmission package of Transmission 2.30 is virtually identical to v2.31.
Offline