Bugzilla – Bug 4439
Slimserver application crash
Last modified: 2006-11-01 16:21:35 UTC
Slimserver crash with the following message in the Event Viewer: Event Type: Error Event Source: Application Event Category: None Event ID: 0 Date: 10/29/2006 Time: 2:59:27 PM User: N/A Computer: MEDIACENTER 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: Carp::Clan::__ANON__(): Error executing 'UPDATE tracks SET lastplayed = ?, playcount = ? WHERE ( id = ? )': DBD::mysql::st execute failed: Lock wait timeout exceeded; try restarting transaction at C:\Program Files\SlimServer\server\CPAN/DBIx/Class/Storage/DBI.pm line 771. . Windows XP SP2 SlimServer Version: 6.5.1 - 10464 - Windows XP - EN - cp1252 Let me know what other info I can provide. y.
see bug 4423, as it is essentially the same thing. What were you doing on the computer at the time? Is anything else running that might be locking the database? In order to keep this stuff more focussed, this should really be merged with bug 4423, and the summary changed there to reflect any growing scope.
(In reply to comment #1) > see bug 4423, as it is essentially the same thing. What were you doing on the > computer at the time? Is anything else running that might be locking the > database? > > In order to keep this stuff more focussed, this should really be merged with > bug 4423, and the summary changed there to reflect any growing scope. > It does look like the same bug. At any given time I have many apps running: MS Outlook, Avast Anti-Virus, MusicIP mixer; Azureus; and Diskkeeper (defrag utility). Perhaps it was Diskeeper? It runs in "smart mode" supposedly only defragging during idle time.
Thanks Yann. I'm going to merge this. If you see the crash again, see if you can confirm the cause by checking the task manager or a status log for diskkeeper to see if it was accessing the mysql data area at the time. Any comments that you can add to bug 4423 may help. *** This bug has been marked as a duplicate of 4423 ***