transmission process Kills beacause of Out of Memory

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Added torrent files to transmission and start downloading them

2. run the system for several hours. the problem occurs may be in an hour or 
may be in couple of hours

3. Swap file enabled & running on attached USB HDD, Syslog also moved to 
attached USB HDD

What is the expected output? What do you see instead?

The system is up and running the services which needs to perform smooth 
operation of transmission client so the client would download the added 
torrents without any problem.

instead of doing that it does,

terminate the transmission process saying out of memory. and in the services, 
transmission service is not running.

What version of the product are you using? On what operating system?

SNAKE OS V1.2.0 (20100621) - 2.6.16-gazineu

80gb USB HDD attached. Swap enabled on it.

Please provide any additional information below

when i reboot the device when this problem occurs, the system run normally 
again and it giving the same problem in couple of hours. the system not 
freezed, crashed, it can be accessed through the browser, but the only thing is 
the transmission services is stopped. please see the attached log file.

Original issue reported on code.google.com by wickum.m...@gmail.com on 6 Sep 2010 at 2:05

Attachments:

• Log.txt

[GoogleCodeExporter]

I can confirm this bug.  Please let me know if you need any information from my 
side.

Original comment by sergio...@gmail.com on 20 Sep 2010 at 1:36

[GoogleCodeExporter]

Hi,

actually i am a very new user with Snake OS and i am lack of knowledge about 
its development and compiling. if you can rectify the bug and send me or 
publish the new firmware, it would be great :)

thank you

Original comment by wickum.m...@gmail.com on 20 Sep 2010 at 4:47

[GoogleCodeExporter]

Sorry, I am not a developer so I can't publish a new firmware.  I was just 
confirming your bug report :-).

However, I talked to a friend of mine and he confirmed that using SNAKE OS 
V1.0.0 (20091027), this issue does NOT happen.

Original comment by sergio...@gmail.com on 20 Sep 2010 at 4:55

[GoogleCodeExporter]

WoW.

nice to hear that. where can i get it?

could you please ask your friend again?

Original comment by wickum.m...@gmail.com on 20 Sep 2010 at 5:10

[GoogleCodeExporter]

I'm sorry, it seems I got confused about the issue.  What's really happening 
here is: the device reboots frequently.  Instead of just killing the 
Transmission process, the NAS simply reboots!  That's the issue which doesn't 
happen with my friend...

I talked to him again, and he said he eventually experiences the same problem 
you're facing, i.e., Transmission gets killed by oom-killer.  However, his 
device doesn't reboot like mine (and apparently neither does yours, right?).  
Sorry about the confusion.  I think I'll open a separate bug report for my 
problem.

Original comment by sergio...@gmail.com on 20 Sep 2010 at 10:31

[GoogleCodeExporter]

oki doki.

at least yours getting restarted and transmission client too get restarted. 
then it will verify the downloaded portion of your torrent then it will 
continue to download. so i guess no harm to the download. but mine completely 
stops the transmission service and won't start again. if it is restarted like 
yours, i can live with that too :D what is the model of your device?

Original comment by wickum.m...@gmail.com on 24 Sep 2010 at 12:54

[GoogleCodeExporter]

I can confirm I have the same issue.
And if someone uses this hardware just for bt purposes, it became an annoyance. 
I had to drop my NAS use until further evaluation of this issue, but I'll keep 
following the topic to check if there'll be any improvement.

Original comment by rvenan...@gmail.com on 6 Oct 2010 at 10:52

[GoogleCodeExporter]

I have the same issue with oomkiller killing the transmission daemon.

I have an NS-K330 with a 1.5TB HDD attached formatted in ext2 format. I 
currently have 4 torrents open and seeding, and the client won't run for more 
than a couple of hours before oomkiller kills it.

Original comment by cary.win...@gmail.com on 7 Oct 2010 at 5:26

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm having this problem too.. my solution is running the chrooted debian, once 
your inside you can choose from many torrent clients, I prefer Bit Tornado on a 
screened terminal, it doesn't crash and works very fast.

Original comment by nicol...@gmail.com on 29 Nov 2011 at 4:52

[GoogleCodeExporter]

I´ve implemented a script thats relaunch transmission-daemon in case of crash.

These are the steps to implement this:

1 .- I´v added a new key in the file /etc/default/config thats enable or not 
the relaunch option:
echo "keep_transmission_alive=1" >> /etc/default/config

2 .- Create a file called trans_alive in the following route 
"/opt/etc/trans_alive" (You can use vi editor). The code within the file is the 
next:

#------------------------------------BEGIN OF 
SCRIPT----------------------------------
#!/bin/sh
# SNAKE OS - 2012-03-27
# Called by crond (periodically)
# Created by Rafix
export PATH=/bin:/sbin:/usr/bin:/usr/sbin

KEEP_ALIVE=$(grep "keep_transmission_alive=" /etc/default/config | cut -d = -f 
2)
if [ $KEEP_ALIVE -eq 1 ] ; then
        PID=$(pidof transmission-daemon | cut -d ' ' -f 1)
                if [ ${PID:-empty} = "empty" ] ; then
                       /opt/etc/init.d/transmission start > /dev/null
                fi
