TwonkyServer on Linksys E3000 - HELP!!

[Ianchi]

I'm having trouble getting TwonkyServer to work on a Linksys E3000 with TomatoRAF firmware.

I've installed MIPS little endian uclibc version and I see the two processes running (twonkymedia and twonkymediaserver) but I can't make it read the ini file, nor access the web config page.
Every time it loads it generates a new .ini file, not taking into account the default.ini.
So it always has an empty server name, and and empty httpport.
This also occurs even if I edit the .ini and set the command line parameter -inifile to it's path.

Any ideas?

Thnks

[phibertron]

You could try to add one or both of the following switches

The is for the path to where the twonkymedia and twonkymediaserver and the twonkyserver-default.ini reside
-appdir <path>

This is for where the data would go like the db files and uploads etc.
-appdata <path>

Also, I think there are two other switches for the ini, not sure if they are needed

-inifile path and filename of ini file
-inipath path to ini file
-ininame filename of ini file

Let us know if this works out, I'm curious to what your attempting, sounds interesting

[Ianchi]

Thanks for the reply, but still no success.
I'm starting Twonky with the following script:


twonkyIni="/opt/twonkymediaserver/config/twonkymedia-server.ini"
twonkyLog="/opt/twonkymediaserver/config/twonky.log"
twonkyData="/opt/twonkymediaserver/config/"
twonkyDir="/opt/twonkymediaserver"

/opt/twonkymediaserver/twonkymedia -D -inifile "$twonkyIni" -logfile "$twonkyLog" -appdata "$twonkyData" -appdir "$twonkyDir"


But still every time I start the process a new .ini is generated replacing the one I edited, and not talking the default values.
Still unable to access the web page.

The log file is generated in the specified path but is empty.

Any ideas?

[phibertron]

The log file is generated in the specified path but is empty.

See this for logging

http://www.twonkyforum.com/viewtopic.php?f=2&t=4473


Also from this post

http://www.twonkyforum.com/viewtopic.ph ... 0.0#p31523

Is /opt the best place to put twonkymedia?
As some NAS clear the /var folder on reboot.
Is the/opt directory one of them on that firmware?

I wonder if the reason you cant get to twonky is because of this

route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0

But still every time I start the process a new .ini is generated replacing the one I edited, and not talking the default values.

Are you refering to the twonkyserver-default.ini when you say the ones you edited?
Are you leveraging the twonkyserver-default.ini?
As that is what is supposed to be used to create the twonkyserver-server.ini, if not detected

Also

If you can get twonky to be responsive
meaning that you can get to it via http gui
I have an idea of how to deal with the settings
Since you are using a startupscript, you could
try and use RPC calls, to set all of your settings
If we cant get past the other stuff

[phibertron]

You know there may bo one other thing needed

I noticed that rmhomedrive is used on a lot of the nas ini's and on the windows home server ini's

Possibly use:

rmhomedrive=/opt/twonkymediaserver/config/

Also

when you runn your exex line
is the context of the script in that path
meaning, cd /opt/twonkymediaserver/twonkymedia

Also

I see & symbol used a lot in the nas scripts, not sure of its purpose

/opt/twonkymediaserver/twonkymedia -D -inifile "$twonkyIni" -logfile "$twonkyLog" -appdata "$twonkyData" -appdir "$twonkyDir" &

[Ianchi]

Pleas, any ideas?

[parnott]

Pleas, any ideas?

Well the /opt directory is probably not a good place to put the Twonky operating files. I always create a specific directory on my harddrive for this purpose e.g. twonky6 at the root of the disk.

Some observations on the parameters on your start command-
-inifile - this does not seem to have worked since the 4.x versions ( the ini is now written to the appdata directory)
-appdir - never heard of it (a string search of the binary does not show it either)
-logfile - I recall having problems with this but I don't recall the specifics

Now I have a completely different NAS, so your configuration will be different but what I do is this-
1) create a directory in the root of your drive (not in the root file system), I usually call it something like 'twonky6', without quotes of course
2) then in the startup script do 'cd /opt/twonkymediaserver'
3) start twonky with the -D parameter and the -appdata parameter followed by the full path from the filesystem root to the directory where you want Twonky to store all its data

[Ianchi]

Still the same behaviour:
it runs, but I can´t access the web interface and on each run it overwrites the .ini without taking into account the default.ini

any ideas appreciated.

Thnks

[parnott]

Still the same behaviour:
it runs, but I can´t access the web interface and on each run it overwrites the .ini without taking into account the default.ini

any ideas appreciated.

Thnks

Post your startup script again with any changes you have made.

When you edit the default.ini make sure it is the one in /opt/twonkymediaserver

Also login to the device as root and post the output from the following commands (NOTE- if you have moved your -appdata directory to another location then use that instead of /opt/twonkymediaserver/config)-

Code: Select all

