Recently with SC 7.4, I've experienced crashes within the scanner. Sadly, the scanner trace logging messages don't report the track that causes the error, so with default trace, there is no idea what causes the crash.
[21:44:43.1903] Slim::Schema::Storage::throw_exception (70) Error: Error executing 'INSERT INTO tracks (audio, audio_offset, audio_size, bitrate, block_alignment, content_type, drm, filesize, lossless, musicbrainz_id, remote, replay_gain, replay_peak, samplerate, secs, tagversion, timestamp, title, titlesearch, titlesort, tracknum, url, year) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)': DBD::mysql::st execute failed: Data too long for column 'musicbrainz_id' at row 1 at P:\Music\SlimServer\trunk\server\CPAN/DBIx/Class/Storage/DBI.pm line 771. [21:44:43.1911] Slim::Schema::Storage::throw_exception (70) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (P:/Music/SlimServer/trunk/server/Slim/Schema/Storage.pm line 70) frame 1: Slim::Schema::Storage::throw_exception (P:\Music\SlimServer\trunk\server\CPAN/DBIx/Class/Storage/DBI.pm line 773) frame 2: DBIx::Class::Storage::DBI::_execute (P:\Music\SlimServer\trunk\server\CPAN/DBIx/Class/Storage/DBI.pm line 788) frame 3: DBIx::Class::Storage::DBI::insert (P:\Music\SlimServer\trunk\server\CPAN/DBIx/Class/Row.pm line 75) frame 4: DBIx::Class::Row::insert (P:\Music\SlimServer\trunk\server\CPAN/DBIx/Class/PK/Auto.pm line 43) frame 5: DBIx::Class::PK::Auto::insert (P:\Music\SlimServer\trunk\server\CPAN/DBIx/Class/ResultSet.pm line 1335) frame 6: DBIx::Class::ResultSet::create (P:/Music/SlimServer/trunk/server/Slim/Schema.pm line 924) frame 7: Slim::Schema::newTrack (P:/Music/SlimServer/trunk/server/Slim/Schema.pm line 1140) frame 8: Slim::Schema::updateOrCreate (P:/Music/SlimServer/trunk/server/Slim/Utils/Scanner.pm line 336) frame 9: Slim::Utils::Scanner::scanDirectory (P:/Music/SlimServer/trunk/server/Slim/Music/MusicFolderScan.pm line 79) frame 10: Slim::Music::MusicFolderScan::startScan (P:/Music/SlimServer/trunk/server/Slim/Music/Import.pm line 494) frame 11: Slim::Music::Import::runImporter (P:/Music/SlimServer/trunk/server/Slim/Music/Import.pm line 323) frame 12: Slim::Music::Import::runScan (P:/Music/SlimServer/trunk/server/scanner.pl line 247) frame 13: (eval) (P:/Music/SlimServer/trunk/server/scanner.pl line 241) frame 14: main::main (P:/Music/SlimServer/trunk/server/scanner.pl line 387) [21:44:43.1923] main::main (253) Error: Failed when running main scan: [Carp::Clan::__ANON__(): Error executing 'INSERT INTO tracks (audio, audio_offset, audio_size, bitrate, block_alignment, content_type, drm, filesize, lossless, musicbrainz_id, remote, replay_gain, replay_peak, samplerate, secs, tagversion, timestamp, title, titlesearch, titlesort, tracknum, url, year) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)': DBD::mysql::st execute failed: Data too long for column 'musicbrainz_id' at row 1 at P:\Music\SlimServer\trunk\server\CPAN/DBIx/Class/Storage/DBI.pm line 771. ] [21:44:43.1927] main::main (254) Error: Skipping post-process & Not updating lastRescanTime! I turned info level tracing on for database.info to try to find an indication of what file was causing the crash, and I think I've identified the file. I've checked the tags and it looks perfectly fine. No musicbrainz tags. I think some extra resilience in the scanner is required to log problematic file names, continue and report the problem files (maybe to a new log file, with a link in the scan results). Phil _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
