Server Version#: 1.32.1.6983
Player Version#: 4.104.2
Plex scanner constantly gets stuck on 1 season or 1 movie, only way to recover is with a restart which sometimes crashes the docker and have to kill the PID completely. If the scanner gets stuck I’m then unable to ad new media.
Database is no corrupted, tried with a working one
Plex dance done
This is a Docker on unraid.
Show me the exact filename and structure please ?
I will test on my Unraid installation.
Well I have done some testings, and spun up a test media server with 1 movie and sure enough it’s not able to scan, I can’t find anything in the logs that says error reading it, I even downgraded to a month old release and downgraded my unraid. I don’t know what is happening.
example test filename path is
/mnt/user/data/media/gdrive/movies/Zoolander 2 (2016)/Zoolander\ 2\ (2016)\ [imdb-tt1608290][Bluray-1080p][8bit][x264][DTS\ 5.1]-DRONES.mkv
I have same issue with all gdrive files, but I have no issue pulling and playing the files on another machine
How are you mounting the gdrive folder? I’ve heard of people getting gdrive session api throttles when hitting bandwidth caps, hitting too many files too quickly, etc - which sounds like might be happening. If you pull some of the data to a local share, do you still have issues?
FYI that does nothing you need {imdb-tt1608290} and I would recommend minimizing the number of square brackets you have. IE Zoolander 2 (2016) {imdb-tt1608290}[Bluray-1080p 8bit x264 DTS 5.1-DRONES].mkv
I tried with a file that is just MOVIENAME (YEAR), Jellyfin has no issue scanning either one.
no throttling, I use a 4tb cache just for rclone and local file is fine too, I spun up a test jellyfin with same movie and it scans and plays fine.
This part of your defintion (which isn’t needed to match it) is incorrectly bracketed.
[imdb-tt1608290]
PMS uses { } (braces, not brackets)
Would be
{imdb: tt1608290}
Anything in squared brackets [ ] is ignored during matching.
Designations in braces { } are directives to the matcher.
what do you mean by " Designations in braces { } are directives to the matcher." could you give more information please ?
Anything you don’t want Plex to see you put in square brackets. This makes sure things like file information don’t accidently get used to match a video
The Matrix (1999) [1080p.HEVC.x265].mkv <–square brackets
A matching tag from IMDB OR TMDB gets put in curly brackets to help the scanner identify it
The Matrix (1999) {imdb-tt0133093}.mkv <–Curly Brackets
To add to Jay,
For TV series you can use {tvdb - NNNNN} to specify TheTVDB as the naming source.
ok, thanks for the info,
i have exactly the same problem than @Angelgtc87 the scanner gets completely stuck with an infinite loop for specific media, i am also using google drive and rclone for all my medias, i checked the rclone logs to check if there was any api calls failed with the bandwidth caps and the logs are OK. i’m using the official docker plex container and i’m also using square brackets instead of curly brackets for identifying my medias, but i think that is not the cause of this issue
the file stucked is “Le Grinch (2000) [imdbid-tt0170016]” and i don’t know why
using latest version of PMS: 1.32.0.6973
Plex Media Server Logs_2023-04-24.zip (3.7 MB)
UPDATE: ok after cleared the cache folder of rclone (3to …) and using the PlexDBRepair of ChuckPa (instructions followed here), it seems that the scan not get stucked anymore. But i hope that i won’t have to do the same things if it happens agains
I found a solution too, nothing to do with my names since they been working for past 3 years, my issue was plex not having full rights to my rclone mount somehow, I noticed by going to my docker plex console and doing an ls -la that files were showing as hotio, or plex user depending on container, I switched to official docker and file ownership are nobody:users, switched my mount command to PID 99 and GUID 100 so the mount is nobody:users as well and plex had no issue scanning them, I don’t know what changed my mount always worked even if files were owned by root and had a 777 permission.
In all this Jellyfin and Emby had no issue with my previous settings.
Le Grinch (2000) [imdbid-tt0170016] ← incorrect and not being used for anything
Le Grinch (2000) {imdb-tt0170016} ← correct format
You both have issues with the scanner getting stuck and you also both happen to be using square brackets to enclose the imdb id
I’m not saying this is the reason but it’s an odd coincidence
Even if it has nothing to do with your problem, I wouldn’t waste my time inputting those id’s
The files are being matched by name alone, and those imdb id’s aren’t doing anything
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
