Twonky Forum

Hi
I'm running 5.1.2 on my D-link DNS 323 and haven't tried any other version. When I restart media server, The DB totaly rebuild. I'm not shore that should be the way or is it?

No. The database should not be rebuilt every time.

- Rick

Hi

What to do then?

/Dick

You might want to try disabling auto-rescan. IF that doesn't work, you might have to wait for a firmware update with a new server build. I'm not a server expert however, there are people here who might have a better suggestion.

- Rick

Also on a Qnap NAS, with pre-installed TMS 5.1.2, the database is totally rebuild after every server re-start.

I'll make sure our developers are aware of this. Thanks.

- Rick

Thank you for your reports.
So far we could not reproduce this problem here.

Could you elaborate how you identified, that the server rebuild the complete database compared to doing just a rescan?

Best regards,

René

I'll give it a try.

When I press "Restart Server" the same happens when I press "Rebuild database".
On the "Server status" page the Chached Memory for my database is about 2100KB with approx. 5400 Music tracks.
After pressing "Restart Server" both numbers are reset, meaning Chached Memory starts with approx. 230KB and Music Tracks start with 0 (zero). At "Last database change" the directory names appear with a + sign before it. After a few minutes the scanning process is completed.

This whole process happens after each change that needs a server restart.

Each time when the server is restarted, all marks before all mediaplayers are lost (blanks) and I also have to mark my mediaplayer again for sharing.

Addition to above: When I press "Reset network clients" (make the list of mediaplayers empty) then also the database is rebuild (the same happened as described above).

I have change to 5.1.3-dev version and the application behave as it did before, no changes!

I'll have the same problem with Media Server 5.1.3. Everytime I restart the server the database is rebuild. With my music-library it needs more than 3hours to collect all data.
And everytime I start the computer the database is rebuild again
The cache memory size has to be build up to nealy 71000KB and the rebuild gets slower and slower the more data the server has scanned.
I can see that in the Server Status window.
This happens with Windows7 64Bit, 8GByte of RAM and Media Manager Version 1.3.1.25
If this can't be repaired, TwonkyMedia isn't usable for me.

I can't confirm this (Version 5.1.3-dev ) - a server restart simply issues a rescan, but the Database is not rebuild (about 11.000 media files) - running the server on a Thecus N7700 NAS
br
Peter

Hi

Restarting 5.0.68 triggers a rescan of the content directories if the resecan is set to -1 (i.e. set to monitor for changes), but this can be prevented by setting the rescan time to 0.

Irrespective of the rescan setting (mine is always set to 0 anyway) all versions of 5.1.2 and 5.1.3 that I've tried on my ReadyNAS kick off a full database delete and rebuild whenever you restart Twonky. I've also had it confirmed (by other forum users) as happening on other devices (including a Thecus 5200). I've reported this and I'm told that it will hopefully be fixed in the next release.

If you only have a small quantity of media files, it's probably not an issue (it'll all happen very quickly anyway). I now have 25,500 FLAC files and it takes 50 minutes, but as I leave my NAS on all the time, it's not an issue for me either. That said, a surprisingly large quantity of people switch their NAS off when not in use, and if they have anything more than very small media collections, it'll be a total 'show stopper' for them (in my case, it would be 50 minutes before I could play my music) and thus it'll be great when this has been resolved.

Bri

Hi,

same here, just upgraded my Buffalo LinkStation Pro (V2) from 4.4.6 - which was running perfectly - to 5.1.3-dev.
Every time I start my LinkStation it completely rebuilds the data base (around 16000 files) which takes approx. 17 minutes.

Additionally I cannot restart the Twonky Server as it leaves a zombie process; even manually killing the processes and starting it from a telnet shell (putty) creates nothing but zombie processes - one every minute. So after every configuration change I have to restart the LinkStation itself.

Cheers,

Martin