Transmission 2.42 not restart after crash
SNAKE OS firmware for wlxkj652, ns-k330 and NAS based on str8132 SoC
Brought to you by:
dgazineu
Menu
▾
▴
#243 Transmission 2.42 not restart after crash
New
nobody
None
Medium
Defect
2012-03-28
2011-11-23
Anonymous
No
Originally created by: batori.peter (code.google.com)
I think this line (or similar) missing from the file /etc/cron.d/root:
*/15 * * * * /opt/etc/init.d/transmission start
Related
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: stefansc...@googlemail.com
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.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: batori.peter (code.google.com)
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/
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: matti.il... (code.google.com)@gmail.com
Could you make a step-by step guide for creating that script? I'm not skilled with unix at all...
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: matti.il... (code.google.com)@gmail.com
I hate to be spamming but is anybody reading this?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: stefansc...@googlemail.com
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.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: matti.il... (code.google.com)@gmail.com
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...
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: stefansc...@googlemail.com
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?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: matti.il... (code.google.com)@gmail.com
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.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: stefansc...@googlemail.com
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.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: matti.il... (code.google.com)@gmail.com
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!
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: matti.il... (code.google.com)@gmail.com
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.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: matti.il... (code.google.com)@gmail.com
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.