Server Version#: Version 1.40.5.8921
Player Version#: Version 4.133.0
Server is running as a docker container on the synology.
I have been trying to watch Slow Horses and the episodes seem to start but the screen just goes dark and the I eventually ( after just over a minute ) get a message saying
Playback Error
An unexpected playback problem occurred
Can you grab the server logs shortly after it errors out? That will help track it down.
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
log files attached
Plex Media Server Logs_2024-09-11_08-15-24.zip (5.0 MB)
Sep 11, 2024 08:15:00.000 [140050110675768] ERROR - [Req#41f201/Transcode/zouaiv2abu02lo6e9i3xolzs/ad10d797-d376-4a00-bbde-dddcef2d4614] [eac3_eae @ 0x7f74ae156700] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-fc71753a-58d3-4166-bcef-d10feae89cbd/EasyAudioEncoder/Convert to WAV (to 8ch or less)/zouaiv2abu02lo6e9i3xolzs_22418-0-16.wav'
Sep 11, 2024 08:15:00.001 [140050110675768] ERROR - [Req#41f203/Transcode/zouaiv2abu02lo6e9i3xolzs/ad10d797-d376-4a00-bbde-dddcef2d4614] [eac3_eae @ 0x7f74ae156700] error reading output: -5 (I/O error)
Sep 11, 2024 08:15:00.002 [140050110675768] ERROR - [Req#41f204/Transcode/zouaiv2abu02lo6e9i3xolzs/ad10d797-d376-4a00-bbde-dddcef2d4614] Error while decoding stream #0:1: I/O error
Maybe try this: TrueHD not loading/infinite buffering - #7 by plumptree
OK - My head hurts …
Had a look at the link (Thanks for that), the lead me to another that was talking about not being able to run the EAE stuff due to the /tmp FS having no exec set. Aha I said, cause I’m using a NAS /tmp is tmpfs which is in RAM and the mount is noexec so I remounted to see if that was the issue, still the same.
Then I thought, the PMS is a container so maybe I can get it to use another directory is I tried setting TMPDIR as an environment variable for the container - no joy.
Then I thought, lets map a volume /tmp directly into the container and again no joy.
I also tried removing the EAE codec that one person suggested but the container recreates it when it starts so that didn’t work. either.
So I don’t know if this is an issue cause it’s in a container or if it still would happen if I were running the straight synology PMS.
On Synology, you must handle the kernel table size FIRST.
Docker is 100% dependent on host resources.
When you get the EAE error, and you have a lot of directories, the notify table (which is how PMS knows you’ve added media) fills up.
EAE requires two slots in that table. Therefore, if the table is full, EAE cannot run and will give the error.
There is a procedure to address this for Synology.
Give a read and ask with any questions.
What a star - thank you
Worked a treat.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
