Issues scanning new movies/tv shows onto plex

Plex Media Server Desktops & Laptops
,
1

Server Version#: Version 1.18.1.1973
Player Version#: n/a

Everything used to work fine and nothing changed but in the last 3 weeks when new movies/tv shows are added my plex does not scan for new content. I have the options turned on to automatically scan for file changes and as i stated before that nothing was changed on the server or the settings.

When I goto the settings → Library and manually “scan library files” it finishes almost instantly and nothing is added.

I checked the logs to see if the db is corrupt but I did not see anything of sorts in the logs but if i take down the server and run through the steps for corrupt database and turn plex back on and do a “scan library files” it finds the new movies/tv shows that is added. then the next day its back to the same issue.

I turned on verbose and debug logging and watched as I hit the “scan library files” and i saw that it looped through my sections and at every section it had

Oct 26, 2019 17:41:09.978 [0x7f0f814de700] DEBUG - Completed: [192.168.1.99:56705] 200 GET /library/sections (7 live) TLS GZIP 3ms 1629 bytes (pipelined: 22)
Oct 26, 2019 17:41:10.010 [0x7f0f93239700] VERBOSE - JobManager: child process with handle 13898 exited
Oct 26, 2019 17:41:10.010 [0x7f0f93239700] DEBUG - Jobs: ‘/usr/lib/plexmediaserver/Plex Media Scanner’ exit code for process 13898 is 1 (failure)
Oct 26, 2019 17:41:10.012 [0x7f0f93239700] DEBUG - Collections: Found 0 collections tags in section 14.
Oct 26, 2019 17:41:10.012 [0x7f0f93239700] DEBUG - Collections: We had 0 collections in the library already.
Oct 26, 2019 17:41:10.012 [0x7f0f93239700] DEBUG - Collections: Synced tags in section 14 in 1ms.
Oct 26, 2019 17:41:10.013 [0x7f0f93239700] DEBUG - Collections: Refreshed attributes for 0 collections in section 14 in 1ms.
Oct 26, 2019 17:41:10.014 [0x7f0f93239700] DEBUG - Collection: Refreshed visibility in section 14 in 1ms.
Oct 26, 2019 17:41:10.014 [0x7f0ef5feb700] DEBUG - Activity: registered new activity 0ba38797-fe4c-48ba-906c-56dd8ab9d78e - Processing subscriptions
Oct 26, 2019 17:41:10.014 [0x7f0ef5feb700] DEBUG - Activity: Ended activity a5a61e6e-8df3-44e7-ad86-eb1a66cc3663.
Oct 26, 2019 17:41:10.015 [0x7f0ef57ea700] DEBUG - DVR:Grabber: Cleaning up orphaned grabs.
Oct 26, 2019 17:41:10.017 [0x7f0ef57ea700] DEBUG - DVR:Grabber: Cleaned up 0 decrepit directories in 0.0 sec.
Oct 26, 2019 17:41:10.017 [0x7f0ef57ea700] DEBUG - Activity: registered new activity bd20b66b-8de6-472d-9ab1-26005ac732fa - Processing subscriptions
Oct 26, 2019 17:41:10.017 [0x7f0ef57ea700] DEBUG - DVR:Subscription: Scheduling subscriptions.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:Subscription: Initialized 1 schedulers.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:Subscription: Starting with 0 grabs, scheduled 0 active ones preemptively.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:NewSchedule: Partitioning, step one, let’s compute an absolute ordering.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:NewSchedule: Initial partitioning completed with 0 partitions.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:NewSchedule: Partitioning completed with 0 partitions.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:NewSchedule: We computed 1 alternative realities in 0 ms.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:NewSchedule: The winning schedule had score: 0 and 0 conflicts.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:Subscription: Scheduled all subscriptions in 1 ms.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - Activity: Ended activity bd20b66b-8de6-472d-9ab1-26005ac732fa.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:Subscription: There are 0 active grabs at the end.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - Activity: Ended activity 0ba38797-fe4c-48ba-906c-56dd8ab9d78e.
Oct 26, 2019 17:41:10.018 [0x7f0ef57ea700] DEBUG - DVR:Subscription: Refreshed all content in 3 ms.

any where else to look to see where the issue might be?

2

Would you please recreate the issue then capture the full ZIP and attach it.

There should have been an error which preceded the Scanner failure.
The DVR information is immaterial.

3

Logs attached from trying to run a manual scanLogs.zip (4.8 MB)

4

I’m sorry, but I need you to turn VERBOSE off again and then recreate. What I need to see has been flushed off the end of the logs.

DEBUG = ON
VERBOSE = OFF

This is the default.

Thanks.

5

thanks. debug on and verbose off. Logs.zip (4.7 MB) added some files and waited and nothing happened so hit the button for manual scan and it rushed by and still nothing was scanned.

new logs attached

6

also this time around i just restarted plex without running the corrupt db steps and manually hit scan and it was able to scan the files… so it looks like the db itself wasnt corrupt but something in plex that keeps it from scanning new files after its been running a while…

7

Would you please restart Plex,
Let it sit about a minute
Then perform another scan ?

I think I see something which can only be confirmed by seeing PMS startup.

8

Chuck - just did that and plex was able to scan the new files.

9

ok so plex’s been up and running for about 2 hours and just for giggles i ran a manual scan again and it went very fast and did not scan anything in and just quit.

attached are the refresh logs( i did purge all logs before the reboot so it should be cleaner to look at)

Logs.zip (1.8 MB)

10

I would have been helpful to know this is Docker first. I should have caught it but I do request, tagging new threads with “server-docker” when creating them. It helps me by putting me in the right thinking before getting into the thread.

One things I’m not seeing is where it scans any media.
This is making me wonder if your mappings are correct (the additional layer of how maps volumes)

Are the media files local or on a NAS volume?

11

sorry about that… i didn’t know that the tag existed, and currently its using podman instead of docker

the mappings are done via docker mounted volumes to /media.

    -v /data/plex:/config \
    -v /data/media:/media \
    -v /dev/shm:/transcode \
    -v /data/tmp:/tmp \
    -v /run:/run \

the media files are nfs mounted on podman host via NAS and all uid/gid/perms is in sync.

the same host also runs other containers that continuously access files in /data/media which mounts to /media in the plex container and those other containers are not having issues.

12

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.