Plex server with error on console

Server Version#: 4.145.1

Hi! I’m having those errors in the console:

[Req#a7cc/Transcode/0f9c2650-6ba5-4ab2-9f75-6ea11c1e7e1e/3c30405e-84dc-44a7-aebc-815f38cb1cab] [eac3_eae @ 0x1540240fdb80] error reading output: -5 (I/O error)
[Req#a841/Transcode/0f9c2650-6ba5-4ab2-9f75-6ea11c1e7e1e/3c30405e-84dc-44a7-aebc-815f38cb1cab] Error while decoding stream #0:1: I/O error

Some files are not playing also, specially if they are in HEVC.

Any thoughts? Thanks in advance!

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.

Would you please recreate the error with DEBUG logging enabled (it is on by default).

After recreating it, Download the server logs (Troubleshooting - Download Logs)

Attach the ZIP file here please.

Thanks folks! I attached my console screen and the log file.

I’m using PLEX docker on Unraid.

Plex Media Server Logs_2025-04-08_05-24-50.zip (3.6 MB)

take a look at the /tmp directory, permissions or something may have gone sideaways there. (just peaked at your logs for that info)

Hi!

Those are the permissions fot /tmp:

Here is the content:

Should I delete everything there?

Thanks for any comment on this!

Hi @ChuckPa ! Any thoughts on the log?

very sorry. been swamped.

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.

  1. PMS creates a temp folder
  2. PMS sets a Notify event for that folder
  3. PMS launches FFMPEG for the video
  4. PMS launches EAE for the dolby audio.
  5. Error occurs if there is no audio file to load and merge with the video

Most common causes:

  1. Notify table is full (too many directories being watched – fills up the max_users_watches table in the Linux kernel
  2. 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:

  1. Count to total number of directories being used for ALL media
  2. See what the kernel currently allows ( fs.inotify.max_user_watches )
root@lizum:/glock/media/testfiles# sysctl -a | grep max_user_watches
fs.epoll.max_user_watches = 14541022
fs.inotify.max_user_watches = 1048576
root@lizum:/glock/media/testfiles#
  1. 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 )

  2. 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:

fs.inotify.max_user_watches=<YOUR_NEW_VALUE>

For general Linux, here’s how to do it.

Thanks @ChuckPa. I have 11.253 folders and I used this command:

echo  fs.inotify.max_user_watches=262144  >> /etc/sysctl.conf

I checked the sysctl.conf and the new line was there. I restart the docker but I still having the errors:

Hi @ChuckPa ! Any other thoughts on this?

Thanks in advance!

Eduardo

@edal86

Did you restart the host to make it active ?

Alternatively, sudo sysctl -p will make it active immediately.

@ChuckPa

Yes, I did…

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 )

Thanks for this! I’m looking forward.

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