Server Version#: 1.41.8.9834
Since yesterday, my Plex library has been full library scanning. I have tried to use Chuck Pa’s DB tool. I have rebooted my entire unraid server. Nothing seems to work. I have not made any changes that I’m aware of that would trigger these full library scans.
It appears to be looping as I’ve noticed it’s scanning over the same movies/shows/libraries over and over.
Please help!
Server DEBUG logs ZIP file please ?
(this will contain the scanner logs too)
Thanks for the logs.
PMS is attempting to scan the media but Unraid is unable to complete the scan
Jun 24, 2025 12:09:46.423 [23284410592056] ERROR - ETP: Uncaught exception in I/O service: thread constructor failed: Resource temporarily unavailable
Jun 24, 2025 12:09:46.424 [23284410592056] DEBUG - Push: Processing new content in section 6 for 34 users.
Jun 24, 2025 12:09:46.424 [23284410592056] DEBUG - Push: There are 0 new top level things for filter '0' (movie.addedAt>>=1750739090&sort=movie.addedAt:desc&type=1).
Jun 24, 2025 12:09:46.425 [23284451138360] DEBUG - Skipping over directory 'FLCL (2000)/Season 04', as nothing has changed; removing 3 media items from map.
Jun 24, 2025 12:09:46.425 [23284451138360] DEBUG - Activity: updated activity 9bc322a1-5116-4e3a-9e1a-a79afa0870a5 - completed 42.7% - Scanning Anime
Jun 24, 2025 12:09:46.425 [23284451138360] DEBUG - Scanner: Processing directory /media/tv-anime/FLCL (2000)/Season 05 (parent: yes)
Jun 24, 2025 12:09:46.425 [23284410592056] DEBUG - Push: There are 0 new top level things for filter '0x152d0c2fd138' (movie.addedAt>>=1750739090&sort=movie.addedAt:desc&type=1).
Jun 24, 2025 12:09:46.426 [23284410592056] DEBUG - Push: There are 0 new top level things for filter '0x152d0ad46ba8' (movie.addedAt>>=1750739090&sort=movie.addedAt:desc&type=1).
Jun 24, 2025 12:09:46.427 [23284410592056] ERROR - ETP: Uncaught exception in I/O service: thread constructor failed: Resource temporarily unavailable
Jun 24, 2025 12:09:46.427 [23284410592056] DEBUG - Push: Processing new content in section 1 for 48 users.
Jun 24, 2025 12:09:46.428 [23284410592056] DEBUG - Push: There are 0 new top level things for filter '0' (movie.addedAt>>=1750738789&sort=movie.addedAt:desc&type=1).
Jun 24, 2025 12:09:46.428 [23284451138360] DEBUG - Skipping over directory 'FLCL (2000)/Season 05', as nothing has changed; removing 3 media items from map.
Jun 24, 2025 12:09:46.429 [23284451138360] DEBUG - Activity: updated activity 9bc322a1-5116-4e3a-9e1a-a79afa0870a5 - completed 43.3% - Scanning Anime
Jun 24, 2025 12:09:46.429 [23284410592056] DEBUG - Push: There are 0 new top level things for filter '0x152d27fdde68' (movie.addedAt>>=1750738789&sort=movie.addedAt:desc&type=1).
Jun 24, 2025 12:09:46.429 [23284451138360] DEBUG - Scanner: Processing directory /media/tv-anime/Samurai Champloo (2004) (parent: yes)
Jun 24, 2025 12:09:46.430 [23284410592056] DEBUG - Push: There are 0 new top level things for filter '0x152d0c305218' (movie.addedAt>>=1750738789&sort=movie.addedAt:desc&type=1).
Jun 24, 2025 12:09:46.430 [23284410592056] ERROR - ETP: Uncaught exception in I/O service: thread constructor failed: Resource temporarily unavailable
Jun 24, 2025 12:09:46.430 [23284410592056] DEBUG - Push: Processing new content in section 6 for 34 users.
Uncaught exception in I/O service: thread constructor failed: Resource temporarily unavailable
You have a volume which is offline but still referred to in PMS ?
Do you have a thread limits on the container ?
I do not have a volume offline.
I do not have a thread limiter on the container.
I remapped my folders for each library to see if that would help, but I just went through each library and all were correctly mapped.
Would you mind asking the Unraid folks what that error means?
What PMS is telling us is :
It wants to start another processing thread to scan/do something else
( In Linux terms, it want’s to perform some variant of fork() )
Unraid is saying “No, No resources”
Possibilities (to my knowlege)
When did you upgrade to 1.41.8 ?
Did you ever see any behavior like this on any version prior ?
Not really sure who to take this to. Should I take to Unraid forums? Plex > Unraid forum?
I upgraded probably morning after it was released to public.
Never seen behavior like this.
I downgraded just now to 1.41.7 and it was quiet for a minute then started scanning again.
I’d not recommend using 1.41.7 due to the known DB problems.
Would you be willing to downgrade to
(change the version in the container definition and let it pull new code only)
If it reoccurs, then we know it’s a system limit problem with unraid
ALSO,
check what unraid is reporting for max-threads
[chuck@lizum ~.2004]$ cat /proc/sys/kernel/threads-max
510292
[chuck@lizum ~.2005]$ free -m
total used free shared buff/cache available
Mem: 63868 13339 7562 358 42967 49473
Swap: 61034 222 60812
[chuck@lizum ~.2006]$
root@Gerbil:~# cat /proc/sys/kernel/threads-max
255697
root@Gerbil:~# uname -a
Linux Gerbil 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz GenuineIntel GNU/Linux
root@Gerbil:~#
root@WillyCloud:~# cat /proc/sys/kernel/threads-max
511355
root@WillyCloud:~# free -m
total used free shared buff/cache available
Mem: 64082 17283 1647 1204 47118 46798
Swap: 0 0 0
root@WillyCloud:~# cat /proc/sys/kernel/threads-max
511355
root@WillyCloud:~# uname -a
Linux WillyCloud 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 12th Gen Intel(R) Core(TM) i5-12600K GenuineIntel GNU/Linux
root@WillyCloud:~#
I’ve also downgraded to 1.41.6.9685-d301f511a. Same issue.
You have no swapfile / partition defined ?
I honestly don’t know what that means. As far as I know, I’ve never had one.
Then I recommend asking further in the Unraid - Plex forum.
All indications are you’ve run out of virtual memory or threads.
I highly doubt you’ve run out of threads.
I’ve started a thread here:
https://forums.unraid.net/topic/191460-issues-with-plex-constantly-full-library-scanning/
Not sure if they’ll know what to do with this info. Did I word it correctly?
That was good.
I replied as well.
So I went ahead and stopped all containers but Plex and all was fine.
Slowly introduced each container and found the problem container.
It was Soulseek.
I have never had problems in the many years I’ve used, but sure enough as soon as I ran it, a library scan would trigger.
Deleted and installed more modern container/app version “slskd” and we’re all good!
Confirmed , not a Plex problem?
Thanks for updating us.
Please mark solved appropriately.
Confirmed not a Plex problem. Thanks for your help!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
