I’ve looked at the articles I could find about this, but my server is NOT through Docker, and this is happening when nothing is playing, so I don’t know why it would be trying to transcode. It takes up about 50% CPU resources just to run this error over and over again.
I have a text file of the logs over the course of a couple minutes, showing that it occurs over and over again. Not sure if it contains sensitive information since I just copied the RAW text, so I can send it to someone if requested. Basically the error repeats:
Nov 15, 2021 11:42:34.001 [0x7f2e069f0b38] Error — [Transcoder] [eac3_eae @ 0x7f9c74e34b00] error reading output
Nov 15, 2021 11:42:34.001 [0x7f2e041a0b38] Error — [Transcoder] Error while decoding stream #0:1: I/O error
Nov 15, 2021 11:42:37.000 [0x7f2e04fcdb38] Error — [Transcoder] [eac3_eae @ 0x7f9c74e34b00] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-085dec92-ff06-4e26-bc5c-fd41cceb950a/EasyAudioEncoder/Convert to WAV (to 8ch or less)/0e3907db-3c62-4862-8dd2-58ec3e22b7a6_220930-0-1657.wav'
Nov 15, 2021 11:42:37.001 [0x7f2e069f0b38] Error — [Transcoder] [eac3_eae @ 0x7f9c74e34b00] error reading output
Nov 15, 2021 11:42:37.001 [0x7f2e041a0b38] Error — [Transcoder] Error while decoding stream #0:1: I/O error
Once again, this happens all day while nothing is playing, either remotely or locally.
What I’ve Tried
I’ve taken a look at the directory ‘/tmp/pms-085dec92-ff06-4e26-bc5c-fd41cceb950a/EasyAudioEncoder/Convert to WAV (to 8ch or less)/’, and I notice that the folders in there change constantly while this is happening. I’ve set the permissions using chown recursively to make sure that the user plex is the owner of the directory.
Restarting the server will stop the process, but it will start again after a few hours.
Possibly relevant info
I have Plex Pass
I’ve noticed this issue occurring for weeks
Scheduled tasks don’t run within their allotted timeframe as specified in the Scheduled Tasks settings, and they always run in the middle of the day (the timezone is set correctly on my server)
Not sure what else I could be missing, so any help would be appreciated.
I have a movies folder with 415 folders inside, each with its movie file and a few with .srt files included. My tv folder has 22 shows, each with its own set of Season subdirectories and their corresponding episodes, most of them being less than 3 seasons’ worth. Some go up to 8 or 9 seasons.
Using the sudo find command from the article you posted, it returned 526 for both the movies and the tv libraries, the only ones connected.
Overall with 415 movies and 22 tv shows, I can’t imagine this would be enough to cripple Plex media server, seeing how people have libraries well into the thousands.
Any new info on this? It’s gotten to the point where this is happening 100% of the time. It’s taking up 50% CPU at all times and working through these transcoding errors, even when nothing is playing, even after a restart.
Monitored, meaning the ones that are chosen in Plex to scan for library contents? I have only two libraries - Movies and TV. In total, there are less than 550 directories within these two folders.
Agreed! I don’t have any audio at all in my libraries. I had an old server that I switched from where I had a single audiobook, but that has been removed and does not exist on my current hard drive.
Open http://127.0.0.1:32400/web (i presume the server is on the same machine you’re typing from. Switch to LAN address if sitting adjacent to you)
It will start to setup a new server - this is desired
SPECIAL NOTE When you get to the point of the server’s friendly name – Give it something obvious, e.g. TEST-SERVER so it doesn’t conflict with the productdion one
Complete setup and get to the dashboard
Now give it a test drive.
The “rename” step above slides your existing server off to the side and keeps it safe
Alright, I followed all the above steps, and it just finished scanning my library. I’m currently not getting EAE transcoding errors, just some XML errors; not sure what they’re about.
This same error chunk has appeared a few times, but the server has only been up for a few minutes so I’m not sure if it’s that important or related to the previous issue.
How long do you recommend I keep this test server up to make sure the EAE error doesn’t appear again?
Note: Plex Media Server is idling between 0.1-1.5% CPU, about what the expected normal usage should be.
I think I’ll try to keep this build of the new server and see if the fresh setup will fix everything. Is the best way to transfer the metadata over to just copy and override the folders from /var/lib/plexmediaserver/Library.keep/Application Support/Plex Media Server/Metadata/[Movies && TV Shows && Collections] to the new server folder?
I do notice that the previous Library.keep has more Metadata folders than the new one:
So if I copy over just Movies, TV Shows, and Collections, will I basically have an identical setup as I did before?
I’m thinking I’ll keep around the Library.keep for now just in case, and maybe delete it in a month or so if everything is still going smoothly. Should I just delete the server itself without worrying about losing anything important?
As far as collections go, I have the library collections turned off and have dozens of custom collections with custom posters for many of the movies. What’s the best way to migrate those, then?
When I upgraded my server a month ago (before these issues), I copied everything from the server data directory as instructed in this article. But since has a fresh new library does that mean it wouldn’t work the same way anymore?
If the error returns, then the database is toasted somewhere that makes no sense.
If there are no EAE errors – then we just confirmed the EAE was damaged somehow
If all is good, and you want to keep what you have (recommended) - Delete the “Test” server (Library.new) and also from Settings - Authorized Devices - Server (dropdown)
If the test fails, I’ll get some help here to get your collections moved