ls -alF /
ls -alF /opt/twonkymediaserver
ls -alF /opt/twonkymediaserver/config
cat /etc/fstab
cat /etc/mtab
killall twonkymedia
cd /opt/twonkymediaserver
./twonkymedia -appdata /opt/twonkymediaserver/config
ps
ls -alF /opt/twonkymediaserver/config

[Ianchi]

Here it goes, hope you can find a lead from here:

+ startup script: I have change a hundred always with the same behaviour. now I just use:

Code: Select all

root@unknown:/tmp/harddisk2/twonky# /tmp/harddisk2/twonky/twonkymedia -appdata /tmp/harddisk2/twonky/config -D

Here is the output for the commands:

Code: Select all

root@unknown:/tmp/harddisk2/twonky# ls -alF /
drwxr-xr-x   17 root     root           199 May 12 16:58 ./
drwxr-xr-x   17 root     root           199 May 12 16:58 ../
drwxr-xr-x    2 root     root           531 May 12 16:58 bin/
drwxrwxrwx    1 root     root             0 May  7 19:19 cifs1/
drwxr-xr-x    2 root     root             3 May 12 16:58 cifs2/
drwxrwxrwt    4 root     root          1700 Dec 31  1969 dev/
lrwxrwxrwx    1 root     root             7 May 12 16:58 etc -> tmp/etc/
lrwxrwxrwx    1 root     root             8 May 12 16:58 home -> tmp/home/
drwxr-xr-x    2 root     root             3 May 12 16:58 jffs/
drwxr-xr-x    3 root     root           194 May 12 16:58 lib/
drwxr-xr-x    2 root     root             3 May 12 16:58 mmc/
lrwxrwxrwx    1 root     root             7 May 12 16:58 mnt -> tmp/mnt/
drwxr-xr-x   17 root     root          4096 May 15 22:31 opt/
dr-xr-xr-x   50 root     root             0 Dec 31  1999 proc/
drwxr-xr-x    4 root     root            32 May 12 16:58 rom/
lrwxrwxrwx    1 root     root            13 May 12 16:58 root -> tmp/home/root/
drwxr-xr-x    2 root     root           737 May 12 16:58 sbin/
drwxr-xr-x   10 root     root             0 Dec 31  1999 sys/
drwxrwxrwx   10 root     root           400 May 19 00:14 tmp/
drwxr-xr-x    7 root     root            86 May 12 16:58 usr/
lrwxrwxrwx    1 root     root             7 May 12 16:58 var -> tmp/var/
drwxr-xr-x    2 root     root          2067 May 12 16:58 www/

Code: Select all

root@unknown:/tmp/harddisk2/twonky# ls -alF /tmp/harddisk2/twonky/

drwxr-xr-x    8 root     root          1024 May 19 00:21 ./
drwxr-xr-x    6 root     root          1024 May 15 23:51 ../
-rw-r--r--    1 root     root          2768 May 15 23:52 Linux-HowTo.txt
-rw-r--r--    1 root     root         53601 May 15 23:52 RevisionHistory
drwxrwxrwx    2 root     root          1024 May 15 23:52 cgi-bin/
drwxr-xr-x    3 root     root          1024 May 19 00:15 config/
drwxr-xr-x    3 root     root          1024 May 19 00:21 configls/
drwxr-xr-x    3 root     root          1024 May 16 01:04 db/
-rw-r--r--    1 root     root           193 May 15 23:52 initial_keystore.dat
drwxrwxrwx    2 root     root          1024 May 15 23:52 plugins/
-rw-r--r--    1 root     root           421 May 15 23:52 radio.m3u
drwxrwxrwx    4 root     root          3072 May 15 23:52 resources/
-rw-r--r--    1 root     root           262 May 19 00:16 test
-rwxr-xr-x    1 root     root          9944 May 15 23:52 twonkymedia*
-rw-r--r--    1 root     root           449 May 16 01:09 twonkymedia-server-defa
ult.ini
-rw-r--r--    1 root     root          5732 May 16 01:13 twonkymedia-server.ini
-rwxr-xr-x    1 root     root          3775 May 15 23:52 twonkymedia.sh*
-rwxr-xr-x    1 root     root       2267008 May 15 23:52 twonkymediaserver*

Code: Select all

root@unknown:/tmp/harddisk2/twonky# ls -alF /tmp/harddisk2/twonky/config
drwxr-xr-x    3 root     root          1024 May 19 00:15 ./
drwxr-xr-x    8 root     root          1024 May 19 00:21 ../
drwxr-xr-x    3 root     root          1024 May 19 00:11 db/
-rw-r--r--    1 root     root          5760 May 19 00:15 twonkymedia-server.ini

Code: Select all

