Bug 8965 – SqueezeCenter 'Cant drop table: rating'...

Bug 8965 - SqueezeCenter 'Cant drop table: rating'...

Summary:

SqueezeCenter 'Cant drop table: rating'...

Status:	NEW

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Database
Version:	7.4.0
Platform:	PC Other

Importance:	-- normal (vote)
Target Milestone:	8.0.0
Assigned To:	Andy Grundman

URL:
Keywords:	new_schema

Depends on:	8303
Blocks:
	Show dependency tree / graph

Reported:	2008-07-31 10:13 UTC by Matt Wise
Modified:	2009-09-08 09:28 UTC (History)
CC List:	4 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Matt Wise 2008-07-31 10:13:47 UTC

Seems like this comes up regularly... need to adjust the scripts to handle the database a bit better. 

2008-07-29 09:07:36 SqueezeCenter died. Restarting.
[08-07-29 09:08:03.4764] Slim::Utils::Misc::msg (1358) Warning:  
[09:08:03.4702] Use of uninitialized value in sprintf at /usr/share/ 
perl5/Slim/Utils/MySQLHelper.pm line 354.
[08-07-29 09:08:05.0738] DBIx::Migration::migrate (115) Warning:  
Database error: Can't DROP 'rating'; check that column/key exists at / 
usr/share/squeezecenter/CPAN/DBIx/Migration.pm line 115.
[08-07-29 09:08:05.0831] Slim::Schema::forceCommit (1483) Warning:  
Trying to commit transactions before DB is initialized!
2008-07-29 09:08:05 SqueezeCenter died. Restarting.
[08-07-29 09:08:31.1937] Slim::Utils::Misc::msg (1358) Warning:  
[09:08:31.1880] Use of uninitialized value in sprintf at /usr/share/ 
perl5/Slim/Utils/MySQLHelper.pm line 354.
[08-07-29 09:08:32.6521] DBIx::Migration::migrate (115) Warning:  
Database error: Can't DROP 'rating'; check that column/key exists at / 
usr/share/squeezecenter/CPAN/DBIx/Migration.pm line 115.
[08-07-29 09:08:32.6609] Slim::Schema::forceCommit (1483) Warning:  
Trying to commit transactions before DB is initialized!
2008-07-29 09:08:33 SqueezeCenter died. Restarting.

Comment 1 KDF 2008-07-31 11:27:22 UTC

falls into the rather sweeping scope of bug 8108

Comment 2 Blackketter Dean 2008-08-06 08:17:23 UTC

Andy: Any idea?  Is this a dup of bug 8108?

Comment 3 Andy Grundman 2008-08-06 08:18:54 UTC

The error in bug 8101 is different so I'd say no.

Comment 4 Blackketter Dean 2008-08-06 12:05:59 UTC

7.2 bug?

Comment 5 Andy Grundman 2008-08-06 12:14:32 UTC

Can we reproduce?

Comment 6 Michael Herger 2008-08-07 05:01:48 UTC

*** Bug 9063 has been marked as a duplicate of this bug. ***

Comment 7 James Richardson 2008-08-21 13:24:48 UTC

Is bug 8108 related to this issue, just reported a different way?

Comment 8 James Richardson 2008-11-05 11:48:14 UTC

Matt: can you please re-try this on the latest 7.2.1.  If you are still able to see this error, please include reproduction steps.

Comment 9 Matt Wise 2008-11-05 11:52:40 UTC

I havn't seen that particular message come up... but the point of the bug is to make SqueezeCenter handle DB failures better primarily.

Comment 10 James Richardson 2008-11-07 09:33:17 UTC

Brandon: assuming there will be database corruption with new_schema, will there be an automatic way to handle these errors?

Comment 11 Blackketter Dean 2008-11-23 15:06:32 UTC

If this is new_schema, then it should be targetted to 8.0

Comment 12 Matt Wise 2009-06-30 13:19:39 UTC

How is this handled with the new sqllite stuff in 7.4? If the database is corrupted does SC at least start up now?

Comment 13 Andy Grundman 2009-07-29 14:58:38 UTC

Moving 7.4 bugs to 8.0.