Hi all,

 

It has been some time since I have been on these forums, my 16TB UnRaid server (4.7) has been working perfectly for some time now, and is used daily.

 

This week however I add a Linn DS streamer to my AV systems, and it requires a uPnP server to serve it the audio files.

 

I have seen the instructions for using Mediatomb (here: http://lime-technology.com/forum/index.php?topic=3532.0) but daren't risk the data loss mentioned in that thread/guide.

 

So I have followed the Twonky Media install guide in the Wiki (here: http://lime-technology.com/wiki/index.php/Install_Twonky_Media_server), even though it seems quite out of date, but cannot get it to work. The Linn Kinksy ipad software can't see the server, and I can't access it via http://tower:9000 on my laptop.

 

Does anyone have any up to date instructions for getting a reliable uPnP server to work on UnRaid 4.7 without any risks of data loss?

 

Thanks in advance,

 

Gareth

Stupid question...  Is your server called "tower"?  Have you tried using the IP address of your server rather than the name?  (e.g. http://192.168.0.36:9000 - use the IP address of your server where I have used 192.168.0.36)

 

I use unRAID v5 now, and it's a long time since I put Twonky on the flash drive (mine is on the cache drive).  However, using Twonky version 6.0.39, I find it stable and reliable.  The link on the wiki page refers to a very old version.  See here if required...  http://www.twonkyforum.com/downloads/6.0.39/

Thanks I'll give that newer version of Twonky a go. Yes, I've tried using the IP address rather than 'Tower' but still no access.

 

Is the addition to the Go script still correct? (i.e. /boot/twonkymedia/twonkymedia) It doesn't need anything strange like a time delay to let the drives spin up or anything does it?

 

- Gareth

Drive spin up is not an issue.  All my drives are normally spun down, and only spin up when needed (applies to the cache drive that I use for Twonky and its database and to the data drives that have the audio files on them.)

 

You may need to look at the file that Twonky uses to store all of its configuration.  It is possible that it's pointing to some folders that may not exist for some files that it would use or create.  To be honest, it's a very long time since I set mine up.  I just take a look through the file called twonkymedia-server.ini and I check that any file locations are sensible.  If you edit it you must use a Linux friendly editor to avoid screwing up the new-line characters.  There are loads of parameters in that file that you probably should not change (Twonky have done a very poor job of documenting them).  The first step is generally to get the web interface working.  After that you can use the web interface to set up some details like the locations of your audio files.  Then you can go back to that file and change anything else that you may need, such as the database location.

 

When setting up, you will probably find that you need to kill the Twonky process before making changes to the ini file (I often just use a killall twonkymedia from the command line).  Then restart Twonky to assess the effect. 

Thanks I will take a look at it. TBH I haven't changed the .ini file from what is included in the .zip package included in the link in the How To.

 

All that is included in that .ini file is the following:

 

contentbase=/
contentdir=+A|/
followlinks=0
radio=0
readdbondemand=0
ignoredir=AppleDouble,AppleDB,AppleDesktop,TemporaryItems

 

What would I need to change here?

 

- Gareth

That looks like the file twonkymedia-server-default.ini

 

The file twonkymedia-server.ini gets set up with a large number of parameters when you first run (or attempt to run) the server.

Ah right, OK, I'll have to check that when I get home and report back.

Right, I managed to fix this. For come reason the addition to the go script wasn't working. I had to change it to the following:

 

./boot/twonkymedia/twonkymedia.sh start

 

I also changed the path on the flash drive from: /tower/flash/twonkyvision (as shown in the Wiki How-To) to:  /tower/flash/twonkymedia

 

I don't know which if the two changes fixed it, but the long and short of it is that it now works.

Certainly changing the path would make a difference.  Not sure what you had in your go script previously.

 

Also, I am not sure where your version stores it's database, possibly in a ram-disk (/etc/...).  Once you become more confident, you may want to consider moving the program off your flash drive, or perhaps moving its data to a hard drive location (cache is ideal, but can be on a share if needed).  That way, your flash gets written to less often and having the data on a hard drive might mean it does not need to be rebuilt each time you reboot the server.

 

Glad you got it working, anyway.