Page 1 of 1
Configuration Changes are lost on Server restart on DNS-323
Posted: Thu Apr 23, 2009 3:47 am
by vifa84
I am having a problem with saving the configuration. For some reason any changes I make, including entering the license key are lost when I reboot the server. Is there a way to enter the license manually so it doesn't get lost?
Re: Configuration Changes are lost on Server restart on DNS-323
Posted: Tue Apr 28, 2009 11:39 am
by s4mb4
are you running version 5.x?
Re: Configuration Changes are lost on Server restart on DNS-323
Posted: Tue Apr 28, 2009 10:18 pm
by vifa84
s4mb4 wrote:are you running version 5.x?
5.0.55 which is the latest one for the 323, i think.
Re: Configuration Changes are lost on Server restart on DNS-323
Posted: Thu Apr 30, 2009 12:47 pm
by s4mb4
its some whacky bug. it also happens to me on my terastation Pro.
Re: Configuration Changes are lost on Server restart on DNS-323
Posted: Wed May 13, 2009 7:55 am
by peterfu
The ini file seems to be in a place on Your NAS, which is cleared upon reboot. This should be corrected in the startup procedure of the server by adding the parameter "-inifile <full qualified place of ini file>" to the twonkyserver startup command.
br
Peter
Re: Configuration Changes are lost on Server restart on DNS-323
Posted: Wed Sep 16, 2009 7:49 am
by BigPun1705
Hello,
I have the same problem.
In which file and position of the file should "-inifile <full qualified place of ini file>" be written?
THX
Re: Configuration Changes are lost on Server restart on DNS-323
Posted: Sun Nov 15, 2009 2:22 am
by torbuk
I am also having this same problem with version 5.0.68. Every time I reboot my DNS-323, I lose the registration setting (I have to re-enter the registration key). Can anyone explain in some basic steps how to add the parameter "-inifile <full qualified place of ini file>" to the twonkyserver startup command?
I'll buy anyone a beer that can help me out...
Re: Configuration Changes are lost on Server restart on DNS-323
Posted: Wed Jan 06, 2010 7:02 am
by maxharp3r
Thanks all. Using the -inifile parameter works for me (using v 5.1).
torbuk: There's a file called "starttwonky.sh" that you put on your DNS-323 as part of the install process. This file is run whenever the DNS-323 is rebooted. Edit the file so that the line that currently reads:
becomes:
Code: Select all
/mnt/HD_a2/twonky/twonkymedia -inifile /mnt/HD_a2/twonky/twonkymedia-server.ini &