Intro detection taking very long time (10 hrs so far on one season)

Plex Media Server
1

Server Version#: 1.19.3.2843

I run plex in an ubuntu 20.04 LXC container on proxmox. My Plex library is stored on a 5 disk raidz zpool, and the server has a Ryzen 7 3700x for a cpu.

Detecting intros has been churning away at a single 10 episode series ever since I updated my plex server this morning (10-ish hours ago). The transcoder appears to be using ~7% of the cpu pretty consistently, so I think it’s still working. Is this a normal time interval for this feature? is something not working correctly? Can I change a setting so that it will use more CPU power to finish faster?

2

Single threaded, CPU based scanning.
As I understand it, it’s to be a maintenance style task which will pick up the new videos added. Yes, initial setup will take a while to churn through large libraries.

3

@ChuckPa I just looked at the plex console, because it’s still working on the same season 14 hrs later, and I noticed these errors:

May 23, 2020 02:25:57.000 [0x7f4d6a7fc700] Error — [Transcoder] [eac3_eae @ 0x104b780] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-17937121-61ce-4907-9a60-dbaaa0d799bc/EasyAudioEncoder/Convert to WAV (to 8ch or less)/38a9caee-c18d-452e-989d-c677778f9c31_3891-0-459.wav'
May 23, 2020 02:25:57.000 [0x7f4d1bfff700] Error — [Transcoder] [eac3_eae @ 0x104b780] error reading output
May 23, 2020 02:25:57.000 [0x7f4d6b7fe700] Error — [Transcoder] Error while decoding stream #0:1: Input/output error

Are these a completely separate issue, or could this be why it’s taking so long? The error appears to repeat about once every second.

4

without seeing the logs (from startup) , there is no way of knowing.

The reason for this is the EAE & transcoder need 2 “Notify” slots to work together.
If there are a lot of monitored Music or Photo directories and the Notify list fills the Linux kernel table then this type error will happen.

The error you’re looking for is “No space left on device” from “Notify”

5

I’ve attached my logs. I’m not seeing any “Notify” errors, but I could have missed them. It only seems to be happening when getting intros from certain seasons of certain shows.

Plex Media Server Logs_2020-05-23_11-50-46.zip (3.0 MB)

6

@ChuckPa I’m still having this error. Every morning I wake up and Plex is trying to detect intros for the same season of the same show over and over again. Is there any additional information I can provide to help trouble shoot this issue?

7

Here’s updated logs, in case that’s helpful. It’s frustrating to have so much of my server’s processing power being wasted on this task that never seems to finish.

Plex Media Server Logs_2020-05-27_15-36-39.zip (4.5 MB)

8

@ChuckPa Would you possibly be able to help me with this? It’s STILL working on the same season, almost a week later.

9

I hate to bump this again, but is there anyone at plex who can help with this? My server keeps trying to generate intro markers for the same season of a show over and over again.

10

@ChuckPa It appears there was a permissions issue in the codec folder. Every codec was missing the execute permission, and a chmod fixed it. This must be a bug in the debian installer?

11

The Debian installer doesn’t create nor manage the directory.
When PMS creates the directory, everything from Plex Media Server and below, it sets it up correctly.

An external script / other action interfere in there? Moved the metadata location by using copy instead of tar?

12

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