I recently restarted my SBS and found it would not start. The SBS log says: [11-02-27 23:05:54.5459] main::init (323) Starting Squeezebox Server (v7.5.2, r31632, Mon Dec 13 14:08:06 MST 2010) perl 5.012003 [11-02-27 23:05:54.7278] Slim::Music::TitleFormatter::init (42) Warning: DBIx::Class::Row::throw_exception(): Inconsistent hierarchy during C3 merge of class 'Slim::Schema::DBI': current merge results [ Slim::Schema::DBI, DBIx::Class::UTF8Columns, ] merging failed on 'DBIx::Class::PK::Auto' at /usr/lib/perl5/5.12.3/i686-linux/mro.pm line 27. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.12.3/Class/C3/Componentised.pm line 147. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.12.3/Class/C3/Componentised.pm line 147. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.12.3/Class/C3/Componentised.pm line 147. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.12.3/Slim/Music/TitleFormatter.pm line 42. Rebuilt perl, Ran perl-cleaner -all (246 packages rebuilt): No luck. From message suspected DBI packages or C3 packages. Downgraded to Class-C3-Componentised-1.0.600 and SBS seems to work OK, but the log now shows many instances of: [11-02-27 23:09:40.5155] main::init (323) Starting Squeezebox Server (v7.5.2, r31632, Mon Dec 13 14:08:06 MST 2010) perl 5.012003 [11-02-27 23:09:41.1779] Slim::Schema::throw_exception (303) Error: Unable to uniquely identify row object with missing PK columns: id [11-02-27 23:09:41.1783] Slim::Schema::throw_exception (303) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Schema.pm line 303) frame 1: Slim::Schema::throw_exception (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Row.pm line 1351) frame 2: DBIx::Class::Row::throw_exception (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/PK.pm line 47) frame 3: DBIx::Class::PK::_ident_values (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Relationship/Accessor.pm line 59) frame 4: DBIx::Class::Relationship::Accessor::__ANON__ (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/InflateColumn.pm line 108) frame 5: DBIx::Class::InflateColumn::_deflated_column (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Row.pm line 601) frame 6: DBIx::Class::Row::get_column (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/UTF8Columns.pm line 68) frame 7: DBIx::Class::UTF8Columns::get_column (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSource.pm line 1361) frame 8: DBIx::Class::ResultSource::_resolve_condition (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Relationship/Base.pm line 207) frame 9: (eval) (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Relationship/Base.pm line 207) frame 10: DBIx::Class::Relationship::Base::related_resultset (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Row.pm line 1123) frame 11: DBIx::Class::Row::inflate_result (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSet.pm line 973) frame 12: DBIx::Class::ResultSet::_construct_object (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSet.pm line 1348) frame 13: DBIx::Class::ResultSet::all (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSet.pm line 248) frame 14: DBIx::Class::ResultSet::search (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSet.pm line 912) frame 15: DBIx::Class::ResultSet::slice (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Queries.pm line 516) frame 16: Slim::Control::Queries::albumsQuery (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Request.pm line 1941) frame 17: (eval) (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Request.pm line 1941) frame 18: Slim::Control::Request::execute (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Request.pm line 880) frame 19: Slim::Control::Request::executeRequest (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Jive.pm line 191) frame 20: Slim::Control::Jive::buildCaches (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Jive.pm line 165) frame 21: Slim::Control::Jive::init (/usr/sbin/squeezeboxserver line 511) frame 22: main::init (/usr/sbin/squeezeboxserver line 579) frame 23: main::main (/usr/sbin/squeezeboxserver line 1073) I cannot tell if this is a new phenomina or has been that way, however SBS seems to be working, but I notice that the init script has problems (even after zapping) actually stopping SBS. Reproducible: Always Steps to Reproduce: 1. The Class-C3 issue is repeatable 2. 3. Actual Results: See above Expected Results: Normal operation.
1) dev-perl/Class-C3-Componentised-1.0.700 is already gone. 1.0.800 is in the tree and should work with SBS. 2) Do you have dev-perl/DBIx-Class-0.08120 installed?
Yes, >dev-perl/DBIx-Class-0.08120 >dev-perl/Audio-Scan-0.82 in package.mask
This looks identical to the very recent bug 356607. Can you take a look at this bug (https://bugs.gentoo.org/show_bug.cgi?id=356607)? The reporter of that bug had success eventually with dev-perl/Class-C3-Componentised-1.0.800. Report back if installing this version fixes things.
Yes, SBS works with dev-perl/Class-C3-Componentised-1.0.800, so feel free to close the bug with my thanks. I am not sure what the log file full (yes there are very many like this one) of DBIx errors is about, or what - if any - impact these have. From what I see in logrotate archives, these messages have been happening for a while. [11-02-28 08:20:48.6933] main::init (323) Starting Squeezebox Server (v7.5.2, r31632, Mon Dec 13 14:08:06 MST 2010) perl 5.012003 [11-02-28 08:20:50.3939] Slim::Schema::throw_exception (303) Error: Unable to uniquely identify row object with missing PK columns: id [11-02-28 08:20:50.3943] Slim::Schema::throw_exception (303) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Schema.pm line 303) frame 1: Slim::Schema::throw_exception (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Row.pm line 1351) frame 2: DBIx::Class::Row::throw_exception (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/PK.pm line 47) frame 3: DBIx::Class::PK::_ident_values (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Relationship/Accessor.pm line 59) frame 4: DBIx::Class::Relationship::Accessor::__ANON__ (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/InflateColumn.pm line 108) frame 5: DBIx::Class::InflateColumn::_deflated_column (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Row.pm line 601) frame 6: DBIx::Class::Row::get_column (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/UTF8Columns.pm line 68) frame 7: DBIx::Class::UTF8Columns::get_column (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSource.pm line 1361) frame 8: DBIx::Class::ResultSource::_resolve_condition (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Relationship/Base.pm line 207) frame 9: (eval) (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Relationship/Base.pm line 207) frame 10: DBIx::Class::Relationship::Base::related_resultset (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/Row.pm line 1123) frame 11: DBIx::Class::Row::inflate_result (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSet.pm line 973) frame 12: DBIx::Class::ResultSet::_construct_object (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSet.pm line 1348) frame 13: DBIx::Class::ResultSet::all (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSet.pm line 248) frame 14: DBIx::Class::ResultSet::search (/usr/lib/perl5/vendor_perl/5.12.3/DBIx/Class/ResultSet.pm line 912) frame 15: DBIx::Class::ResultSet::slice (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Queries.pm line 516) frame 16: Slim::Control::Queries::albumsQuery (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Request.pm line 1941) frame 17: (eval) (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Request.pm line 1941) frame 18: Slim::Control::Request::execute (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Request.pm line 880) frame 19: Slim::Control::Request::executeRequest (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Jive.pm line 191) frame 20: Slim::Control::Jive::buildCaches (/usr/lib/perl5/vendor_perl/5.12.3/Slim/Control/Jive.pm line 165) frame 21: Slim::Control::Jive::init (/usr/sbin/squeezeboxserver line 511) frame 22: main::init (/usr/sbin/squeezeboxserver line 579) frame 23: main::main (/usr/sbin/squeezeboxserver line 1073)
Thanks! Closing, but... Stuart, can you see if the error/backtrace attached rings any bells and if we need to look into it? *** This bug has been marked as a duplicate of bug 356607 ***
Yes, the log entries in comment#4 have been happening forever. I'd like to know what causes them but I've never been able to track it down - I suspect it's something DBIx-related, but it's very hard to get to the bottom of. As far as I've ever been able to tell they are completely harmless, but I know it's not ideal that it's pouring this stuff into the log. (In reply to comment #5) > Thanks! Closing, but... > > Stuart, can you see if the error/backtrace attached rings any bells and if we > need to look into it? > > > *** This bug has been marked as a duplicate of bug 356607 *** >