ERROR - [Transcoder] [ac3_eae @ 0x2fd4f40] EAE timeout! EAE not running, or wrong folder ....

Plex Media Server NAS & Devices
41

Same error after 2 days.

42

Same here @lightrush. Iā€™ve tried all the recommend fixes but after a few days the transcoder dies and I have to either restart or kill the Plex EAE Service.

43

I dont mean to interrupt but do have a question about

  -v /mnt/data:/data \

Is that a full network mount which has the transcoder temp on a network device?

If so, you must have POSIX file locking on the mount. Without it, the EAE codec will fail every time. It requires it.

1 Like
44

My data is on an ext4 volume mounted via USB.

45

Thanks. I only mentioned because there has been a recent increase in those, new to Linux, storing their Library directory out on NFS without POSIX locking. The same EAE symptom manifests for them.

46

Is it confirmed that when running in docker, this is caused by EAE using /tmp inside it?

47

Soooā€¦ I tracked this thread down after having similar issues pop up and the tip regarding EasyAudioEncoder having the wrong permissions got me headed down the right track.

Iā€™m going to say this probably stems from trying to migrate a server rather than starting from scratch. Just like you guys, that encoder file was the wrong permissions. And who knows what else suffers the same fate. Rather than piece-meal attempting to fix, I went ahead and started with a fresh docker and no migration and wouldnā€™t you know itā€¦ transcoding works fine now (and that encoder executable has the correct permissions).

I think Plex has to - if anything - work on the docs regarding server migration and/or database backup/restore because I followed them precisely and this result is actually expected, in hindsight.

48

This worked perfectly for me too.

49

Iā€™m going to say yes as mounting /tmp outside of docker resolves the issue for me. I checked my EasyAudioEncoder and it was rwxr-xr-x with dockeruser<1001> as the user and group (this is also the PID and GID I pass to my docker containers). I want to try mounting it as a volume, - plextmp:/tmp, instead since the data is temporary I donā€™t feel the need to really have it be an actual folder. Iā€™m testing this now but below is what I use in Docker Compose and everything works.

Snip from my docker-compose

[...]
  plex:
    container_name: plex
    environment:
      - PLEX_UID=1001
      - PLEX_GID=1001
      - TZ=America/New_York
    image: plexinc/pms-docker
    network_mode: host
    restart: always
    volumes:
      - /mnt/docker-data/plex:/config
      - /mnt/media/TV:/data/TV
      - /mnt/media/Movies:/data/Movies
      - /mnt/media/transcode:/transcode
      - /mnt/media/tmp:/tmp
[...]
50

Hey everyone.

Iā€™ve tried all the fixes above and none are working for me so far, except mounting /tmp outside the docker container but Iā€™m not sure if thatā€™s a good permanent fix. Iā€™ve been on the official docker image and then switched it out for the linuxserver one, which didnā€™t help. Iā€™ve tried changing the permissions without success. Iā€™ve also increased the max watches and it didnā€™t work.

As @aR3SA4Ry pointed out, I too have migrated the config before, so that could definitely be related.

Currently Iā€™m back on the official image, with /tmp mounted to the transcode directory. Iā€™d really like to avoid starting over with my database as I would lose my ratings and other metadata.

51

The only thing that worked for me was to change the owner and group of the /tmp dir in the container to ā€œplexā€ This isnā€™t ideal as Iā€™d have to do it every time the container restarts.

52

i am having same issue on sysnology tried all the fixes and cant get it to work still getting same error message
Sep 10, 2018 13:41:03.009 [0x7f6ac0bff700] VERBOSE - It took 0.0 sec to serialize a list with 0 elements.
Sep 10, 2018 13:41:03.009 [0x7f6ad1bff700] DEBUG - Completed: [127.0.0.1:38383] 206 PUT /video/:/transcode/session/c27e953c90df8500-com-plexapp-android/67ba3081-2603-4241-b2eb-6a03fa5a77a8/progress?progress=-107561189662.6&size=-22&remaining=-1&speed=0.0 (11 live) 1ms 326 bytes (range: bytes=0-)
Sep 10, 2018 13:41:03.327 [0x7f6ad1911700] VERBOSE - WebSocket: processed 1 frame(s)
Sep 10, 2018 13:41:06.001 [0x7f6ac9623700] ERROR - [Transcoder] [truehd_eae @ 0x23e5d80] EAE timeout! EAE not running, or wrong folder? Could not read ā€˜/volume1/Plex/tmp_transcoding/pms-3b0b709d-b49a-4f24-9bcd-9cf42c12ade8/EasyAudioEncoder/Convert to WAV (to 8ch or less)/c27e953c90df8500-com-plexapp-android_30021-0-8.wavā€™
Sep 10, 2018 13:41:06.003 [0x7f6ac7bff700] ERROR - [Transcoder] [truehd_eae @ 0x23e5d80] error reading output
Sep 10, 2018 13:41:06.005 [0x7f6acf317700] ERROR - [Transcoder] Error while decoding stream #0:1: Input/output error
Sep 10, 2018 13:41:06.006 [0x7f6ad1911700] VERBOSE - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Sep 10, 2018 13:41:06.006 [0x7f6ad1911700] VERBOSE - Auth: Came in with the master token, authorization succeeded.

anybody got any other ideas

53

I had this same issues mentioned in this thread but on an Ubuntu install within a VM rather than the docker install like most are mentioning here. It seems all threads linked to this one.

I first increased the watched directories, made no impact
I then deleted the codecs folder which made plex re-initialize it all, this fixed my issue

54

watari

So instead of just deleting the EasyAudioEncoder you also deleted the whole Codec folder?
I just want to be sureā€¦since just removing the EasyAudio doesnt fix the issueā€¦ it always come back!

Thanks

55

Tried mapping tmp out of the container. Tried pretty much everything here; only deleting EasyAudio did the trick. I suspect it will comeback next time Plex upgrades. Iā€™m not sure what consequences of not having EasyAudio are but now I can stream to web, ATV and IOS so it make me happy for now :slight_smile:

1 Like
56

This also worked for me with Unraid 6. Thanks for posting the solution that also worked for me!! ::smile:

57

Getting same error on debian with official docker image.

Tried restarting docker, deleting codecs folder, recreating image and configs from scratch (as original was migrated from other server). All of solutions solves it just for a dayā€¦ next day I get same errorsā€¦

Any ideas why this happens?
I donā€™t get any ā€œFailed to add watch for ā€¦ā€ in logs.

58

Fantastic Catch!!!
That solved it for me!
Tanks!

59

Deleting EasyAudioEncoder, killing it (kill -9) and restarting the stream worked! Thanks! EasyAudioEncoder reappeared and it seems to work nowā€¦

60

Had the same issue today on the official docker image (latest).

Tried without success:

  • mapping /tmp and /transcode outside the container
  • deleting EasyAudioEncoder
  • chmod EasyAudioEncoder

In the end what worked for me was to delete the /tmp/pms-892a70a0-35d3-47d7-b5ea-133e13ca9622 folder completely.

Letā€™s see how long this will work outā€¦