fi
#---------------------------------------END OF 
SCRIPT----------------------------------

3.- Assign execution permission to this file: 

chmod u+x /opt/etc/trans_alive

4.- Add a line in the crond of the root user that calls the script every 10 
minutes:
echo "*/10 * * * * /opt/etc/trans_alive" >> /etc/cron.d/root

5.- VERY IMPORTANT!!!! Save the configuration from the webadmin (System -> 
Config -> Save Config button). If you don´t do this after reboot you will lose 
all changes in the crond file and config file. 

And that´s all. 

I´m working to improbe this method by modifying webadmin for activate or 
deactivate keep_transmission_alive from transmission web page.
I know that this is a poor fix but it works. Hope I have help you.
Sorry for my english, I´m from Spain and I don´t know too much well speak in 
english.

Original comment by jra...@gmail.com on 28 Mar 2012 at 7:20

[GoogleCodeExporter]

Can u explain me this steep?
¿Puedes explicar este paso? tecleo tal cual lo que pones?
4.- Add a line in the crond of the root user that calls the script every 10 
minutes:
echo "*/10 * * * * /opt/etc/trans_alive" >> /etc/cron.d/root

si puedes contactame en mi mail (manuel.mena de gmail), necesito ayuda con la 
caida constante de transmission 
Gracias

Original comment by manuel.m...@gmail.com on 11 Apr 2012 at 10:39

[GoogleCodeExporter]

Hola Manuel. Sí, la idea es añadir una linea al fichero "/etc/cron.d/root" ya 
que es el fichero que lee el cron. La linea lo que indica es que se ejecute 
cada 10 minutos el script trans_alive. La escribes tal cual y si quieres para 
ver si te la ha cogido bien puedes hacer "more /etc/cron.d/root" para ver si te 
la añadio correctamente.

Original comment by jra...@gmail.com on 11 Apr 2012 at 4:32

[GoogleCodeExporter]

I´v created the attached file that replace transmission service web page and 
includes a checkbox to enable, disable the parameter keep_transmission_alive.

You only have to replace the file /opt/share/www-service/transmission with 
attached.

Original comment by jra...@gmail.com on 11 Apr 2012 at 4:38

Attachments:

• transmission

[GoogleCodeExporter]

Copy the file transmission, I check Keep Alive Transmission but when you click 
apply or start the mark disappears. I have also tried saving the settings and 
still the same. What I can do?

Original comment by manuel.m...@gmail.com on 11 Apr 2012 at 7:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Check the file /etc/default/config, within it there must be a line like 
keep_transmission_alive=1 if the parameter is active and 
keep_transmission_alive=0 if is deactived.

If not exists, insert how is indicated above an SAVE THE CONFIG from the web, 
this is mandatory to avoid lost the parameter on reboot.

Original comment by jra...@gmail.com on 11 Apr 2012 at 11:07

[GoogleCodeExporter]

Then in the file / etc / default / config add:
 A-One line with "keep_transmission_alive = 1" (without quotes)
 or
 B-Two lines "keep_transmission_alive = 1
                           keep_transmission_alive = 0 "
 What option A or B?.
 As you see, with Linux I'm very lost.
 Thanks for your help.

Original comment by manuel.m...@gmail.com on 12 Apr 2012 at 8:29

[GoogleCodeExporter]

In the end I got it. Now the check is marked in transmission. The steps I have 
taken has been:
1 .- I´v added a new key in the file /etc/default/config thats enable or not 
the relaunch option:
echo "keep_transmission_alive=1" >> /etc/default/config

2 .- Create a file called trans_alive in the following route 
"/opt/etc/trans_alive" (You can use vi editor). The code within the file is the 
next:

#------------------------------------BEGIN OF 
SCRIPT----------------------------------
#!/bin/sh
# SNAKE OS - 2012-03-27
# Called by crond (periodically)
# Created by Rafix
export PATH=/bin:/sbin:/usr/bin:/usr/sbin

KEEP_ALIVE=$(grep "keep_transmission_alive=" /etc/default/config | cut -d = -f 
2)
if [ $KEEP_ALIVE -eq 1 ] ; then
        PID=$(pidof transmission-daemon | cut -d ' ' -f 1)
                if [ ${PID:-empty} = "empty" ] ; then
                       /opt/etc/init.d/transmission start > /dev/null
                fi
fi
#---------------------------------------END OF 
SCRIPT----------------------------------

3.- Assign execution permission to this file: 

chmod u+x /opt/etc/trans_alive

4.- Replace the file /opt/share/www-service/transmission with attached.

5.-SAVE THE CONFIG from the web.

It only remains to verify that the restart transmission. Thank you very much 
for your help.

Original comment by manuel.m...@gmail.com on 12 Apr 2012 at 2:16

[GoogleCodeExporter]

It does not work, at least for me. Within hours web access transmission fails, 
later I can not access remote transmission and finally though the service is 
active, not download. Proves another solution.
thanks and regards.

Original comment by manuel.m...@gmail.com on 15 Apr 2012 at 9:53