Hi everyone,
I've got a DNS-320L with transmission 2.82 installed onto Fun_plug 0.7. Transmission runs seemingly normally until I add a torrent, at which point I believe the program crashes (Remote GUI loses connection and I cannot connect on the ip:port). It can run smoothly for days without crashing if you don't use it, and as soon as you add the torrent it breaks. Once you restart transmission you have to remove the torrent you just added as it says the specified file could not be found and so you have to re-add it, causing the program to crash again.
Does anyone have any ideas what could be causing this?
Will
DNS-320L & Transmission
Re: DNS-320L & Transmission
I seem to have found a thread of someone saying run:x190 wrote:Does this help?
chmod 664 /dev/random
chmod 775 /dev/urandom
before starting transmission and it seems to work. Would there be any way to automate this?
Dlink DNS-320 & Transmission Daemon - Big log file crypt err
Hello,
The same problem here on a Dlink NAS DNS-320. The log was growing 6GB by day due to this error.
I could manually chmod the 2 folders /dev/random and /dev/urandom, but I wanted to do this automatically.
So I alter the transmission.sh under edit on Midnight Commander (it is not installed by default in FunPlug).
After the reboot the transmission-daemon starts, and the permissions are corect:
root@Nas-Perso:~# ls -l /dev/random
crw-rw-r-- 1 root root 1, 8 Jan 1 2000 /dev/random
root@Nas-Perso:~# ls -l /dev/urandom
crwxrwxr-x 1 root root 1, 9 Jan 1 2000 /dev/urandom
No more big log file and no more crypt errors.
So here is the modification, just before the daemon start, after the echo "Starting $name" , and it is done, even with the user nobody, so no problems on rights.
This is my transmission.sh file, don't forget to use the HOME of your installation.
The same problem here on a Dlink NAS DNS-320. The log was growing 6GB by day due to this error.
I could manually chmod the 2 folders /dev/random and /dev/urandom, but I wanted to do this automatically.
So I alter the transmission.sh under edit on Midnight Commander (it is not installed by default in FunPlug).
After the reboot the transmission-daemon starts, and the permissions are corect:
root@Nas-Perso:~# ls -l /dev/random
crw-rw-r-- 1 root root 1, 8 Jan 1 2000 /dev/random
root@Nas-Perso:~# ls -l /dev/urandom
crwxrwxr-x 1 root root 1, 9 Jan 1 2000 /dev/urandom
No more big log file and no more crypt errors.
So here is the modification, just before the daemon start, after the echo "Starting $name" , and it is done, even with the user nobody, so no problems on rights.
Code: Select all
#!/ffp/bin/sh
# PROVIDE: Transmission
. /ffp/etc/ffp.subr
if [ -d /mnt/HD/HD_a2 ]; then
TRANSMISSION_HOME=/mnt/HD/HD_a2/.transmission-daemon
else
TRANSMISSION_HOME=/mnt/HD_a2/.transmission-daemon
fi
name="transmission-daemon"
command="/ffp/bin/$name"
start_cmd="transmission_start"
stop_cmd="transmission_stop"
status_cmd="transmission_status"
user=nobody
su_cmd="/ffp/bin/su"
transmission_start()
{
if [ ! -d ${TRANSMISSION_HOME} ]; then
$su_cmd $user -c "mkdir ${TRANSMISSION_HOME}"
fi
echo "Starting $name"
chmod 664 /dev/random
chmod 775 /dev/urandom
$su_cmd $user -c "$command -g ${TRANSMISSION_HOME} -e ${TRANSMISSION_HOME}/$name.log"
}
transmission_stop()
{
echo "Stopping $name"
/ffp/bin/killall -SIGINT $name
}
transmission_status()
{
_pids=$(pidof $name)
if test -n "$_pids"; then
echo "$name is running"
else
echo "$name not running"
fi
}
run_rc_command "$1"
This is my transmission.sh file, don't forget to use the HOME of your installation.
Last edited by rivman on Sat Dec 20, 2014 9:23 am, edited 1 time in total.
-
- Posts: 1
- Joined: Tue Nov 04, 2014 12:15 pm
Re: DNS-320L & Transmission
Thanks for your help on the above post, Ive been pullung my hair out for hours! All working like a dream now!