Media Feed not working with 6.0.34 Terastation Live

[turk]

I have a Terastation Live running 6.0.34. I used an Win XP PC to install Twonky. Everything seems to be working very well except the media feed.

Trying to access media feed from the configuration page, I get:

"No user credentials found. Can not authorize with the Mediafusion server."

Searching around, I have found that this problem may be due to several files not being copied to the /root folder, including:

initial_keystore.dat

This file and other do not appear to be in the /root folder but I don't know how to copy them from my desktop. When I try telnet, I can connect but not copy. I may be starting in the wrong directory or calling out the wrong path, regardless, it is not working. I have tried to copy from the /share directory on the terastation but still didn't have any luck. This is what I used:

root@SAO_TERA:/share# cp initial_keystore.dat /root

and it tells me the file doesn't exist. I used the command "ls", expecting a list of what is in the directory and it gives me nothing.

I tried to connect using PuTTY and SSH, but I can't get it to connect.

In windows, I can map to "twonky on 'TeraStation (Sao_tera)'" and this is where I see the installed Twonky files and missing .dat file. Is this the /root folder?

Sorry for the for the newby questions, I have tried for some hours on my own. Thanks for the help.

[parnott]

The initial_keystore.dat file needs to be in the directory where Twonky is installed. Just copy the file there.

/root is a completely different directory which twonky does not use.

[turk]

I have tried to copy it to the Twonky install directory with win explorer and I get 'access denied'. I thought that this was b/c I needed to transfer another way. So I guess it is just a permission thing. I am admin on the computer, do you know why it would not allow me to copy to the Twonky directory? Thanks

[turk]

I have tried to copy the .dat file to the Twonky server directory from many computers and it always comes back with 'access denied'. I haven't found any security properties to change. Is there a reason it would be write protected?

[parnott]

Seems like you have a permissions problem on the NAS.

Sorry I can't help you with the Terastation, but here is what I would do on my Linux NAS.

1. Copy the initial_keystore.dat file to a directory I can write to on the NAS.
2. Log in to NAS as root via Telnet or SSH (whatever works)
3. Change to the directory where Twonky is installed, i.e. cd /pathtotwonkyinstall
4. Copy the initial_keystore.dat into the Twonky directory from the directory where I initially wrote it to the NAS, e.g. cp /pathtowherethefileis/initial_keystore.dat ./

[turk]

Thank you very much. With your help, and realizing the complete install path, I was able to get it copied over. When I was trying to change the directory in telnet, I was leaving out the mnt part of /mnt/array1/twonky.

I got initial_keystore.dat copied over, restarted the server and it is still giving me the same response under Media Feed. Do you know if I need to copy over these files as well:

mediafusion_keystore.dat
mediafusion_keystore.dat_default

I don't have these files as they are not in the 6.0.34 zip but I have seen them referenced in previous revision Media Feed issues. They are not in the Twonky install directory.

[parnott]

Do you know if I need to copy over these files as well:

mediafusion_keystore.dat
mediafusion_keystore.dat_default

I don't have these files as they are not in the 6.0.34 zip but I have seen them referenced in previous revision Media Feed issues. They are not in the Twonky install directory.

No they don't exist. You need to find your Twonky appdata directory and see what is in there. By default it is something like /var/twonkymedia. You should see something like-

Code: Select all

# ls -alF
total 64
-rw-r--r--  1 root root   55 Jul 12 13:05 db.info
-rw-r--r--  1 root root  317 Jul 12 12:50 twonkymedia-config.html
-rw-r--r--  1 root root  311 Jul 12 12:50 twonkymedia-config1.html
-rw-r--r--  1 root root 7269 Jul 12 12:07 twonkymedia-server.ini
drwxr-xr-x  7 root root 4096 Jul 16 12:46 ./
drwxrwxrwx 16 root root 4096 Mar 27 12:16 ../
drwxrwxrwx  6 root root 4096 Jul 12 12:14 cache/
-rw-r--r--  1 root root  507 Jul 16 12:46 clients.data
drwxr-xr-x  4 root root 4096 Jul 12 13:05 db6/
-rwxrwxrwx  1 root root   40 Jul 12 12:50 license.dat*
drwxrwxrwx  5 root root 4096 Jun 22  2010 managed/
drwxrwxrwx  2 root root 4096 Jul 12 12:07 online-data/
-rw-r--r--  1 root root  401 Jul 12 12:50 portal_keystore.dat
drwxrwxrwx  2 root root 4096 Oct  3  2010 rmmedia/
-rw-r--r--  1 root root    0 Jul 12 12:50 tsbyebye
-rw-r--r--  1 root root  702 Jul 12 13:05 twonkymedia-locations-6.db
#

