Scans failing can cause a soft-lock

[J-Stuff]

Scans failing can cause a soft-lock

[ShaneIsrael]

So this tends to happen if there is a non video file in the folder that ffmpeg tries to load or a corrupt video file.

2023-06-06 07:41:05.434001+00:00Message: 'Could not extract video info'

I would double check your mount point for videos and make sure there isn't any hidden non-video files. If there are, remove them and try a scan again and it should work. If there isn't, you may have a corrupt video file somewhere.

If you look closely at the stacktrace you'll see that the file ffmpeg is having an issue with is this one.

2023-06-06 07:41:05.434012+00:00Arguments: (CalledProcessError(1, ['ffprobe', '-v', 'quiet', '-print_format', 'json', '-show_entries', 'stream', '/processed/video_links/d76bbe5d3276a41d08fff725f5f7e66f.mp4']),)

/processed/video_links/d76bbe5d3276a41d08fff725f5f7e66f.mp4

Thats a symlink that fireshare creates that points to the actual file. Find the file that it is pointing to and inspect it to make sure that it is indeed a video file and isn't corrupt or maybe something else wrong with it.

To figure out where that symlink is pointing you can run this command against it.
stat d76bbe5d3276a41d08fff725f5f7e66f.mp4

[J-Stuff]

I think I figured out the problem.
My scan interval was set to every minute. Fireshare was scanning files that were in the process of being uploaded to the SMB share (over the Network). After setting my scan interval to 120 minutes, the malformed file error seems to have stopped

[ShaneIsrael]

@J-Stuff while that is a decent fix, you can still run into issues in the event you start uploading a file right before the scan starts.

If you really want to make sure this issue never happens again, I would upload files to a folder that is not watched by fireshare first and then move the files (either manually or with some script) so that fireshare doesn't attempt to scan a partially moved file.