Transmission 2.42 not restart after crash

[GoogleCodeExporter]

I think this line (or similar) missing from the file /etc/cron.d/root:
*/15 * * * * /opt/etc/init.d/transmission start

Original issue reported on code.google.com by batori.peter on 23 Nov 2011 at 7:12

[GoogleCodeExporter]

That must have gotten lost when the source moved to svn.

It would be neat if a package could create cron jobs without having to write to 
the system cron file. A seperate instance of cron for packages or something.

Original comment by stefansc...@googlemail.com on 24 Nov 2011 at 6:16

[GoogleCodeExporter]

I propose a simple solution:
1. Create a cron job, which run a script (ex. scheduler.sh) every minute
2. scheduler.sh manages the seperate cron jobs. I suggest way:
Directory structure:
[optwaredir]/schedules/1min/
[optwaredir]/schedules/10min/
[optwaredir]/schedules/15min/
[optwaredir]/schedules/30min/
[optwaredir]/schedules/60min/

Original comment by batori.peter on 27 Nov 2011 at 12:39

[GoogleCodeExporter]

Could you make a step-by step guide for creating that script? I'm not skilled 
with unix at all...

Original comment by matti.il...@gmail.com on 16 Jan 2012 at 1:05

[GoogleCodeExporter]

I hate to be spamming but is anybody reading this?

Original comment by matti.il...@gmail.com on 30 Jan 2012 at 10:27

[GoogleCodeExporter]

Yeah ..this should set up the cron job (do the first line only once!):
echo "*/15 * * * * /opt/etc/init.d/transmission start" >> /etc/cron.d/root
/usr/share/snake/config save
/etc/init.d/cron restart

also this should reduce log spam from cron:
sed -i s,"/usr/sbin/crond -c /etc/cron.d","/usr/sbin/crond -l 9 -c 
/etc/cron.d", /etc/init.d/cron
/usr/share/snake/config save
/etc/init.d/cron restart

batori.peter: 
I think busybox has a version of run-parts ..that should do the job of 
scheduler.sh. I'm a bit worried that it will constantly spin up the disk 
though. I'd have to check if it actually happens in practice.

Original comment by stefansc...@googlemail.com on 31 Jan 2012 at 8:48

[GoogleCodeExporter]

Thanks Stefan! Is this a permanent fix or should i run those commands after 
each reboot? At least my transmission config doesn't seem to stick even if I do 
it via snake-os UI...

Original comment by matti.il...@gmail.com on 1 Feb 2012 at 10:45

[GoogleCodeExporter]

Only once .. "/usr/share/snake/config save" writes the config to the flash. 
It's the same as pressing system->config->save config in the web interface.

Did you save after changing the transmission settings?

Original comment by stefansc...@googlemail.com on 2 Feb 2012 at 12:22

[GoogleCodeExporter]

I did save the config. I just now found out that transmission service has to be 
stopped when changing those settings. So now that works.

Only problem now is that I want to disable DHT and PEX and enable UPnP. I 
cannot access these settings from the config though. If I alter these settings 
from transmission, the settings are reset every time the service is restarted. 
I tried editing the transmission config file manually but it seems I couldn't 
locate the right one or it was rewritten.

Original comment by matti.il...@gmail.com on 2 Feb 2012 at 10:46

[GoogleCodeExporter]

Odd that you have to stop transmission .. that shouldn't be necessary.

The config file is /etc/default/settings.json. That's a leftover from when 
transmission was still part of the snake image. I should finally make it use a 
config file in the installation path.

Original comment by stefansc...@googlemail.com on 2 Feb 2012 at 3:16

[GoogleCodeExporter]

I had to stop transmission because whenever I left the transmission service 
page in snake UI, my changes were reset if the service was running.

Thanks for pointing me to the right config file!

Original comment by matti.il...@gmail.com on 2 Feb 2012 at 9:27

[GoogleCodeExporter]

Is there going to be an update for transmission or the firmware? 

I managed to have cron restart transmission if it's stopped, but now a bigger 
issue is transmission freezing after 10 or so hours of running. The process is 
listed as running but it's not seeding nor leeching anything and also doesn't 
let me access the UI. This is something the cron job won't fix.

Original comment by matti.il...@gmail.com on 28 Mar 2012 at 7:47

[GoogleCodeExporter]

Oh, and also transmission still freezes most of the time after starting 
download with new torrent files. Doesn't matter whether I use the torrentwatch 
folder or upload manually.

Original comment by matti.il...@gmail.com on 28 Mar 2012 at 7:48