Hello,

Recently have an issue where Plex is constantly scanning my library.

I have made no recent changes that I can think of.

It's constantly looping as if a system wide filesystem change is constantly being made on the Unraid, triggering the scan.

The member at Plex (chuckpa) asked if I could ask someone here the following:

Would you mind asking the Unraid folks what that error means?

What PMS is telling us is :

1. It wants to start another processing thread to scan/do something else
   ( In Linux terms, it want’s to perform some variant of fork() )

2. Unraid is saying “No, No resources”

Possibilities (to my knowlege)

1. System-wide thread count limit

2. Insufficient memory

3. Insufficient swap (to allocate but not use)

My debug:

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.

I've looked at the full logs.

The only thoughts we have (support & engineering) is the host thinks it's run out of either thread or virtual memory.
None of that makes any sense given the resources shared in the Plex forums.

Don't know if this is a config issue or something else.

Jun 24, 2025 12:09:46.427 [23284410592056] ERROR - ETP: Uncaught exception in I/O service: thread constructor failed: Resource temporarily unavailable

Being out of ideas, I suggested @willyv post here

Edited June 24, 20251 yr by ChuckPaPlex
specific error from logfile

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!