I can test more this week, but I noticed it specifically if a movie is “upgraded” to a better version, so a movie that already existed, but I converted it to a different format, and am scanning the directory again. But I do not have NFO files in the folder with the movies or anywhere if that helps. I’ll be able to get better logs later this week…maybe @farfetchd has some newer logs?
I am having the same issue trying to scan from the command line. My hunch is that it has something to do with the NEW scanner (Plex Movie) since I think I have been seeing this issue ever since my library was switched from the OLD scanner (Plex Movie Scanner). The core dumps are created ever time I try to scan a directory. Scanning from within Plex is working, and it looks like that uses the “–match” action instead of “–scan”. I’m going to mess around with that to see if match works instead of scan from the command line.
Thanks for the reply – yes I’ve tested with both NFO and without NFO.
I’ve looked at the logs between a working instance (older version) to the newer version – and it looks like the new scanner/cli scanner refuses to go past acknowledged the scan…
It’ll find the files… to scan then seg fault… unfortunately without debugging tools for the cli app I can’t diagnose further.
I guess I can test on the windows client and debug, but I doubt it’ll be replicated… I’ll wait for @ChuckPa to respond
Is it possible for me to get a copy of the actual file to test here with ?
If there is a problem with the file, I’ll find it.
If there is a problem with the scanner, I’ll have what I need to give it to Engineering so they can fix it.
Is the LD_LIBRARY_PATH environment variable set? Either in the docker exec command or in the docker create/compose itself? If Plex Media Scanner is crashing immediately that may be the reason.
Yes LD path is set, I’ve actually shelled into the docker container, and ran the commands myself… it seg faults with the scan/refresh command arguments, runs fine for tv/series just not for movies.