2015/02/24: I think I’ve finally figured out how to get Twonky working in a stable fashion, so I’ve written up my findings in a
I foolishly unplugged my 4TB MyCloud last night, in order to sort out power leads etc. [I’m of the opinion that, since mains power isn’t always guaranteed, even in first world countries, systems **_ought_** to cope with sudden loss of power, or be able to tidy up the ensuing mess automatically]
On re-booting, the NAS took a while, so I used the Dashboard to see what was going on. It was okay, but I spotted a pending firmware upgrade, so I installed that and let it re-boot again.
Now, coincidentally to the upgrade, or the power cycle, the Twonky server started playing up, reporting an error 400162.
After trying the usual suspects of shutting Twonky down, re-building, re-scanning, re-starting, etc, to no avail, I found this suggestion:
Si I installed PuTTY, shut down Twonky, enabled SSH access, logged in to the Linux as root, and found that there was no twonky.db as suggested. But there was a db directory, so I moved that and db.info into a backup directory, and re-started Twonky. It still seemed to be having trouble.
After much experimentation, I enabled loging in Twonky’s dashboard, and found that it had stopped reading the twonkyserver.ini file, reporteing an error, identical to the one found here:
[Error] - LOG_SYSTEM: upnp_multiuser_load : load user-db from twonky.users: failed
By this time, I was getting somewhat fed up with rubbish software that cannot sort itself out, so I did a trash & burn on all the obvious configuration files
[shut down media streaming in WD Dashboard]
rm -f -R db
rm -f db.info
rm -f twonky-locations-70.db
rm -f twonkyserver.ini
[restart media streaming]
This has stopped the error as Twonky starts up, and it appears to be re-building the database correctly again.
Having trashed the .ini file, I obviously had to re-do all the Twonky settings.
For any WD employees monitoring these forums:
I’d suggest adding a ‘trash & burn all Twonky settings & database and re-start from fresh’ button, as neither Twonky or the WD Dashboard were able to fix this problem. Or discuss the issue with PacketVideo Corp, and come up with a user-friendly solution. Systems shouldn’t be corrupted by sudden loss of power, or they should recover on their own. Users shouldn’t have to resort to root access to the server operating system, nor destroy files to fix problems.
Maybe I’ll just ditch Twonky (as it seems appallingly slow to serve media; so much so that MediaConnect on the iPad and MediaMonkey on Android both timeout, Kinsky on the PC is more patient) and go install MiniDLNA in its place: