[17-04-04 10:18:37.3354] Slim::Utils::SQLiteHelper::updateProgress (463) Notify to server OK [17-04-04 10:18:37.3366] Slim::Schema::optimizeDB (430) End schema_optimize [17-04-04 10:18:37.3372] Slim::Music::Import::endImporter (643) Completed dbOptimize Scan in 175 seconds. [17-04-04 10:18:37.3380] Slim::Schema::forceCommit (2158) Syncing to the database. [17-04-04 10:18:37.4770] Slim::Music::Import::runScanPostProcessing (443) Finished background scanning. [17-04-04 10:18:37.4783] Slim::Utils::SQLiteHelper::updateProgress (439) Notify to server: ["end"] [17-04-04 10:18:37.4871] Slim::Utils::SQLiteHelper::updateProgress (463) Notify to server OK [17-04-04 10:18:37.4934] Slim::Schema::forceCommit (2158) Syncing to the database. [17-04-04 10:18:37.6213] Slim::Utils::SQLiteHelper::updateProgress (439) Notify to server: ["exit"] [17-04-04 10:18:42.2959] Slim::Utils::SQLiteHelper::updateProgress (463) Notify to server OK
So it look as if the scan would work fine with the fulltext search plugin installed, but not so well without. There actually is a difference between running the scanner with or without plugins: in the latter case the scan would run as a separate task, logging to scanner.log etc. For most users this probably is the standard behaviour, as Fulltext Search and others are installed by default. But you disabled them all. So you run into an issue which might have existed for long, but nobody encountered because they didn't run such a naked LMS.
What I wanted to say: we seem to have a bug with the in-process scanner. I'll have to investigate this. Thanks for the heads-up!
-- Michael _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
