Twonky Forum

Hi,

I just tried to install the 7.0.8 Twonky Server on my Linkstation Live NAS. I've downloaded the file from http://www.twonkyforum.com/downloads/7. ... -7.0.8.zip and unzipped it on my NAS at /usr/local/twonky. But now, when I try to start twonky with the twonky.sh script, or the twonkystarter file, i get this output:

root:/usr/local/twonky# ./twonky.sh start
Starting /usr/local/twonky/twonkystarter ...
Twonky Version 7.0.8
Starting twonkywebdav ...
For image conversion and scaling the TwonkyServer utilizes ImageMagick. For details on the license please see /usr/local/twonky/cgi-bin/convert-readme.txt

ImageMagick is installed, I don't know why this hint is given. Furthermore, when I try to visit the admin control panel of twonky at
http://10.0.0.42:9000
or
http://10.0.0.42:9010

I can't access it. A portscan of my nas shows me, that there are no open ports from twonky. So, I tried to list all twonky processes, to see whats going on:

root:/usr/local/twonky# ps aux | grep twonky
root 7130 0.0 0.7 1696 400 ? S 12:57 0:00 /usr/local/twonky/twonkystarter
root 7133 0.2 2.6 4600 1404 pts/0 Sl+ 12:57 0:00 /usr/local/twonky/twonkywebdav
root 7136 0.1 2.7 4668 1432 pts/0 Sl+ 12:57 0:00 /usr/local/twonky/twonkyproxy
root 8357 7.3 0.0 0 0 ? Z 13:00 0:00 [twonkyserver] <defunct>
root 8396 0.0 1.1 3364 592 pts/0 S+ 13:00 0:00 grep twonky

I think the "defunct" after the twonkyserver is a problem, maybe the twonkyserver process is a zombie process, can't be started, killed, whatever.
So my question: Is this a bug? I can't find any other errors in the log files. Or are there any newer versions i could try? What could be the problem? My NAS runs with a custom firmware from here: http://www.discountnetz.com/downloadber ... 0-firmware

Thx,
tux

You usually cannot use the twonky.sh script to start Twonky on a NAS device without modifying it to match your NAS device's file structure layout. The script is for mainline Linux. Also some of the commands used in that script do not support the full range of options required by the script, e.g. ps --no-headers.

The output you show from ps would indicate that twonkyserver failed to start. Possibly because it could not write to the default appdata directory which is in /var. This is very common with NAS devices where /var is located in a very small partition. Your ps output does not show the Twonky processes being started with an appdata path so that I suspect is your problem.

You need to use the -appdata command line option when starting each of the Twonky processes to give them a location that can be used for the appdata. So for example on my NAS (not a Linkstation but it still applies) I start the Twonky processes with-
/<path to twonky>/twonkystarter -D -appdata /share/1000/twonky7 &
/<path to twonky>/twonkyproxy -appdata /share/1000/twonky7 &

Same goes with the logfile. Use the -logfile command line option to tell Twonky where to write logs.

/<path to twonky>/twonkystarter -D -appdata /share/1000/twonky7 &

I don't see the purpose of running this command in background (&) when it is being daemonized (-D) ?

cool, -D did the trick!

thx!