AudioNervosa
Systemic Development => Digital Audio Devices => Streaming Players => Topic started by: Bob in St. Louis on December 23, 2009, 06:56:21 PM
-
I've been through the Squeeze forum archives and can't find a solution for this error message. Seems to be happening quite a bit and most folk blame the antivirus(AV) programs, but I've eliminated that as an option.
When I [Clear library and rescan everything], it makes it about halfway through the files (takes over an hour) and gives me the message "music scan terminated unexpectedly". My playlists also don't show up.
Here's what I've done:
- Deactivate AV program
- rescan F:
==Received failure message
- Uninstall AV
- 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
Any ideas? :duh
Thanks fellas,
Bob
p.s. Running; Windows XP Pro SP3
-
Do you have all the sleep modes and power saving stuff disabled on your PC? Are you running squeeze server as a service or does it run on demand? The default is on demand and IME it's horribly unreliable in this mode. The older versions installed it as a service then for a while they provided a utility to enable this. In 7.4.1 the control panel has an option to enable "run at system startup", this installs it as a Windows service and IMO is the only way it should be run. I did create an account for it to run as, in my case it's "sys_slim" but you can name it anything you like.
-
http://www.readynas.com/forum/viewtopic.php?f=22&t=34836
Possible that the ReadyNAS cleaning utility cures it for us, but won't help you on a PC. But there might be clues to be gained. Turn on the logging to max detail, see if you can see more details. I think I have version 5 if you want to downgrade.
It is also mentioned that 7.4 has a new scanning engine rewritten in C instead of PERL. So it could be a bug, which the prevalence across different platforms would suggest. It took a long time for the Duet wifi remote controller networking issues to be resolved but many updates happened in the meantime, none addressed that major bug. But finally it got fixed.
-
Mike - Didn't think about the sleep/hibernate modes. I turned them off. Just for grins, I even turned off the screensaver. One hour, eleven minute rescan:
Got about half the library again. Fail. :(
Not 100% sure about the 'service' or 'demand', but mased on your description, I'd say I'm running it as a service. I'm basing this thought entirely on the fact that when Windows launches, I get a balloon that points at the icon near the clock and tells me "SqueezeCenter running".
Please correct me if I'm wrong.
I can't find in the GIU where it specifies which mode.
A far as creating an account, you've lost me there.
Rich - Dude, you've lost me there. Most of what you've said is over my head. I'm not using a NAS, although I understand what you're saying about gaining clues from it. I just haven't gained any yet. :duh
Got my new (replacement) Duet in the mail today. Just hooking it up, and have loaded all the newest updates goodies it says are available. Somehow I doubt that's what you're referring to, but I thought I'd mention it.
Bob - Confused :duh
Merry Christmas and Happy Holidays to all!
-
I don't have the software installed so I can't tell you exactly where the logging settings are, but you can poke around in the SqueezeCenter GUI to find it. Then set the logging settings to record everything that happens instead of the deafult setting which is just summary to save disk space. Note what time the failure happens, then look it up on the log by timestamp. The surrounding activities might give you a clue. But if it was really that easy, somegeek would have figured it out. When you're done playing, switch it back to default setting.
Here is a link to 7.3.3 to use until this blows over. (That should be OK, right?) I don't know if there is any special procedure to use for downgrading Squeezecenter.
http://downloads.slimdevices.com/SqueezeCenter_v7.3.3/SqueezeCenter-7.3.3.exe
-
Bob,
If you double click the tray icon you should see the attached screen. The middle section where it says "automatically run at system start" will enable it to run as a service. If you want to create a user account for it, under windows control panel you can use the "users" application to create a new user and give it a password. You need to do that prior to changing the settings in the squeezebox control panel if you choose to go this route.
To view the scanner logs, click settings in the web UI, lower right hand corner. Choose the "information" tab and then click the "view previous scan details" link. At the bottom of that page you can view up to 1000 entries in the scanner and server logs. You can change the logging settings from the "advanced" tab, select logging from the drop list.
-
Neat way to embed a photo Mike. Very cool, I've never seen that.
Here's a screen shot of mine, right next to yours. Two things to note; Mine is 7.4.2, and the drop down to change "automatically run at login" can't be changed to "automatically run at system start".
Seems like I'm missing a button somewhere that would make things much easier than I'm making them. :roll:
Sorry I didn't notice this screen earlier. I never go there. I change things through the settings button when SS is running.
Thanks Mike
Bob
EDIT: Wait a minute, I just found something.......
(http://i85.photobucket.com/albums/k60/BobinStLouis/Crap-n-Stuff/ss.gif)
-
Alright, I've changed the setting Mike spoke of, and am now rescanning. It'll be over an hour before I expect anything bad to happen (but of course I'd prefer it not happen). By then, the kids will be in bed and the wife and I will be dealing with another version of SqueezeCenter.
Rich, thanks for the heads up on the 7.3.3. Good to know.
Poking around where Mike spoke of, I did find where to get the log file.
If it comes to that, I'll let you know what I find.
Thanks men. Have a good night.
Bob
-
Nope. Interesting time stamp though.
Another screen shot of yours and mine.
(http://i85.photobucket.com/albums/k60/BobinStLouis/Crap-n-Stuff/ss2.gif)
-
You could try Revo Uninstall (http://www.revouninstaller.com/) to make sure you scour away every atom of SC before reinstall. But this is just throwing the dice with long odds. I wish I knew what the cleaner app was that the NAS boys use.
-
I'm guessing you've checked , but as Mike said, on the Advanced tab you can access the server and scanner logs. It would be interesting to see if it's always crashing in the same directory or at the same point in the scan. Might be some clues there.... Perhaps a corrupted file or folder?
But, hey, it's Christmas! Think about it tomorrow and just enjoy the day!
-
I now have quite a few more tunes than I thought I had, or have ever had. But the playlists are gone. ](*,)
Most unusual.
I'll rescan and see what the log says, just for grins.
Bob
-
Early on during todays scan, it's almost as if the scan had determined where it's going to fail. Usually it's somewhere around the 55,000 to 60,000 song mark, but today I notice that a few minutes after I started the scan, it said, "XXXX of 43,000" songs. Like it KNEW where it was going to fail, but continued the scan anyway.
It made it this far: Directory Scan (4443 of 43118) Complete 00:19:13
Put another way, the 43,118 was there VERY early during the scan, like in the first minute or two. It took 19 minutes to actually stop the scan.
That's a hint, maybe?
Also, here's the log file. kinda huge.
Hopefully this means something to somebody. The first couple "paragraphs" look interesting.
[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
-
Make a new directory with 1 song in it. Let it scan that. If successful, go back and try the other again. If not delete the one song and scan again with nothing. Look for errors in the log. You can empty the log before you do a test.
First 4 lines are lost connectivity to the player. Try a hard wire if you are using wireless. Could be this error causes others.
DBI.pm is choking and failed to connect to database. Try extended ping of the database port,
"ping 127.0.0.1:9092 -n 100" in command prompt
See what your percentage is after it finishes in a couple minutes. Probably 100%, but maybe this will help Mike think of another reason your database connection failed. :D
I would try removing the whole thing and every trace of it with max strength setting on Revo. Then reboot and reinstall "Like a Virgin."
-
It still sounds a bit like the antivirus problem but I'm assuming you're not running one at this point.
I agree with Rich... I'd use Revo Uninstaller and remove the install and all remnants (including your Squeezebox Server settings) and start over with the lastest download. Something is definitely funky but I suspect wipe and reinstall will be the least painful path.
-
Thanks guys.
Alright, I'll do the Revo thing, but when I reinstall should I do the latest "retail" version, or the latest nightly version?
I've deleted my Antivirus program altogether (to eliminate it as a possibility). Unless there's some weird thing running in the background I don't know about????
Here's a screenshot of the ping. Looks good to me.
(http://i85.photobucket.com/albums/k60/BobinStLouis/Crap-n-Stuff/ss3.gif)
-
I'm using the latest 7.4.2 nightly and it seems rock solid.
-
Unless there's some weird thing running in the background I don't know about????
Besides windows? :rofl:
You pinged something, but was it 127.0.0.1:9093? If so it returned your DNS service, opendns.com. Can you disable that temporarily?
127.0.0.1:9093 is the database port on your local machine.
-
Thanks Mike. When the time comes, I'll reinstall with the latest nightly.
Rich. Can I just delete OpenDNS?
I did that one day thinking I knew what I was doing. I think there was an issue with excessive intake of liquid intelligence that caused me to do that. :roll:
It pops up (not literally) from time to time and I wouldn't mind if it was gone.
I did a copy and paste of your "ping 127.0.0.1:9092 -n 100" and the screen shot I posted is what came up. I didn't know the results are "9093". I don't even see that in the shot. How can you tell, and how can you tell OpenDNS was involved.
Actually, now that I think about it, your explanation would probably be over my head. I appreciate your assistance. Don't wanna burden you by asking stupid questions. All I need to know is can I delete OpenDNS, or should I keep it.
Thanks man,
Bob
-
No problem whatsoever! That returned IP address in your screen print is from OpenDNS network, gleaned from an IP lookup. (http://ip-lookup.net/)
OpenDNS (http://en.wikipedia.org/wiki/OpenDNS) It speeds browsing by getting name resolution from OpenDNS name server which is supposedly faster than your ISP's own DNS servers, but the ping was consistently on the slow side at 50mS, so I don't know how much faster it really is, maybe..... It sits in memory to "help you" with various other browsing tasks and protection from bad boys. You can ditch it. Use Revo to really clean it out.
I remembered that you can't ping a specific port as I was asking you to do, so instead of error message from windows, you got sent to openDNS to try to resolve it. So nevermind about the ping. Maybe serendipitously discovering openDNS and deleting it will help in one way or another.. 9093 is an active port number on the local computer's internal IP address 127.0.0.1. All computers have that same internal IP address. The MySQL database used by Squeezecenter is on your computer and is contacted by any application through that IP address and port number. (http://en.wikipedia.org/wiki/TCP_and_UDP_port) You can think of ports as phone numbers for programs to call each other using TCP/IP protocol. Like an office number inside a building where the building is the IP address.
-
Excellent information Rich, thank you VERY much.
I'll take dumb luck, or as you so eloquently phrased it "serendipitously discovering", anyday. My goals for the day are to:
- Install Revo
- Uninstall OpenDNS
- Uninstall anything to do with Squeeze.
- Poke around with Revo to delete anything else I think might be bits of trash that haven't gone away from previous uninstalls.
Two questions;
-#1 When I uninstall OpenDNS, will "things" revert to my provider automatically, or will I then findmyself logging in here on my wifes PC because this one is no longer able to connect to the internet because I need to change some setting.
Basically, will I be "F"ing myself.
- #2 When I use Revo to uninstall Squeeze, will it merely be uninstalling the current version in use, or will it actively search for all of the older versions (7.4.1 - 7.4.0 - 7.3._) and kill them too?
By the way, I do occasionally use "The Ultimate Troubleshooter" from time to time.
That's a great piece of software that has helped me find nasty things.
Just thought I'd throw that out there.
Thanks again!
Bob
-
Uninstalling OpenDNS shouldn't pose any problems - I've done the same. Worst case is you might need to do an ipconfig /renew from the CMD prompt or simply reboot, but it should cleanly revert to your provider (or however your router is configured if it is serving up DNS).
Revo first runs the software's uninstall and then goes hunting for leftover directories and registry entries. If earlier versions still remain in different directories (but no longer actually installed), you might need to find them by hand.
-
Alright cool. Revo is currently on a recon mission for things to "Squeeze". :twisted:
I'll be having fun playing "search and destroy" for things to delete.
more soon.
Bob
-
Just for grins, I installed Ad-aware, and Malwarebytes. Scanned the drive, no problems.
Used Revo to uninstall both pieces of software.
I still have "TUT" (The Ultimate Troubleshooter) and it showed things are clean.
Used "Hijackthis", everything looks good.
Uninstalled SqueezeCenter, OpenDNS, and a few other bits and pieces using Revo.
Reboot PC.
Install nightly SqueezeCenter 7.4.2-29679
Changed setting to "Run at system start up" as Mike suggested.
Scanning the library now....... :beer:
-
Nope.....still "terminating unexpectedly". :(
Here's the log:
[09-12-26 20:26:37.3752] main::init (320) Starting Squeezebox Server (v7.4.2, r29679, Sat Dec 26 04:01:57 PST 2009) perl 5.010000
[09-12-26 20:26:47.3752] Slim::Schema::init (148) Warning: Creating new database - empty database or database from 6.3.x found
[09-12-26 20:26:47.3774] Slim::Schema::Storage::throw_exception (82) Error: DBI Exception: DBD::mysql::st execute failed: Table 'slimserver.dbix_migration' doesn't exist [for Statement "SELECT value FROM dbix_migration WHERE name = ?;
"]
[09-12-26 20:26:47.3782] Slim::Schema::Storage::throw_exception (82) Backtrace:
frame 0: Slim::Utils::Log::logBacktrace (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Schema/Storage.pm line 82)
frame 1: Slim::Schema::Storage::throw_exception (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>DBIx/Class/Storage/DBI.pm line 957)
frame 2: DBIx::Class::Storage::DBI::__ANON__ (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>DBIx/Migration.pm line 237)
frame 3: (eval) (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>DBIx/Migration.pm line 233)
frame 4: DBIx::Migration::_version (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>DBIx/Migration.pm line 149)
frame 5: DBIx::Migration::version (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Schema.pm line 479)
frame 6: Slim::Schema::migrateDB (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Schema.pm line 162)
frame 7: Slim::Schema::init (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Music/Import.pm line 745)
frame 8: Slim::Music::Import::_checkLibraryStatus (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Music/Import.pm line 678)
frame 9: Slim::Music::Import::useImporter (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Music/MusicFolderScan.pm line 48)
frame 10: Slim::Music::MusicFolderScan::init (slimserver.pl line 429)
frame 11: main::init (slimserver.pl line 572)
frame 12: main::main (slimserver.pl line 98)
frame 13: PerlSvc::Interactive (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>PerlSvc.pm line 99)
frame 14: PerlSvc::_interactive (slimserver.pl line 0)
frame 15: (eval) (slimserver.pl line 0)
[09-12-26 20:26:47.3804] Slim::Schema::Storage::throw_exception (82) Error: DBI Exception: DBD::mysql::st execute failed: Table 'slimserver.dbix_migration' doesn't exist [for Statement "SELECT value FROM dbix_migration WHERE name = ?;
"]
[09-12-26 20:26:47.3812] Slim::Schema::Storage::throw_exception (82) Backtrace:
frame 0: Slim::Utils::Log::logBacktrace (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Schema/Storage.pm line 82)
frame 1: Slim::Schema::Storage::throw_exception (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>DBIx/Class/Storage/DBI.pm line 957)
frame 2: DBIx::Class::Storage::DBI::__ANON__ (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>DBIx/Migration.pm line 237)
frame 3: (eval) (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>DBIx/Migration.pm line 233)
frame 4: DBIx::Migration::_version (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>DBIx/Migration.pm line 78)
frame 5: DBIx::Migration::migrate (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Schema.pm line 481)
frame 6: Slim::Schema::migrateDB (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Schema.pm line 162)
frame 7: Slim::Schema::init (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Music/Import.pm line 745)
frame 8: Slim::Music::Import::_checkLibraryStatus (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Music/Import.pm line 678)
frame 9: Slim::Music::Import::useImporter (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>Slim/Music/MusicFolderScan.pm line 48)
frame 10: Slim::Music::MusicFolderScan::init (slimserver.pl line 429)
frame 11: main::init (slimserver.pl line 572)
frame 12: main::main (slimserver.pl line 98)
frame 13: PerlSvc::Interactive (/<C:\PROGRA~1\SQUEEZ~2\server\SQUEEZ~3.EXE>PerlSvc.pm line 99)
frame 14: PerlSvc::_interactive (slimserver.pl line 0)
frame 15: (eval) (slimserver.pl line 0)
[09-12-26 20:27:00.6408] Slim::Plugin::MusicMagic::Plugin::initPlugin (265) Can't connect to port 10002 - MusicIP disabled.
[09-12-26 20:27:01.5945] main::checkDataSource (967) Warning: Schema updated or no tracks in the database, initiating scan.
[09-12-26 20:38:06.4846] main::init (320) Starting Squeezebox Server (v7.4.2, r29679, Sat Dec 26 04:01:57 PST 2009) perl 5.010000
[09-12-26 20:38:15.6096] main::checkDataSource (967) Warning: Schema updated or no tracks in the database, initiating scan.
[09-12-26 20:55:22.6721] main::init (320) Starting Squeezebox Server (v7.4.2, r29679, Sat Dec 26 04:01:57 PST 2009) perl 5.010000
[09-12-26 20:55:34.3752] main::checkDataSource (967) Warning: Schema updated or no tracks in the database, initiating scan.
-
When you did the uninstall, did you blow away all your old preferences as well? Was the full Program Files\Squeezebox directory deleted? I suspect so, but thought I'd ask since I ran into that awhile back.
I somehow suspect the directory scan is running into some kind of corrupt music files and there's a couple threads in forums.slimdevices.com that indicated such. Have you ever been able to successfully run a 7.4 version with your current music? Is there anything in the scan log that shows what music it was on when it failed?
See this thread: http://forums.slimdevices.com/showthread.php?t=69127
On the 2nd page, it seems this guy had a very similar problem that seems to have been caused by a couple of corrupt .wav files.
-
Another hardware platform (Bubba) having same issues.
http://forum.excito.net/viewtopic.php?p=9441
Please create a new test directory and put only one file in there, then ~10 then ~100 then 1000 if you have success. If there is a certain spot that always crashes it, use that track or area. If there are weird characters like accents delete the weird character from the name in the test directory to see if that fixes it. If not delete the weird character in the tag also and test again. Debugging is a pita. But at least you know they are working on it if you don't want to bother. Just go back to 7.3 for now.
http://forums.slimdevices.com/showthread.php?t=17482
https://bugs.slimdevices.com/buglist.cgi?quicksearch=music+scan+terminated+unexpectedly
Press the "Long Format" button to see the details and responses. Feel free to participate in the bug hunt by posting your experience on the appropriate thread.
-
I received an email from a concerned bystander asking if I've performed the Windows "[Error Checking and Repair Scan]" of the music harddrive. No I hadn't, so I thought it sounded like a good idea. The scan took 13.5 hours. I assume all is well because there was no error messages, no report, no nothing.
Am about to do Squeeze scan of the library to see if that "fixed" anything.
Rich, I'll check out the Bubba thread. Thank you VERY much for that. Nice to know since misery loves company.
I also completely forgot to do the new directory that you've now mentioned twice. I forgot the first time. :duh Sorry about that.
With the exception of one time, it does seem to always stop around the 55,000-58,000 song area. There might be something right around there pissing it off.
Mike, yes.....When I deleted Squeeze, I deleted E*V*E*R*Y*T*H*I*N*G that had anything to do with Squeeze. At least everything that Revo could find, that is.
Ok, here are the plans for today....... :roll:
#1 Rescan the library to see if the [Error Checking and Repair] did anything.
#2 Create the smaller sub directory as Rich asked and rescan
and if those don't work....
#3 Visit and participate in the Slim Forums.
#4 Drink lots of beer while performing the above tasks.
Sounds like a fun filled day. :rofl:
Bob
-
.......in addition to that.....
I just fired up the Squeeze software to "clear and rescan" and it's been rescanning the library for over six minutes now.
How the Hell does that happen? :wtf:
Bob
-
Rich, I was able to sucessfully scan select smaller folders, as opposed to the "big one". Those scan just fine. I still don't get playlists, but that's expected since they're located in the 'biggie' folder.
I did start >> a bug report with Slimdevices, << (https://bugs.slimdevices.com/show_bug.cgi?id=15394) thanks for the heads-up on that.
I've not touched this issue since last Sunday. If things don't get fixed soon, I'll revert back to 7.3.x.
There's a spare PC sitting in my workshop I could wipe out. Due to this and other PC issues, I'm tempted to spend the cash and upgrade that one to '7', then start populating the "new" PC with my old stuff.
But that's not what I wanted to spend money on right now.
Maybe.....
Bob
-
OK so if you got it to complete a scan without error, start throwing things into that test directory to try to break it. When you find something then you can discover what is different about it. Try changing the one file you have in there to have a foriegn language character like "accent grave." You can find them for copy and paste in "Start button: All Programs | Accessories | System Tools | Character Map, use font Arial. Or just rename the file and retag the song name to "ÿÚ®¢¥¶õÆÇ" If it can swallow that then it's probably not character problem which is common in new software, the squeezebox forum history is full of foreign char fix requests.
Another idea is to copy in 100 or 1000 songs from the area where it usually chokes to find one that is causing the trouble. Happy new year Bob! Make sure you stop the dubugging to give someone a big kiss round a bout midnight. :D
-
I'll kiss you if this works. 8)
Seriously though, If time allows this weekend, I'll do exactly that. I was hoping for a blanket fix as opposed to finding a weird hieroglyph buried somewhere in a tag. That would suck. Especially to find it belongs to a song I don't care much for anyway.
Happy New Year folks!
BOb
-
If it was always hanging on the same folder, I'd:
Create the folder, try a scan
Then, add songs 1 at a time until you find what it is rather than trying to do it all manually. Might save some time.
Bryan
-
It's hanging in the letter "M".
I've got about 120 artists under the letter "M". One song at a time would drive me to my grave. I'm currently rescanning just the folder with the letter "M" in it. I might run through the "M"s and delete the stuff I don't like then rescan. If that doesn't work I'd be more willing to scan smaller 'bits' of the folder. Sure would be nice if there was a simple fix that's resolved on a future download. I can only pray.
Thanks for the replies guys. I'll keep plugging away as time allows.
Bob
-
Never mind.....
It just successfully scanned 6596 songs who's artists start with the letter "M" just fine. :roll: :duh
Previously it's been stalling on "M".
Based on recommendation from you fellas, I now know what to do. :?
Damn. That's a lotta time looking for a weird character.
Bob
-
Not if you do it the easy way. It's either tolerant of oddball chars or not. So put one track in your test directory. Scan to make sure it succeeds. Edit the track tag so it has some weird chars in it, like the word I posted above, just copy and paste it in. Scan again. Then edit the filename with weird chars too. Scan again. If it fails with weird chars, and succeeds with normal chars, then you have found something to report to buglist. You are quite persistant mr bisl. kudos!
-
From here on this will be known as the MrBiSLbug :rofl:
-
Ok Rich, I think I understand. I'll give that a shot today.
I found one interesting discovery this weekend. My music harddrive is 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.
THat sounds like something worthy of adding to the bug report. Maybe?
What sucks, is that it takes over two and a half hours for it to scan that many songs. I've got an auxiliary fan blowing on my external drive, cause it's gettin' DARN hot. I know I'm shortening the life of my drive with all these scans.
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%.
Bob
-
Hmmm, a magical 58869 number! I wonder what would happen if you just scan the ~ first 58000 songs thru completion and then incrementally add more as you inch up to the magic #?
That is quite a large library of music you have but I can't imagine others haven't topped it. If it's always failing at that point, I wonder if you're running out of some resource... ?
But, yes, definitely worthy of logging as a bug.
-
With the 58,869 discovery, and that directory scanning clean, I think you have discovered a problem that is worthy of reporting since it is repeatable. The only thing I can think of that could be an influence on your end is the amount of RAM you have. But even 1GB should be enough to hold 1KB of metadata for 1Million+ songs. You could pull out some RAM to see if it crashes sooner, but I don't think it will unless slimserver is using RAM very inefficiently.
I had unfixable networking issues with early Duets. I sold them to get Sonos and haven't had a single issue since. But it needs a good DAC and there are no plugins. Nothing's perfect!
-
That's really odd. If it fell on a natural boundary like 65,535, it would be at least potentially explainable. This is just weird.
Bryan
-
Yes Bryan, leave it to me to have a "stumper". :duh :rofl:
Just thinking out loud here.....Correct me if I'm wrong, but I've eliminated the character as being an issue, haven't I? I mean since it's scanning the folder without a problem. So I don't need to worry about creating a test folder.
Mike, I like your idea of "sneaking up on it". I've uninstalled SC using the Revo, and have installed last nights nightly update. Rescanning now.
If it is an issue with RAM, wouldn't I be able to see that in the task manager, or with the "TUT" software?
Bob
-
I'd say the character issue is put to bed.
You're running out of SOMETHING on a consistent basis. I'd start checking things like virtual memory size, available disk space in the area windows uses, etc.
Bryan
-
My guess is that it's either an issue with scanning such a large library in a single pass or it's an issue of having such a large library. If sneaking up on it by incrementally adding music works, then that at least narrows it down and would give the Squeezebox folks something specific to address.
Either way, I think you need to throw it to the Squeezebox folks and post the 58869 limit you reached in the Squeezebox forums. At least you'd find out if others with such large libraries have run into similar problems.
-
Alright. Right in the middle of rescanning the drive, I enlarged the virtual memory. Probably not the correct way of doing it, but we'll see. It may not even enlarge it until I restart the PC?????
Looks like it's time to start shopping for RAM.
1GB may not be enough anymore.
Bob
-
You could try it in safe mode, to eliminate memory and program conflict issues. 1GB was enough in 7.3...
Definitely report what you've found. It strongly implies something in their code.
-
In 52 minutes it already made it to 46,000 songs. :shock: :thumb:
Something is DEFINITELY faster.
I've got the task manager running in the background on the performance screen. When (if) it terminates, I'll be waiting to do a screen shot. Maybe there will be something in there that will give a hint if RAM is the cause.
more soon,
Bob
-
Nope..... :( That wasn't it. :duh
I barely know what I'm doing fiddling around with virtual memory. However, I did enlarge it from 1536 ("initial size") to 2000.
Here are two screen shots.
#1 is during the scan.
#2 is a few seconds after the scan terminated. (Ignore the double humps in the chart in number two. That's when I checked my email. :lol:)
I noticed the scan stopped at 58,849....Slightly short of the 58,869. I assume it's due to having more stuff going on in the background, like the screen print software?
Notice the huge hump on the right side of #2?
That's where it "choked". Is that due to memory?
(http://i85.photobucket.com/albums/k60/BobinStLouis/Crap-n-Stuff/ss1.gif)
======================================================
(http://i85.photobucket.com/albums/k60/BobinStLouis/Crap-n-Stuff/ss2-2.gif)
-
....but then I go to my SC user interface and it says I've got 58,949 songs. one hundred more than it claims to have scanned.
That's just weird.
Bob
-
You could try it in safe mode, to eliminate memory and program conflict issues. 1GB was enough in 7.3...
By the way, I didn't mean to ignore you Rich. I'm not sure I know how to start in safe mode and then open a piece of software. I did that once a decade ago, but have not needed to use the "safe" thing since.
Sorry man. You're dealing with an idiot when it comes to certain aspects of Windows.
Bob
-
I'd try adding more music incrementally at this point to see if you can. I'm not sure if Squeezebox Server will let you since the last scan failed but worth a try.
You can boot into safe mode via the setup function on reboot (one of the function keys usually gets you there - can't remember which).
-
I'd try adding more music incrementally at this point to see if you can.
Yip. I'm going to "clear library and rescan". I'll only do one folder at a time. Given there are eleven separate folders, that'll take a while. It will answer whether or not it's a memory issue.
But I really need to finish installing the wood floors for the wife, least I earn myself a divorce for the new year. :shock:
more later,
bob
-
You have enough memory.
To get into safe mode, Reboot the PC. When the POST (BIOS startup test) is almost finished start hitting F8 key twice per second. If you see the windows graphic then you missed it, so reboot and try again. This will give you a boot menu which will let you choose "Safe mode with networking." You may need to start slimserver service manually because safe mode is not supposed to start anything it doesn't absolutely need.
And, don't forget version 7.3 is there waiting for ya! ;)
-
You have enough memory.
Ya know....I think you might be right. But when you say I've got "enough", is that enough of the physical memory, the virtual memory, or both?
I did scans of smaller folders, one at a time, with a reboot of the PC in between each scan. I just got the 'terminated' failure again. Strangely enough, it occurred in the "M"s in that same folder as before. This time it failed at:
Directory Scan (50293 of 76276) Complete 00:49:25
Not even close to the 58,849. Ignore the 76276, since I'm adding small folders individually.
Not sure how much of this is valuable to the bug thread at Slimdevices, but I think I'll post a link to this thread and let them decide. The 7.3.x is looking better all the time.
For now, I'll try the safe mode and do a complete rescan of the entire drive.
Bob
-
"Screen Print" doesn't work in safe mode, but the scan terminated at:
Directory Scan (58856 of 101972) Complete 00:57:19
It's taking less than half the time as it did before I played with the memory, but it's still terminating at about the same place. :?
Bob
-
Nogo on the safemode, I didn't think there would but it eliminates memory and other programs being an issue. You've done everything you can while still maintaining your sanity. At least you can downgrade until coast is clear.
By saying, "You have enough memory," I meant that 1GB RM should be enough memory to prevent slim from crashing with no other heavy programs running. Your performance meter seems to agree. You were pushin it, but no major stress.
Virtual memory is OS simulated RAM running on the hard drive. Looks like RAM to the program, runs 100 times slower than physical RAM but it prevents crashes from running out of memory. Set it to allow Windows to manage virtual memory automatically. Then it will use as little as possible, but can increase instantly if needed. It should take a couple GB or so if you have it to spare.
My kids use an XP SP3 machine with 1.5GB, memory is maxed out. It is a little slow to fully boot, but once it's up and running it's fast enough for the kids playing online VR action games like Roblox and Wizard101. You can check how much physical RAM you have in system properties, then look it up on 4allmemory.com to see if it's worth maxing it out. Some commodity memory is really cheap now. I still have a 500MB DIMM lying around unused. It's yours if you want it, goes in Dell Dimension 2400, probably pretty standard DIMM, you can look it up on 4allmemory to know for sure. Win + Break brings up system properties, or right click My Computer icon for properties command.
-
Cool, thanks for all the help Rich, Mike, and Bryan.
So it's not a memory/hardware issue, nor is it an antivirus/firewall, issue. Doesn't seem to be anything on my end from the looks of it.
That leaves a Logitech based solution. Right?
I've been thinking about "uping" the amount of RAM recently. That, combined with the spare PC I've got and a fresh install of a new OS (Windows '7') will fix all my woes.
A boy can only hope.
For now it looks like the only solution is to downgrade to 7.3.
Once I can scan my tunes again, then I can address my issue with the Duet error "Can't connect to library".
:roll: :duh :roll: :duh :roll: :duh :roll:
Done for the weekend.
Thanks all,
Bob
-
Having at least 2G of memory for Windows is definitely a good idea, but I somehow doubt that has anything to do with the problem you're having. As Rich said, I'd go back to the latest v7.3 release and see if that works now. If you're still having the problem, then maybe there's something flakey with your PC, but if 7.3 works, then I think it's gotta be something with the 7.4 series of Squeezebox Server. Let them deal with it (but don't hesitate to ping them occasionally if you don't get any response).
Good luck, Bob!
-
So, that's like 8,500 albums.. wow. It would take you a year of 24/7 playing to hear it all. That is an impressive number of albums. How much of it do you actually listen to? Do you really like that much music? I mean this as a nice question because I'm genuinely blown away at the volume(s) of music.
Stats from my setup:
My paultry 846 albums with 11091 songs by 402 artists takes about 5 minutes to completely scan and another 4 to get all the artwork for the albums. I have a 2G processor w/ 2G of RAM. During the scan it uses up to 50% CPU and a half Gig of ram.
-
SUCCESS
Per the recommendation, I reverted back to 7.3.?
Works like a charm, I've got all my tunes now. :thumb:
That works out great since the fellas at the Slim bug fix-it center have told me to contact the support department. :duh
Apparenty they've determined it's not worthy of "bug status".
Carl, the tunes are for myself and my wife. We have wildly different tastes which tends to fill a collection rather quickly. I like everything but country and she hates everything but country. To give you an example, I spent most of yesterday upstairs installing wood floors. WHile doing that I had her PC (using MediaMonkey) play songs at random from the Blues genre. Most of the time that's the way I'll listen, just pick a genre and "let 'er roll" all day.
So yea, I really do like that much. :D
Bob
-
:thumb:
Back in the music....
-
That works out great since the fellas at the Slim bug fix-it center have told me to contact the support department. :duh
Apparenty they've determined it's not worthy of "bug status".
It'll be interesting to see how the boys in the support department are going to address this. Keep us posted!
-
It'll be interesting to see how the boys in the support department are going to address this. Keep us posted!
Nope. I'm officially out of the debugging biz. I've gone far enough. I've spent waaaaay too much time jacking with this. Enough time I've neglected the wife's projects, my projects, and projects for other people. Time to get on with life. :rofl:
Thanks again for all the support guys. I truly appreciate it.
Bob
-
Hi Guys, I had the same problem, but since I have made a couple of changes, my scan now is always 100% complete, 31,476 songs in 3,208 albums taking 3min 59 secs.
I used to get the errors and a stopped scan the same as you are, my filing system was this, L drive/Music/ then the folders i.e Led Zeppelin then sub folders of each album by Led Zep. L:Music/Led Zeppelin/Houses of the Holy
Now, when my system used to terminate during a scan, I went to the name of the directory (Led Zeppelin) and found a music track inside the Led Zeppelin folder along with all of the album sub directories. I deleted or moved the file out of the parent directory and into another sub directory with other music files (if I wanted to keep it).
I re-ran the scan and it went past Led Zeppelin only to hang at another folder, again when I looked in here I found a stray track, so I moved this and voila, it went past on the next scan.
Conclusion (for me anyway) I checked that I had NO individual music files in directories on the way down to the final directory and now my system is perfect, this may not be the answer for all of you, I KNOW it fixed mine, so good luck with yours !!!!!
Kind regards, Nick
-
Wow! How in the world are you getting it to scan 3208 albums in 4 minutes? Are they flac, mp3? Or, do you just have a seriously high horse-powered PC running Squeezebox Server?
I've got about a third of the albums you do (all in flac) and it takes at least 15 minutes to fully scan the entire music tree. My music is organized much like yours.
FWIW, I'm running v7.5.1 and it's working like a charm! I should be receiving my Touch tomorrow - can't wait to see how it sounds compared to my Duet which, I suspect, will soon be seeing a demotion to kitchen duty.
-
Welcome to AN....
Luv your avatar Jag! XJ-S convertible was once my favorite car, saw it first at 1980 Boston car show, navy blue gorgeous with V12. The last real jag. :(
Do you drive it?
Looking fwd to your Touch review Mike!