Server does a rescan of the media files after server restart

[mr420]

Hi,

I have a problem with the TwonkyMedia Server 6.0.39. Everytime I restart my server, twonky re-scans my media content, which takes about 20 minutes.

My Hardware: WHS Acer H340.

I also tried to recreate the database but it does not help. My rescan option is set to -1.

I also tried a reinstall of Twonky but it did not help.

Any suggestions? Regards, Sören

[phibertron]

The rescan you are refering to, I assume is "scantime="
Does not pertain to startup scanning,
It is for finding new content while running

There is nothing we can do about that behavior at present
nor have I found any way to make it stop
However I also use Twonky on WHS, but on an HP box
For me to reboot the thing is not very frequent, mostly have to for patches etc.
In which case the rescan on startup isnt too bad of an issue at present

[mr420]

Thanks for your replay, you are right for restart only it is not really a problem because, I usually just do a restart after windows updates. But, the problem also occurs after the server was in sleep mode. I configured the server, to go to sleep as soon as no other device is active in the network (this can happen a couple of times a day). The problem is, coming up from sleep the TwonkyServer service does not start again. I am using the "Light out Plugin" and I configured Light out to start the service after a sleep period again.
The Problem is, Twonky is coming up again, but always does a rescan of the media. This looks like a bug to me.

[phibertron]

Ahh I see th problem, ouch!
I actually stopped putting my server to sleep a long time ago
it sips power as it is, and the wake up process has its caveats

Sadly, Twonky does not view the rescan as a bug, they see it as needed
I think I know why they do it, which is to do a verify and discover
of existing content in there DB and any new media at the same time

But yeah, it should be user configurable as on whether to do it or not
of which it is not, will they ever add this feature, who knows...