root@unknown:/tmp/harddisk2/twonky# cat /etc/fstab
#device Mountpoint FStype Options Dump Pass#
LABEL=swap none swap sw 0 0
LABEL=optware /opt ext3 rw,noatime,nodev 1 1
LABEL=harddisk /tmp/harddisk ext3 rw,noatime,nodev 1 1
LABEL=harddisk2 /tmp/harddisk2 ext3 rw,noatime,nodev 1 1

Code: Select all

root@unknown:/tmp/harddisk2/twonky# cat /etc/mtab
rootfs / rootfs rw 0 0
/dev/root / squashfs ro 0 0
proc /proc proc rw 0 0
tmpfs /tmp tmpfs rw 0 0
devfs /dev tmpfs rw,noatime 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/sdb1 /tmp/harddisk2 ext3 rw,nodev,noatime,data=ordered 0 0
- /cifs1 cifs rw,noatime,nodiratime,unc=\\192.168.2.3\TimeCapsuleMIR,username=xxxx,domain=xxxx,uid=0,gid=0,rsize=16384,wsize=16384 0 0
/dev/sda2 /opt ext3 rw,nodev,noatime,data=ordered 0 0

Code: Select all

root@unknown:/tmp/harddisk2/twonky# /tmp/harddisk2/twonky/twonkymedia -appdata /
tmp/harddisk2/twonky/config -D
Daemonizing...

root@unknown:/tmp/harddisk2/twonky# ps
  PID USER       VSZ STAT COMMAND
    1 root      1376 S    /sbin/init noinitrd
    2 root         0 SW<  [kthreadd]
    3 root         0 SW<  [ksoftirqd/0]
    4 root         0 SW<  [events/0]
    5 root         0 SW<  [khelper]
   18 root         0 SW<  [kblockd/0]
   45 root         0 SW   [pdflush]
   46 root         0 SW   [pdflush]
   47 root         0 SW<  [kswapd0]
   48 root         0 SW<  [aio/0]
   90 root         0 SW<  [mtdblockd]
  285 root       752 S    hotplug2 --persistent --no-coldplug
  326 root      1360 S    buttons
  327 root      1300 S    console
  328 root      1712 S    /bin/sh
  330 root      1704 S    syslogd -L -s 50
  332 root      1700 S    klogd
  344 root         0 SW<  [khubd]
  438 root         0 SW<  [scsi_eh_0]
  439 root         0 SW<  [usb-storage]
  456 root         0 SW<  [scsi_eh_1]
  457 root         0 SW<  [usb-storage]
  515 root         0 SW<  [kjournald]
  718 root      1708 R    telnetd -p 23
  744 root      1040 S    eapd
  747 root      1256 S    nas
  750 nobody    1040 S    dnsmasq -c 1500 --log-async
  755 root      2588 S    httpd
  757 root      1720 S    crond -l 9
  758 root         0 SW<  [cifsoplockd]
  760 root         0 SW<  [cifsdnotifyd]
  761 root         0 SW<  [cifsd]
  763 root      1056 S    rstats
  819 root         0 SW<  [kjournald]
 1608 root      1720 S    -sh
 1677 root       748 S    /tmp/harddisk2/twonky/twonkymedia -appdata /tmp/hard
 1678 root      3832 R    /tmp/harddisk2/twonky/twonkymediaserver -appdata /tm
 1679 root      1708 R    ps

When stopping twonkymedia without "-D" I always get the message (with the -D the same goes to the log):

Code: Select all

root@unknown:/tmp/harddisk2/twonky# killall twonkymedia
root@unknown:/tmp/harddisk2/twonky# 00:27:10:249  [Critical] - LOG_SCAN:upnp_file_scanner_exit : critical section not initialized
00:27:10:251  [Critical] - LOG_HTTP:remote_access_lock : critical section not initialized
00:27:10:252  [Critical] - LOG_HTTP:remote_access_unlock : critical section not initialized

When starting the process without -D I get:

Code: Select all

root@unknown:/tmp/harddisk2/twonky# /tmp/harddisk2/twonky/twonkymedia -appdata /
tmp/harddisk2/twonky/config
TwonkyMedia Version 6.0.32
root@unknown:/tmp/harddisk2/twonky#
For image conversion and scaling the TMS utilizes ImageMagick. For details on th
e license please see /tmp/harddisk2/twonky/cgi-bin/convert-readme.txt

Thnks

[parnott]

Something does not look right in your /tmp/harddisk2/twonky/config directory.

There should also be files like -
db.info
twonkymedia-config.html
twonkymedia-config1.html

Plus a few others, all of which are important.

It looks as though Twonky cannot get fully started. It should create/copy all the missing files into the appdata drectory you specified.

The only suggestion I have now is to review the /tmp/harddisk2/twonky/config/townkymedia-server.ini file and see if there are any paths not pointing to /tmp/harddisk2/twonky/config.

And as I don't know this device also ask-
Does it have enough memory to run Twonky?
Are you using the right version of Twonky for the device?
Have you Googled to see if anyone else has got it running?