The license.dat and portal_keystore.dat files get generated the first time you run Twonky. My guess is from the contents of the initial_keystore.dat file.

You should also consider moving the Twonky appdata directory out of /var. On many NAS devices /var gets recreated on each reboot so you lose all your settings and media database. Even if /var is saved across reboots, there may not be enough space in the partition for all the Twonky appdata files which includes the media database. See this thread for some general hints about how to do this- http://www.twonkyforum.com/viewtopic.ph ... it=appdata

[turk]

Thanks Parnott
I am going to try and relocate the appdata dir tomorrow but wanted post what I have found so far. It doesn't look like I have a portal_keystore.dat file in my appdata dir.

root@SAO_TERA:/var/twonkymedia/twonkymedia# ls -alF
drwxr-xr-x 3 root root 4096 Jun 26 00:40 ./
drwxr-xr-x 3 root root 24 Jun 20 03:02 ../
-rw-r--r-- 1 root root 474 Jun 25 10:47 clients.data
drwxr-xr-x 4 root root 4096 Jun 26 00:28 db/
-rw-r--r-- 1 root root 59 Jun 26 00:39 db.info
-rw-r--r-- 1 root root 40 Jun 25 00:05 license.dat
-rw-r--r-- 1 root root 0 Jun 25 00:05 tsbyebye
-rw-r--r-- 1 root root 302 Jun 25 00:05 twonkymedia-config.html
-rw-r--r-- 1 root root 298 Jun 25 00:05 twonkymedia-config1.html
-rw-r--r-- 1 root root 592 Jun 26 00:40 twonkymedia-locations-6.db
-rw-r--r-- 1 root root 7277 Jun 25 00:05 twonkymedia-server.ini
root@SAO_TERA:/var/twonkymedia/twonkymedia#

Should I relocate the /var directory to /mnt? Something like /mnt/twonkymedia? Actually, just realized there is already a twonkymedia in there with /music, /pictures and /video.


root@SAO_TERA:/mnt# ls -alF
drwxrwxrwx 15 root root 4096 Jun 23 21:10 ./
drwxr-xr-x 19 500 hdusers 4096 Jun 23 21:10 ../
drwxrwxrwx 8 root root 106 Jun 23 21:11 array1/
drwx------ 2 root root 6 Mar 5 2008 array2/
drwxrwxrwx 2 root root 6 Mar 5 2008 authtest/
drwxrwxrwx 3 root root 36 Jun 23 21:11 disk1/
drwx------ 2 root root 6 Mar 5 2008 disk2/
drwx------ 2 root root 6 Mar 5 2008 disk3/
drwx------ 2 root root 6 Mar 5 2008 disk4/
drwxr-xr-x 4 root root 35 Nov 1 2007 info/
drwxrwxrwx 2 root root 6 Jun 20 17:36 msdfs_root/
drwxrwxrwt 3 root root 260 Jun 26 03:01 ram/
drwxr-xr-x 5 root root 46 Jun 23 20:45 twonkymedia/
drwx------ 2 root root 6 Mar 5 2008 usbdisk1/
drwx------ 2 root root 6 Mar 5 2008 usbdisk2/
root@SAO_TERA:/mnt#


Here's what's in my /root as well, if this helps. In Linux is this also called the root directory? Really trying to keep from sounding like a fool.

