Scanning media Library forever

[treason 11]

I can't seem to complete a library scan anymore. It stops are 10.2% indefinitely. I've been looking through the logs, but they are so verbose and massive that I dont even know what I'm looking for. Is there a way I can grep for a string in this log related to the halt? Would it be called `LibraryMonitor` ? Is there a way to disable these repetitive "Info HttpServer" logs?

 

Anyhow, I would post the log but it's so big and has so much private information I'm hoping to debug myself.

 

Anyone have any tips?

[Capt.Insano 3]

My library scans have also increased so hugely in length that they appear static since the 6030 release.

 

I am running Emby via Docker on a 16 cpu thread server and my Library Scan which prev took seconds/minutes to complete is taking over an hour to complete.

 

htop is also only showing 1 cpu thread being used from what I can see and my logs are currently being filled with:

2016-08-05 18:36:27.5881 Info ImageProcessor: Completed creation of image collage and saved to /config/cache/temp/0f6d9cef7b154dfebf9191598837083f.png
2016-08-05 18:36:27.7122 Info ImageProcessor: Creating image collage and saving to /config/cache/temp/682333a2b4cd46a8a756edd5629b0e29.png
2016-08-05 18:36:27.8462 Info ImageProcessor: Completed creation of image collage and saved to /config/cache/temp/682333a2b4cd46a8a756edd5629b0e29.png
2016-08-05 18:36:27.9609 Info ImageProcessor: Creating image collage and saving to /config/cache/temp/140848557e7b4f55bcc3562f295b7e8c.png

over and over again.

 

Any changes in the 6030 release that could have caused problems with library scanning?

[treason 11]

Yes, Captain insano shows no mercy, and neither does this scan.

 

It is a new problem with the latest release. I wish I knew how to debug

Edited August 6, 2016 by treason

[treason 11]

Also there's a JS bug on the settings screen, so the spinner never stops spinning

 

`TypeError: session.TranscodingInfo is undefined`

web/scripts/dashboardpage.js?v=3.0.6030.0 line 29, col 29

[treason 11]

The js bug was fixed by logging out an in again. The long library scan was fixed by removing a huge photos collection I had.

[Luke 42085]

Great, thanks for the info.