Logging Error After Scan That Prevents Further Scanning
torrabsolute2 opened this issue · comments
Describe the bug
Whether a manual library scan or a scheduled library scan, the cli shows "--- Logging error ---". I think that this keeps the scan process as currently active and prevents further scanning.
To Reproduce
Steps to reproduce the behavior:
- Manually scan or wait for the scehduled scan to begin
- See error
Screenshots
https://imgur.com/rtJcq1C
There was a directory that had a bunch of .jpgs in it. I deleted those and I think that mightve solved it? Unsure but it doesnt error on scanning now.
edit: turns out that it also had enourmous files in it as well.
Seems like the scan is error'ing while it tries to get video info for one of your videos. Might be that it's corrupt? Either way, because its breaking during the scan the lockfile isn't getting removed which is why subsequent scans are being aborted. it thinks the scan is still running when it's not.
You can solve this by simply restarting the docker container and it will remove the lockfile on startup. However, it will probably keep breaking every time it tries to scan that video.
You might want to inspect the video at /processed/video_links/21652*****.mp4 (its in your logs) Thats a symlink that fireshare creates to the actual video. I would try removing the actual video and the symlink and see if the scan works without issue. If so, its something about that video file in particular.
I looked and that folder that was deleted had emourmous video files in it as well. I just deleted it and everything is resolved! I can't dig into it more but im guessing this had a hard time with huge files.
Depending the size that could definitely be the case. I've tested files in size up to about 30 gigabytes in size and haven't had an issue but I'm also running the software on a fairly beefy system.