I’d start by checking your hardware logs. Errors displayed on the console like that are not usually application errors, but are indicative of potential hardware problems. And errors where some files but not others are not available may be a pointer of failing storage.
Apr 07, 2025 20:36:52.000 [22846242962232] ERROR - [Req#44f1d/Transcode/f3a89269-f362-450f-89c9-4ae55c765d8d/20f205c9-b351-4167-9f2e-cfb0b6d4dc0f] [eac3_eae @ 0x146b4db50b80] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-f333e80e-d54a-484b-9744-a9aa0beeff5d/EasyAudioEncoder/Convert to WAV (to 8ch or less)/f3a89269-f362-450f-89c9-4ae55c765d8d_72835-0-2235.wav'
Apr 07, 2025 20:36:52.001 [22846214212408] ERROR - [Req#44ff2/Transcode/f3a89269-f362-450f-89c9-4ae55c765d8d/20f205c9-b351-4167-9f2e-cfb0b6d4dc0f] [eac3_eae @ 0x146b4db50b80] error reading output: -5 (I/O error)
Apr 07, 2025 20:36:52.001 [22846474734392] ERROR - [Req#44ff3/Transcode/f3a89269-f362-450f-89c9-4ae55c765d8d/20f205c9-b351-4167-9f2e-cfb0b6d4dc0f] Error while decoding stream #0:1: I/O error
This error means that the file/directory doesn’t exist.
Could not read ‘/tmp/pms-f333e80e-d54a-484b-9744-a9aa0beeff5d/EasyAudioEncoder/Convert to WAV (to 8ch or less)/f3a89269-f362-450f-89c9-4ae55c765d8d_72835-0-2235.wav’
How it’s supposed to work.
PMS creates a temp folder
PMS sets a Notify event for that folder
PMS launches FFMPEG for the video
PMS launches EAE for the dolby audio.
Error occurs if there is no audio file to load and merge with the video
Most common causes:
Notify table is full (too many directories being watched – fills up the max_users_watches table in the Linux kernel
tmp directory is on a network drive where notify will not work.
Given the most common cause is max_user_watches fills.
( 8192 directories on some, 65535 directories on other Linux kernels )
the solution is to:
Count to total number of directories being used for ALL media
See what the kernel currently allows ( fs.inotify.max_user_watches )
If needed, increase it.
– newer Linux kernels dynamically set the table size based on memory available. (be careful when limiting a container’s memory – it can hurt you here )
Round up number of directories in use to next integral multiple of 32768
(it’s ok to increase another 32768 if you’re frequently adding and have plenty of memory)
On regular Linux kernel,
– ON HOST, edit file /etc/sysctl.conf
– at bottom of file, add:
I will try to recreate this so we can move forward
Not sure what is causing it but will try some ideas to see if I can recreate it at the OS level. (this is an OS/kernel issue - inotify )