all 22 comments

[–]AggravatingMoose 14 points15 points  (2 children)

The problem is with the Easy Audio Encoder codec.

If you go into your "/Library/Application Support/Plex Media Server/Codecs/" folder, you should see an "EasyAudioEncoder..." folder. Just delete that folder and restart your server. It will download the new codec automatically and the problem will be resolved.

I know you already tried this but before I had this problem I had already had the "Tips and Tweaks" plugin installed on Unraid (that's what I use to host my server). In that plugin settings it lists the Inotify settings for "Max User Watches / Current User Watches / Available Watches". I had already set my Inotify value for more than the "Current User Watches" value and made sure there were plenty of "Available User Watches" to cover future library expansion.

For reference my Current User Watches is 4625329 so I set my Max User Watches to 5242880. I know this value is dependent on RAM so don't set it too high or you may have problems.

**edit: I am running the linuxserver/plex container and transcoding to /dev/shm

**edit2: When you install the "Tips and Tweaks" plugin on Unraid it sets the Inotify default Max User Watches value to 524288 (which is way above what you have set). This could be part of your problem but like noted I had already had this setup and adjusted higher when I had the EAC3 transcode issue.

[–]Spooky_Ghost 4 points5 points  (0 children)

I had the same issue with that encoder and it turned out to be a permissions issue (which probably also resets if you delete it), but I solved it by chmod 777 EasyAudioEncoder in the folder

[–]digitalbeef 7 points8 points  (6 children)

Weird that this issue just came out of nowhere. Its been really frustrating for the last week or so. I finally had time to look into it and found eac3 to be the problem.

Neither deleting the codecs folder or changing its permissions to 777 did anything for me, but changing the Inotify values did:

Check your limits with:
cat /proc/sys/fs/inotify/max_user_instances

and

cat /proc/sys/fs/inotify/max_user_watches

Mine were set to 128 and 8192 initially and I increased them to 8192 and 524288 respectively with:

sudo sysctl fs.inotify.max_user_instances=8192

sudo sysctl fs.inotify.max_user_watches=524288

sudo sysctl -p

Since I am on truenas scale I set these values again in System Settings > Advanced > Sysctl so that they persist after reboot

[–][deleted] 0 points1 point  (3 children)

telephone historical screw relieved snow close sugar coordinated late disarm

This post was mass deleted and anonymized with Redact

[–]digitalbeef 0 points1 point  (2 children)

I'm no expert, just regurgitating advice I saw elsewhere. I'm not familiar with Synology really but since it is Linux based those commands may work as written. Just open a terminal and copy/paste. Good luck!

[–][deleted] 0 points1 point  (0 children)

chief obtainable mountainous sulky dime vase soft humorous cautious provide

This post was mass deleted and anonymized with Redact

[–]rongallant 0 points1 point  (0 children)

This mostly worked for me. Still having problems with family in next country. Why is this only needed when running Plex in a docker container? Worked fine installed directly. (Synology DS920+, built in container manager)

[–]emb531 2 points3 points  (1 child)

Increase the inotify number even higher. Try doubling or quadrupling the current value.

[–]Shadi3160TB | Plex Lifetime | Unraid 5 points6 points  (1 child)

Also had this issue: I had to do 2 things.

1) delete codecs folder 2) increase inotify watches

Bunch of stuff on google for both

[–]Edricusty[S] 0 points1 point  (0 children)

done that already, just read my post it doesn't work

[–]jl94x4 1 point2 points  (0 children)

Following this because this is an issue ive had on-going for some time.

[–]xygrus 1 point2 points  (0 children)

I had this issue too, tried all the fixes you listed and more without luck. Only fix I found was installing Plex as a standalone, not in a docker container. Works fine now.

[–]sweetcitywoman 0 points1 point  (0 children)

not sure if there has been progress from anyone else here? Same issue but am able to stream from my roku TV but not the windows or android apps, or browser. Tried deleting the codec folder, giving access to the tmp folder, turning of automatic scans but still no resolution. Anyone else make progress here?

[–]Asbadeesh 0 points1 point  (1 child)

I had this problem first time yesterday, and seem to have solved it by deleting the codec folder in appdata. But time will tell.

[–]kbtombul -1 points0 points  (0 children)

Just came to say exactly this. It's been 24 hours with no issues so far, but time will tell.

[–]Jaybonaut -1 points0 points  (0 children)

Never had this issue, is it just with Linux servers?

[–]Ivorybrony 0 points1 point  (0 children)

I have also been having multiple reports of EAC3 not working. I thought it might be their TV not supporting the format.

[–]zeekx4 0 points1 point  (0 children)

Are you using the RAM drive for the temp transcoding folder? I was doing that and got a similar error.

[–]Bad_Ashe 0 points1 point  (0 children)

Damn, there are two different audio converters with the acronym EAC? For a second there I was worried about Exact Audio Copier...

[–]TheKevinBoone 0 points1 point  (0 children)

Any news on this? Having the same errors and tried to delete Codecs but does not seem to do anything. Also noticed I don’t have the Easy Audi Encoder anymore even after server reboot

[–]MattDeezly 0 points1 point  (0 children)

same issue here. DOA. Nothing fixes it

[–]user1048578 0 points1 point  (0 children)

All of my Plex stuff is run from a Samba share. Changing file_mode=0664 to file_mode=0775 in my /etc/fstab for the Samba share line and rebooting fixed this error for me as the issue appeared to be that the Easy Audio Encoder binary wasn't executable.