Bugzilla – Bug 2606
live365 stops slimserver
Last modified: 2008-09-15 14:38:10 UTC
after a day or so of playing one station of live365, slimsever stops and the only way to get back into slimserver internet radio live365 on my squeeze box2 is to reboot my computer. below is the event viewer report. Event Type: Error Event Source: Application Event Category: None Event ID: 0 Date: 11/20/2005 Time: 1:10:36 AM User: N/A Computer: BOX Description: The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Can't use an undefined value as a HASH reference at C:/Program Files/SlimServer/server/Plugins/Live365/Plugin.pm line 732. . this also shows up before it crashes but i'm not sure if it's related or not. Event Type: Error Event Source: TrueVector Service Event Category: None Event ID: 5007 Date: 11/16/2005 Time: 1:41:31 AM User: N/A Computer: BOX Description: TrueVector engine: File "C:\WINDOWS\Internet Logs\BOX.ldb" was corrupt and has been copied to "C:\WINDOWS\Internet Logs\xDB4.tmp". File "C:\WINDOWS\Internet Logs\BOX.ldb" was corrupt and has been deleted.
Michael - any thoughts on this?
Dan, I'm sorry, I never touched Live365. But I did a quick google research for the other problem. I found many references where Zone Alarm killed XP with that message. If that error always occurs just before the slimserver crash, I could imagine it's rather a ZA problem than slimserver related. And if the firewall is locked up, slimserver might really have a problem streaming internet radio. I wouldn't see a reason how slimserver could lock up completely. But I can imagine a firewall being being overloaded by constant streaming. Just an idea: disable ZA, enable the XP firewall and see, wether the behaviour is still reproducable.
I've just checked in a possible fix for this as change 5924 Will be in the 2006-01-29 nightlies. Please let me know if you see it anymore. Thanks