Bugzilla – Bug 15394
music scan terminated unexpectedly
Last modified: 2010-02-05 17:34:40 UTC
I'm new here, hopefully I'm doing it correctly. When I [Clear library and rescan everything], it makes it about halfway through the files (takes over an hour and "see's" about 58,000 songs) and gives me the message "music scan terminated unexpectedly". My playlists also don't show up. Here's what I've done: - Scanned all drives with Ad-aware, and Malwarebytes "The Ultimate Troubleshooter" and the usual Windows security software, all looks clean. - Deactivate Anti-virus (AV) programs - rescan F: ==Received failure message - Uninstall AV's - rescan F: ==Received failure message - Uninstall Squeeze software 7.4.1 - Re-Install 7.4.1 - rescan F: ==Received failure message - Uninstall 7.4.1 - Install 7.4.2 (nightly D/L as of: December 22 2009 04:02) - rescan F: ==Received failure message - Deactivated Sleep, hibernate and screen savers on the PC. - rescan F: ==Received failure message - The latest version of 7.4.2 I've tried is r29679 (the log file is from r29665). Here's a log file: [09-12-24 11:31:19.1253] main::init (320) Starting Squeezebox Server (v7.4.2, r29665, Tue Dec 22 03:59:59 PST 2009) perl 5.010000 [09-12-24 12:02:47.0783] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 300 seconds [09-12-24 12:22:59.0824] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 300 seconds [09-12-24 12:58:11.7971] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 300 seconds [09-12-24 15:22:55.5647] Slim::Control::Request::execute (1918) Error: While trying to run function coderef [Slim::Control::Commands::playlistcontrolCommand]: [Can't call method "name" on an undefined value at /<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Control/Commands.pm line 1882. ] [09-12-24 17:30:07.0958] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 300 seconds [09-12-24 19:56:34.3908] main::init (320) Starting Squeezebox Server (v7.4.2, r29665, Tue Dec 22 03:59:59 PST 2009) perl 5.010000 [09-12-24 20:29:56.3752] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Connect timed out: Bad file descriptor, retrying in 300 seconds [09-12-24 23:02:49.0471] Slim::Schema::Storage::throw_exception (82) Error: DBI Exception: DBD::mysql::st execute failed: Server shutdown in progress [for Statement "SELECT me.id, me.url, me.musicbrainz_id, me.added, me.playcount, me.lastplayed, me.rating FROM tracks_persistent me WHERE ( ( rating IS NOT NULL OR playcount IS NOT NULL OR lastplayed IS NOT NULL ) )"] [09-12-24 23:02:49.0481] Slim::Schema::Storage::throw_exception (82) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>Slim/Schema/Storage.pm line 82) frame 1: Slim::Schema::Storage::throw_exception (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 957) frame 2: DBIx::Class::Storage::DBI::__ANON__ (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 1217) frame 3: DBIx::Class::Storage::DBI::_dbh_execute (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 532) frame 4: DBIx::Class::Storage::DBI::dbh_do (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 1227) frame 5: DBIx::Class::Storage::DBI::_execute (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 1451) frame 6: DBIx::Class::Storage::DBI::_select (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI/Cursor.pm line 82) frame 7: DBIx::Class::Storage::DBI::Cursor::_dbh_next (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 547) frame 8: (eval) (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 540) frame 9: DBIx::Class::Storage::DBI::dbh_do (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI/Cursor.pm line 101) frame 10: DBIx::Class::Storage::DBI::Cursor::next (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/ResultSet.pm line 953) frame 11: DBIx::Class::ResultSet::next (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>Slim/Schema/TrackPersistent.pm line 62) frame 12: Slim::Schema::TrackPersistent::export (slimserver.pl line 1008) frame 13: main::cleanup (slimserver.pl line 988) frame 14: main::stopServer (slimserver.pl line 58) frame 15: PerlSvc::Startup (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>PerlSvc.pm line 95) frame 16: PerlSvc::_startup (slimserver.pl line 0) frame 17: (eval) (slimserver.pl line 0) [09-12-24 23:02:50.3596] Slim::Schema::Storage::throw_exception (82) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (10061) at /<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 950 [09-12-24 23:02:50.3603] Slim::Schema::Storage::throw_exception (82) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>Slim/Schema/Storage.pm line 82) frame 1: Slim::Schema::Storage::throw_exception (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 972) frame 2: DBIx::Class::Storage::DBI::_connect (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 814) frame 3: DBIx::Class::Storage::DBI::_populate_dbh (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI.pm line 568) frame 4: DBIx::Class::Storage::DBI::dbh_do (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/Storage/DBI/Cursor.pm line 101) frame 5: DBIx::Class::Storage::DBI::Cursor::next (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>DBIx/Class/ResultSet.pm line 953) frame 6: DBIx::Class::ResultSet::next (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>Slim/Schema/TrackPersistent.pm line 62) frame 7: Slim::Schema::TrackPersistent::export (slimserver.pl line 1008) frame 8: main::cleanup (slimserver.pl line 988) frame 9: main::stopServer (slimserver.pl line 58) frame 10: PerlSvc::Startup (/<C:\PROGRA~1\SQUEEZ~2\server\SqueezeSvr.exe>PerlSvc.pm line 95) frame 11: PerlSvc::_startup (slimserver.pl line 0) frame 12: (eval) (slimserver.pl line 0) [09-12-24 23:04:06.7502] main::init (320) Starting Squeezebox Server (v7.4.2, r29665, Tue Dec 22 03:59:59 PST 2009) perl 5.010000
Ok, here's something I feel might help: Ok Rich, I [i]think[/i] I understand. I'll give that a shot today. I found one interesting discovery this weekend. My music harddrive is an external USB drive and is separated from the operating system. All it contains is the music. The music is then separated into several different folders. Lets call them folders "1", "2", "3" etc.... Every time it terminates, it terminates in the letter "M" on folder #5 with song number 58,869. Now I can scan just folder number five, and it scans it perfectly. But if I scan the entire drive, all several folders, then it dies on folder #5 in the letter "M" with song #58,869. Twice I've deleted the song it's stalled on, but then it finds the next song (song #58,869) and terminates at that one instead. It takes over two and a half hours for it to scan that many songs. As a result, I've not scanned "too many" times, but enough to notice the number 58,869 seems to be popping up quite often. One more thing I find interesting when I scan the entire drive, if not slightly aggravating, is that when it says it stalled on song #_____ of _____ total songs, the total number of songs can vary by as much as 20%. I assume the lack of replies is due to the holiday weekend? Bob
(In reply to comment #1) > Ok, here's something I feel might help: > I found one interesting discovery this weekend. My music harddrive is an > external USB drive and is separated from the operating system. All it contains > is the music. The music is then separated into several different folders. Lets > call them folders "1", "2", "3" etc.... > Every time it terminates, it terminates in the letter "M" on folder #5 with > song number 58,869. > Now I can scan just folder number five, and it scans it perfectly. But if I > scan the entire drive, all several folders, then it dies on folder #5 in the > letter "M" with song #58,869. Twice I've deleted the song it's stalled on, but > then it finds the next song (song #58,869) and terminates at that one instead. > It takes over two and a half hours for it to scan that many songs. As a result, > I've not scanned "too many" times, but enough to notice the number 58,869 seems > to be popping up quite often. > One more thing I find interesting when I scan the entire drive, if not slightly > aggravating, is that when it says it stalled on song #_____ of _____ total > songs, the total number of songs can vary by as much as 20%. > I assume the lack of replies is due to the holiday weekend? > Bob
Sorry about the double post there. I was trying to clean it up a bit. I've got a four page thread on a forum you may find helpful. I'm not sure if I'm "doing it right" posting here. In order to give as much helpful information without too much garbage, you may want to check out the thread, I do believe there is some good tidbits of information there. http://www.audionervosa.com/index.php?topic=1957.0 Thank you, Bob
Bob - please contact support. They should be able to guide you through the steps needed to isolate the issue.
Thank you Michael. Instead of contacting support, I've decided to uninstall 7.4.2 and revert back to 7.3 The system works great now. Bob