root@SAO_TERA:/# ls -alF
drwxr-xr-x 19 500 hdusers 4096 Jun 23 21:10 ./
drwxr-xr-x 19 500 hdusers 4096 Jun 23 21:10 ../
-rw-r--r-- 1 root root 134217728 Jun 23 21:10 .swapfile
drwxr-xr-x 2 root root 4096 Jun 20 03:02 bin/
drwxr-xr-x 3 root root 1024 Jun 23 21:10 boot/
drwxr-xr-x 6 root root 8192 Jun 23 21:11 dev/
drwxr-xr-x 21 root root 4096 Jun 26 02:03 etc/
drwxrwxrwx 2 root root 6 Jan 25 2007 home/
drwxr-xr-x 4 root root 4096 Jan 25 2007 lib/
drwxr-xr-x 2 root root 6 Jun 23 21:10 lost+found/
-rw-rw-rw- 1 root root 0 Apr 21 2008 mb_collectionrevindex.mdb1
-rw-rw-rw- 1 root root 0 Apr 21 2008 mb_collectionrevindex.mdb1_stable_flag
-rw-rw-rw- 1 root root 0 Apr 21 2008 mb_collectionrevindex.mdb2
-rw-rw-rw- 1 root root 0 Apr 21 2008 mb_collectionrevindex.mdb2_stable_flag
-rw-rw-rw- 1 root root 0 Apr 21 2008 mb_collectionrevindex.mdbx
drwxrwxrwx 15 root root 4096 Jun 23 21:10 mnt/
drwxr-xr-x 4 root root 30 Jun 23 21:10 modules/
dr-xr-xr-x 105 root root 0 Jan 1 1970 proc/
drwx------ 3 root root 39 Jul 9 2008 root/
drwxr-xr-x 2 root root 4096 Mar 5 2008 sbin/
drwxr-xr-x 2 root root 6 Jan 25 2007 share/
drwxr-xr-x 10 root root 0 Jan 1 1970 sys/
lrwxrwxrwx 1 root root 8 Jun 23 21:10 tmp -> /mnt/ram/
drwxr-xr-x 11 root root 113 Nov 17 2006 usr/
drwxr-xr-x 14 root root 4096 Jun 23 21:11 var/
drwxr-xr-x 5 root root 61 Nov 1 2007 www/

[parnott]

portal_keystore.dat may not get created until you subscribe to a media feed. Don't know. On my NAS it has always been there with the same date/time created as license.dat.

Definitely don't put the appdata directory directly under /mnt. Directories directly under /mnt should only be used for mounting filesystems. /mnt is also probably in a partition that will not have enough room for the Twonky data. Have no idea what the /mnt/twonkymedia directory is doing there. Definitely something I would not expect to see, however it could have something to do with the way Twonky runs on the Linkstation. To find out what is mounted use- cat /etc/mtab

I think you want to relocate the appdata to a directory under /mnt/array1. I would create a new directory just so it is easy to find. Note- you will have to do this via Telnet, logged in as root, otherwise the permissions will be wrong.

The directories / and /root are not the same. / is the root directory of the entire filesystem. /root is the home directory for the root user, you can see it in the ls output you posted.

[turk]

I moved my appdata away from /var and to /mnt/array1. Not sure if I need to edit a script file or what to accomplish this:

Then in the command you use to start Twonky add the -appdata option followed by the path to the directory you just created.

I don't ever start Twonky, it starts with the boot of the NAS. Any hints on what I am looking for? Thanks

[parnott]

Sorry I meant to modify the Twonky startup script. Try looking for it in the /etc/init.d diectory. If that directory does not exist you will have to do some searching.

[turk]

I copied the whole init.d dir over to my share folder so I could open up the the files and look for anything referencing the path /var/twonkymedia/twonkymedia. Nothing so far. Do you know which file is the startup script? I started with the obvious: reboot.sh* and reboot_start.sh*, ....

Code: Select all

