I get proper library updates upon a fresh start of PMS, but after a few hours, the Activity menu shows “Scanning some library: some folder” and the progress shown does not change. When I inspect the system, the Plex Media Scanner process is idle and has no media files/directories open. This started after a recent update to 1.25.4, and the second update I installed still has the same problem.
In the logs (without verbose logging enabled), I only see entries like these for each of my libraries:
Jan 29, 2022 22:13:26.272 [0x7f1fef50fb38] Info — It's been 83956 seconds, so we're starting scheduled library update for section 10 (Movies)
Jan 29, 2022 22:13:26.272 [0x7f1fef50fb38] Info — It's been 84893 seconds, so we're starting scheduled library update for section 5 (TV Shows)
strace output for the Plex Media Scanner process:
strace: Process 55891 attached with 4 threads
[pid 55893] futex(0x7f404ec91974, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 55891] futex(0x7ffc77b01194, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 55892] rt_sigtimedwait([HUP INT QUIT TERM CHLD], <unfinished ...>
[pid 55895] select(49, [48], [], [], {tv_sec=36, tv_usec=385939}
This may not be the response you want but I’ll post it regardless.
I’ve seen many topics on this in the last week. From what I can see from pretty much all of them is that the folks with problem have poorly named media and/or have not followed the plex naming of media for tv and movies libraries.
Will plex address why the scanner is stopping now, maybe but you can most certainly fix or at least help yourself by renaming your media to match what plex expects.
The plex scanner know what they expect to perform well. It will try and pickup poorly named stuff but the scanner then becomes less efficient and I suspect a recent change has now got to a point where its started to fail.
There has also been many comments of, well it worked last week so why does it not work now ? All I can comment on that and say is it works until it doesn’t if you have decided not to follow the naming scheme.
Plex Media Server 1.25.3.5409 and subsequent releases Plex Media Server - #479 by drzoidberg33 contain a number of scanner changes from plex which could explain why you are seeing problem.
Two things …
give actual examples of how your media is named, screen shots if you can so we can compare. Movie and TV please.
upload a fresh copy of your server logs so we can help debug your actual problem
Hey @anon5074910, been having problems with my scanning hanging too. Specifically, it happens with non-TV/Movie libraries. Here’s where it hangs with the Audiobook library. The attached library has hung on Jade City.
Server Version#: 1.25.5.5492 in the linuxserver Docker image.
I’ve also tried downgrading to an older version, but I think the Plex persistent storage is overriding the image version.
There doesn’t seem to be any rhyme or reason to it, though it does appear to hang on some items more than others. I’ll do a restart, then it’ll go and hang on another item.
Took a quick look at your logs. I suspect your error is different to the other reports on this thread as its related to non TV & Movies libraries and is using audiobooks. As I don’t have music or audiobooks in my library your errors are most likely beyond my knowledge.
In saying that I did see from your audiobook library is using Plex Music Scanner. No idea if that is correct or supported. If I had to guess that music scanner is most likely having a hard time scanning & matching your audiobooks and then ultimately failing, hanging
I’d suggest opening your own thread on this error and see if someone from plex or a ninja could jump in and help. What might be the best library type for audiobooks ? Not sure music is.
We’re not entirely sure what’s causing this issue yet but there was a not insignificant change to our http client code in 1.25.4 which seems like it may be related. There is a bug fix for a potential deadlock in this code that will be in the next beta which I hope is the culprit here.
The beta should be out next week sometime. I’ll follow up here.
As expected, there seems to be a problem with the version.
The new version that came out today, 1.25.6.5545 works normally.
Thank you for your active efforts to solve it.
