Interrupted library scan - upper limit of 11886 pictures?
for many years I was happy user of Serviio (1.9.2 and earlier) on Windows 10 and earlier. But since several months, Serviio 1.9.2 doesn't serve my content completely any more. It started with Serviio having problems to find and serve added files correctly. So I switched to "polling" and using "Force refresh", as described in other posts. This worked for a while. But in the mean time, after more images were added to my hard disk, even this doesn't help any more to serve all files. So I did a clean-up and tried from scratch. This is the steps I took and the resulting behavior:
- Uninstall Serviio 1.9.2
- Delete library and old logs
- Reinstall Serviio 1.9.2
- Turn on DEBUG in file log4j.xml
- Stop server
- Add single folder D:\Bilder\Fotos in polling mode to library. It contains 38526 image files in three layers of subfolders
- Wait until scanning ended, result:
Serviio stops scanning after 11886 files.
This is reported by the Serviio GUI and confirmed by the Serviio log.
But actually there are 38526 pictures.
-> Library is incomplete
- Click "Force refresh"
Numbers and served content doesn't change.
Only the log file contains two more lines:
2018-09-14 18:04:47,442 INFO [LocalLibraryManager] Starting manual library scan
2018-09-14 18:04:47,443 INFO [LibraryOneTimeScanner] Interrupting library scan
To me it looks like some unintended interrupt of the library scan.
I checked the folder where scanning stopped. There is no specifically suspicious file there:
No corrupt file, all with read permission, no unusual file or image size, no unusual file format.
I tried this also with Serviio 1.9.1 - same problem.
I attach my log files.
I also tried to attach my database, but it's too big, even when zipped (~4MB).
So I tried to create an archive split into files smaller than 500kB. Unfortunately that results in more than the allowed 3 attachments.
I can provide the library by email to anybody who is willing to help.
I would really like to stay with Serviio (instead of movint to Plex, for example), but I need help to solve the reported issue.
Thanks,
Rolf