View Full Version : program SC to auto rescan after error
Is there a way to program SC to automatically abort and rescan again after an error stops the rescan process? Due to many scan errors I am having to babysit the program and manually abort and rescan after every error condition, which takes a long time . . . .
Mark Miksis
2008-12-07, 18:09
Is there a way to program SC to automatically abort and rescan again after an error stops the rescan process? Due to many scan errors I am having to babysit the program and manually abort and rescan after every error condition, which takes a long time . . . .
Why are you seeing so many errors? Are these errors due to your setup/tags or problems with SC? I'd suggest figuring out what causes the errors and filing bugs as necessary.
Is there a way to program SC to automatically abort and rescan again after an error stops the rescan process? Due to many scan errors I am having to babysit the program and manually abort and rescan after every error condition, which takes a long time . . . .
What's the nature of these errors? I take it that the scanner is crashing. What are you doing to correct the problem before starting the scan again?
Restarting won't do any good if the error is going to occur again in the same place during the scan.
The scan errors are caused by some album name tag problems which I cannot resolve. Can the scanner be edited to auto abort and rescan after these errors?
Mark Miksis
2008-12-07, 18:38
What version of SC are you running? Newer versions of SC are more robust about these issues. There are no user controls over this.
Out of curiosity, why can't the tag issues be fixed?
If it still crashes on the latest SC, your best bet is to open a bug at bugs.slimdevices.com and attach a file that causes a crash.
The scan errors are caused by some album name tag problems which I cannot resolve. Can the scanner be edited to auto abort and rescan after these errors?
The scanner should not be crashing due to tagging errors. If it's doing so, then it's a bug.
And if it is behaving like this, then it would be expected to crash in exactly same spot in the next rescan, wouldn't it? And if _that's_ not the case, then something else altogether must be happening - the crash isn't being caused by any particular tags. Maybe MySQL is choking, or something else happening.
What type of files are in your library? How were they tagged?
Go to Settings > Advanced > Logging and set 'scan.import' to Debug. Run a scan and then check your log file (from that same settings page). It should help you figure out what's going on.
Here is the error message from the scan log
main::main (219) Error: Failed when running main scan: [Carp::Clan::__ANON__(): Error executing 'INSERT INTO albums (title) VALUES (?)': DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' clusive')' at line 1 at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>DBIx/Class/Storage/DBI.pm line 771.
]
It seems to have a scan error when an album title has a word in it that begins with "ex", such as express, example, exclusive (which happened in the above log).
Pretty crazy.
It seems to have a scan error when an album title has a word in it that begins with "ex", such as express, example, exclusive (which happened in the above log).
Well, you're a little closer. If you have debugging enabled, there should be more than that being logged for the error when there's a crash.
Again, what types of files are in your library, what kind of tags do they have, and how were they tagged? Is this running on Windows?
There have been ongoing character set issues with the scanner. Do any of the file names, or tag data contain extended characters, or is your system using some unusual character set?
Running SC 7.2.1, Windows XP, MP3 and M4A files. Nothing unusual in my setup.
I do not think SC is ready for primetime. If I did not have a good working knowledge of computers SC would be essentially non-functional as a music scanner.
I do not think SC is ready for primetime. If I did not have a good working knowledge of computers SC would be essentially non-functional as a music scanner.
30 day return policy. People with 1/10th your working knowledge of computers have worked through worse issues to get to a point where they're quite happy with the system. If you don't want to give it some effort, then return it.
I'll try a bit more...
Can you tell if the crashes are happening with only one or the other of mp3 or m4a files? That would be the first thing I'd want to figure out. You could determine this by removing the files causing the crash and then rescanning. Try removing the whole album in which the crashing file belongs.
30 day return policy. People with 1/10th your working knowledge of computers have worked through worse issues to get to a point where they're quite happy with the system. If you don't want to give it some effort, then return it.
I'll try a bit more...
Can you tell if the crashes are happening with only one or the other of mp3 or m4a files? That would be the first thing I'd want to figure out. You could determine this by removing the files causing the crash and then rescanning. Try removing the whole album in which the crashing file belongs.
I essentially asked him the same questions in another thread he started on this same issue before he started this thread. He seems very reluctant to provide any details.
Seems like we're not getting the whole story here.
I deleted all the files that had words beginning with "ex" in the album title and that fixed it. SC did not like words beginning with "ex" for some reason.
I deleted all the files that had words beginning with "ex" in the album title and that fixed it. SC did not like words beginning with "ex" for some reason.
Great you got it fixed. :)
Did it properly scan all 20,000 tracks after your fix?
yes it scanned OK after the fix
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.