Twonky server keeps crashing

[phred]

I got the 6.0.1 Twonky server installed on my WHS serving a well organized collection of MP3s to my Roku clients around the house. Unfortunately the server crashes several times a day causing a high CPU load when scanning through the files.

In my WHS event viewer I find a lot of these messages:

Code: Select all

Faulting application TwonkyMediaServer.exe, version 0.0.0.0, faulting module TwonkyMediaServer.exe, version 0.0.0.0, fault address 0x0003cd65.

I'm a newbie configuring Twonky so I hope someone can point me in the right direction of where to look.

TIA!

[Twonky_Rick]

Seems like it might be getting stuck on a corrupted media file. There are some suggestions on how to locate these files here: http://www.mediasmartserver.net/2010/03 ... 0-patch-2/

I've also used MP3 file scanners in the past that can identify and in some cases patch corrupted files. I don't remember their names however.

- Rick.

[phred]

Seems like it might be getting stuck on a corrupted media file. There are some suggestions on how to locate these files here: http://www.mediasmartserver.net/2010/03 ... 0-patch-2/

I've also used MP3 file scanners in the past that can identify and in some cases patch corrupted files. I don't remember their names however.

- Rick.

I tried the Handle solution you suggested and got this result:

Code: Select all

C:\Documents and Settings\Administrator\Desktop>handle -p twonky

Handle v3.42
Copyright (C) 1997-2008 Mark Russinovich
Sysinternals - www.sysinternals.com

------------------------------------------------------------------------------
twonkymediaserverwatchdog.exe pid: 1668 NT AUTHORITY\SYSTEM
   18: File  (RW-)   C:\WINDOWS\system32
   5C: File  (RW-)   C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.37
90.3959_x-ww_D8713E55
------------------------------------------------------------------------------
twonkymediaserverconfig.exe pid: 3316 WHS\Administrator
   18: File  (RW-)   C:\Program Files\TwonkyMedia
   5C: File  (RW-)   C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.37
90.3959_x-ww_D8713E55
   98: Section       \Sessions\1\BaseNamedObjects\CiceroSharedMemDefaultS-1-5-21-1911054772-20683884
-2551100552-500
   D0: Section       \Sessions\1\BaseNamedObjects\CTF.TimListCache.FMPDefaultS-1-5-21-1911054772-206
83884-2551100552-500SFM.DefaultS-1-5-21-1911054772-20683884-2551100552-500
  178: Section       \Sessions\1\BaseNamedObjects\MSCTF.Shared.SFM.ANM
  194: Section       \Sessions\1\BaseNamedObjects\MSCTF.Shared.SFM.AFGB
------------------------------------------------------------------------------
twonkymediaserver.exe pid: 3540 NT AUTHORITY\SYSTEM
   18: File  (RW-)   C:\WINDOWS\system32
   8C: File  (RW-)   C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.37
90.3959_x-ww_D8713E55
  120: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\TwonkyMediaSer
ver-log.txt
  1E4: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\1.tms.dat
  1E8: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\1.tms.dat
  1F4: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\3.tms.dat
  1F8: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\2.tms.dat
  228: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\10.tms.dat
  240: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\2.tms.dat
  254: File  (RWD)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db
  258: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\twonky_db_b
ackup.import.items
  27C: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\3.tms.dat
  280: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\5.tms.dat
  284: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\6.tms.dat
  28C: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\7.tms.dat
  298: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\7.tms.dat
  29C: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\4.tms.dat
  2A0: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\4.tms.dat
  2A4: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\5.tms.dat
  2A8: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\6.tms.dat
  2B0: File  (RW-)   C:\Documents and Settings\All Users\Application Data\TwonkyMedia\db\10.tms.dat

C:\Documents and Settings\Administrator\Desktop>

From what I understand when reading the log Handle doesn't find any corrupt file (pls correct me if I'm wrong!).

Since Twonky server crashes after different up-times I don't think the crash is caused by a single corrupted file (if so, it should crash at the same file again and again?!).

I'll do some research for apps finding corrupt MP3s.

[Twonky_Rick]

A new version of TwonkyServer was recently posted here: http://www.twonky.com/support/downloads.aspx

Can you make sure you're running that?

Installation instructions can be found here if you need them. Make sure to do a clean install and not preserve settings if asked.
http://www.twonkyforum.com/viewtopic.php?f=2&t=8233

- Rick

[phred]

A new version of TwonkyServer was recently posted here: http://www.twonky.com/support/downloads.aspx

Can you make sure you're running that?

Great!

I upgraded to the latest version and the server has now been running for over 50 hrs without a crash! Also, the CPU usage has dropped from 50% continuously to about 1-2%. One other change: the cache memory usage has almost doubled and is now 166272 KB (but i can live with that..).

Tnx Rick!

[Twonky_Rick]

Thanks for reporting this. Fortunately we're aware of the cache memory problem. We'll be posting a new server release on Twonky.com in the next 2 weeks. I'm not 100% sure the fix is in that release, but it's worth trying. If it's not in that release it will be in 6.1, which is scheduled for a Nov. release.

- Rick