Bugzilla – Bug 4416
Slimserver crashes on rescan
Last modified: 2007-05-21 13:14:45 UTC
(reference tmid 11714) Customer upgraded to 6.5. Now his server crashes if he rescans his library. But if if rescans with "Clear library and rescan everything" it does not crash. Only when he uses "Look for new and changed music".
Created attachment 1662 [details] log file from manual scanner run this is the results from > scanner.exe --wipe --d_import --d_server --d_scan --logfile=C:\slimserver.log
that looks like a failure to connect to mysql. the server MUST be running when scanner is run manually.
we checked. mysql is indeed running.
try running slim.exe --d_import --d_scan --d_server --logfile=c:\slimserver.log instead. The previous log isn't really showing a proper "crash". Rather it is an inability to initialise and can't be trusted to be the SAME problem that is causing slimserver to crash. this is rather similar to bug 4299.
Did you have a chance to try KDF's suggestion, Dan?
Created attachment 1677 [details] New log from manual scan per KDF's flags
I have an additional support ticket that is showing something similar to this behavior. (support tmid 11953) Scanner.exe is crashing if he tries either "Clear library and rescan everything" or "Look for new and changed music". But, when he manually runs scanner.exe it successfully scans his files. He's running: scanner.exe --wipe --d_import --d_server --d_scan --logfile=C:\slimserver.log (but because it worked, he did not provide the log file)
if scanner.exe works, when a launch from slim.exe fails it may be a permissions problem.
Or it could be that some scanner option is being tried by slim.exe that is not being specified when he types it in by hand. For instance musicmagic, moodlogic, iTunes, or some debug flags. I'd be interested to know if he has musicmagic, moodlogic, itunes, or any debug settings turned on in the GUI, if you talk to him again, Dan.
Any more info here?
Regarding the first customer (11714) he updated to the new Slimserver on 11/05/06 and reported that everything was working correctly. Regarding the second customer (11953) he suffered thru the odd behavior until he bought a new computer in February. The new system has Vista and therefore he ran into the common Vista problems, but did not report any scanning issues. He stopped responding after that. Close bug?