Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi All,
I just got my DNS-323 a few days ago and installed fun_plug and the Twonky media server. I tested out the setup before starting to move massive amounts of files over and everything seemed great, however, somewhere along the line strange stuff started happening. First sshd wouldn't start automatically on a reboot, then I couldn't access my mapped drives through windows, and finally the hard disk LEDs would blink pink. Looking at the log files sshd said it wouldn't start because of bad permissions on various keys (which was true, they were set to 422, which they hadn't been on installation). I started a fresh install and everything seemed to go back to normal for a time, but then at some point the problem would re-occur.
I then noticed Twonky took quite a bit of CPU time every time I restarted. It also seemed liked adding media files to Twonky precipitated all the problems. Finally I noticed the Twonky database files are stored in /var/twonkymedia/. I believe the /var directory is stored in RAM or something, meaning any changes to this directory are not saved. This would cause Twonky to rebuild its db upon reboot. The size of this RAM drive also seems to be rather small, so while Twonky would work in my test setup with just a few files to index, when I'd copy over my full library the root filesystem diskspace would be completely consumed.
So a couple of questions...
Is it possible the pink LED phenomenon is caused by the root filesystem being full?
I'm using twonky dns323-5.0.65. This seemed to be the latest version I could find. Is this the latest one? Perhaps this issue is fixed in another version.
Is there somewhere in Twonky to change the default path for its database? I took a quick look around and couldn't find anything.
Offline
Likely that your blinking LED is because of twonky filling up your /var directory with loads of crap. Standard /var is RAM.
I'm starting twonky with a specific ini file that allows to redirect all your paths to whereever you like.
My startup script has a line like this:
/pathtoyoutwonky/twonkymedia -inifile /pathtoyourtwonky/twonkymedia-server.ini &
My ini file looks like this. It assumes you've got a fun_plug standard installation under /ffp. Password, user and share paths etc have been removed. You need to change to edit to reflect yours (or let twonky do the job via web interface etc.)
This also works arround some issues I had to have twonky remembering some settings being made to it through runtime.
#! TwonkyVision ini file / charset UTF-16
#! change settings by commandline or by editing this file
#! version 5.0.65
[main]
# accessuser
accessuser=
# accesspwd
accesspwd=
# autotree
autotree=3
# cachedir
cachedir=/ffp/var/twonkymedia/db/cache
# cachemaxsize
cachemaxsize=
# Registration key
cdkey=
# clearclientsonrestart
clearclientsonrestart=0
# Enable sharing for new media receivers automatically
clientautoenable=1
# codepage
codepage=932
# compilationsdir
compilationsdir=Compilations,Sampler
# contentbase
contentbase=/mnt/somewhere/blablabla
# Content Locations
contentdir=+P|/blalblapics,-A|/p,+A|/blabla/movies,-A|/blabla/music
# dbdir
dbdir=/ffp/var/twonkymedia/db
# dyndns
dyndns=
# enableweb
enableweb=2
# followlinks
followlinks=1
# Server name
friendlyname=Twonky DNS-332
# HTTP Server Port
httpport=9000
# httpremoteport
httpremoteport=
# ignoredir
ignoredir=AppleDouble
# ip
ip=
# ituneslib
ituneslib=
# Language
language=en
# rtpport
rtpport=
# Restart on NIC changes
nicrestart=0
# platform
platform=DNS323
# Rescan in minutes
scantime=-1
# startupmb
startupmb=0
# streambuffer
streambuffer=16384
# enable upload
uploadenabled=1
# uploadmusicdir
uploadmusicdir=/ffp/var/twonkymedia/twonkymedia-server-uploaded-music
# uploadpicturedir
uploadpicturedir=/ffp/var/twonkymedia/twonkymedia-server-uploaded-pictures
# uploadvideodir
uploadvideodir=/ffp/var/twonkymedia/twonkymedia-server-uploaded-videos
# onlinedir
onlinedir=/ffp/var/twonkymedia/twonkymedia-server-online-data
# v
v=0
# webnodes
webnodes=MPV
# webpicturenum
webpicturenum=0
# mediastatisticsenabled
mediastatisticsenabled=0
# mediastatisticsdir
mediastatisticsdir=/ffp/var/twonkymedia/media-statistics/
# defaultview
defaultview=advanceddefault
Offline
Hi Kai,
Thanks for the response. I solved the problem by moving the twonky data files to a more permanent location and creating a symbolic link in the /var directory in a startup script. Your solution seems somewhat more elegant... maybe I should have read through the twonky forums I think I'll go set up a custom ini file now.
Offline