root@SAO_TERA:/etc/init.d# ls -alF
drwxr-xr-x    2 root     root         4096 Jul 21  2008 ./
drwxr-xr-x   21 root     root         4096 Jun 26 23:48 ../
-rwxr-xr-x    1 root     root         2587 May 10  2007 atalk.sh*
-rwxr-xr-x    1 root     root         1226 Apr  9  2007 bootcomplete.sh*
-rwxr-xr-x    1 root     root          773 Mar 14  2007 checkconfig.sh*
-rwxr-xr-x    1 root     root          965 Oct 17  2006 checkroot.sh*
-rwxr-xr-x    1 root     root          721 Nov  1  2006 clientUtil_servd.sh*
-rwxr-xr-x    1 root     root          333 Jan 25  2007 cron.sh*
-rwxr-xr-x    1 root     root          378 Jan 25  2007 daemonwatch.sh*
-rwxr-xr-x    1 root     root          816 Jan 25  2007 devpts.sh*
-rwxr-xr-x    1 root     root          599 Jan 18  2007 directcopy.sh*
-rwxr-xr-x    1 root     root          309 Oct 16  2006 diskmon.sh*
-rwxr-xr-x    1 root     root         1075 Nov 16  2006 down_lcd_led.sh*
-rwxr-xr-x    1 root     root          252 Oct 10  2006 drivecheck.sh*
-rwxr-xr-x    1 root     root          958 Oct 18  2006 epg.sh*
-rwxr-xr-x    1 root     root          514 Oct 26  2006 errormon.sh*
-rwxr-xr-x    1 root     root         1109 Jun  7  2006 ftpd.sh*
-rwxr-xr-x    1 root     root          152 Jan 25  2007 hotplug.sh*
-rwxr-xr-x    1 root     root         1179 Jan 16  2007 httpd.sh*
-rwxr-xr-x    1 root     root          417 Jan 25  2007 inetd.sh*
-rwxr-xr-x    1 root     root          695 Oct 19  2007 itunes.sh*
-rwxr-xr-x    1 root     root          494 Jun  8  2006 kernelmon.sh*
-rwxr-xr-x    1 root     root          445 Jan 25  2007 logchkd.sh*
-rwxr-xr-x    1 root     root           43 Oct 12  2006 logtag*
-rwxr-xr-x    1 root     root         1886 Nov 30  2006 lprng.sh*
-rwxr-xr-x    1 root     root          331 Jan 25  2007 lsprcvd.sh*
-rwxr-xr-x    1 root     root         1085 Dec 21  2006 ltbootd.sh*
-rwxr-xr-x    1 root     root          895 Nov  8  2006 micon_setup.sh*
-rwxr-xr-x    1 root     root          423 Nov 16  2006 miconmon.sh*
-rwxr-xr-x    1 root     root         1733 Apr 24  2007 module_loader.sh*
-rwxr-xr-x    1 nobody   nogroup      1530 Apr  6  2007 modules.sh*
-rwxr-xr-x    1 root     root          241 Jan 16  2007 mount_share.sh*
-rwxr-xr-x    1 root     root         4448 May  8  2007 networking.sh*
-rwxr-xr-x    1 root     root         4115 Sep  6  2007 pcastd.sh*
-rwxr-xr-x    1 root     root          554 Feb 10  2005 procps.sh*
-rwxr-xr-x    1 root     root          313 Jul 19  2007 rService*
-rwxr-xr-x    1 root     root          225 Jul 19  2007 rcDown*
-rwxr-xr-x    1 root     root         1361 Jun 20 02:37 rcS*
-rwxr-xr-x    1 root     root         1299 Jul 21  2008 rcS.bak*
-rwxr-xr-x    1 root     root         1346 Jun 20 02:36 rcS_old*
-rwxr-xr-x    1 root     root          161 Apr 19  2006 reboot.sh*
-rwxr-xr-x    1 root     root          347 Jul 27  2006 reboot_start.sh*
-rwxr-xr-x    1 root     root          579 Jan 31  2007 remove_appledb.sh*
-rwxr-xr-x    1 root     root         1107 May 10  2007 restore_config.sh*
-rwxr-xr-x    1 root     root           53 Jan 25  2007 save_config.sh*
-rwxr-xr-x    1 root     root          119 May 10  2007 sendsigs.sh*
-rwxr-xr-x    1 root     root         5828 Jan 25  2007 set_quota.sh*
-rwxr-xr-x    1 root     root          791 Jan 15  2007 sethostname.sh*
-rwxr-xr-x    1 root     root         1219 Jul 19  2007 shutdown_start.sh*
-rwxr-xr-x    1 root     root         4764 May 10  2007 smb.sh*
-rwxr-xr-x    1 root     root        11201 Jun  5  2007 start_data_array.sh*
-rwxr-xr-x    1 root     root         1270 Nov  1  2006 syslog.sh*
-rwxr-xr-x    1 root     root          119 Jun 23 20:33 twonky*
-rwxr-xr-x    1 root     root          131 Sep 29  2006 umount_disk.sh*
-rwxr-xr-x    1 root     root         3853 Feb 16  2007 ups*
root@SAO_TERA:/etc/init.d#

[parnott]

You won't find any direct reference to /var/twonkymedia/twonkymedia. This is just the default directory that is used when Twonky is started without the -appdata option.

However, /etc/init.d/twonky looks like the obvious candidate for the startup script.

NOTE- DO NOT edit this file from your PC with Notepad. It will be saved in an incorrect format for Linux and could cause your NAS to fail to boot.

You need to Telnet into your NAS and edit the file with a Linux text file editor. Most NAS's have vi, it is rather basic but does the job.