Server Version#: 1.43.0.10162 (Unraid; LinuxServer Docker)
Player Version#:
Hello,
Over the last week I started having playback issues with my server. This happens across numerous devices (Web, Android and IOS). Plex UI on all devices is good (no errors, updates with new media in a timely manner, etc.). This seems to be strictly a playback issue.
When I press play I immediately get one of two errors depending on the device:
“Failed to fetch play queue response” or
“An Error Occurred loading items to play.
These errors happen 100% of the time, even after a fresh reboot (hardware and/or docker). This also happens for all media (video, audio and photo) and also PlexAmp.
I think I see the issue in my log (attached), but the error is not providing any context and I can find no tangible mention of it on google or this forum.
DEBUG - [DownloadQueue] Updating status for generator 12382
ERROR - [DownloadQueue] Failed to get status for generator 12382
DEBUG - [Req#100] PlayQueue: Start index: 0 End index: 0 Count: 1
ERROR - Got exception from request handler: std::exception
Things I have tried:
Reboot server
Updated to latest LinuxServer / PMS Version
Confirmed I am not out of space on both Docker image and drives (Docker has 8GB free and config folder (database, logs, Metadata, etc) has 140GB free
Confirmed R/W access on the server config files is still good.
Deleted Codecs folder
Confirmed the media files are not corrupted.
Ran ChuckPa’s DBRepair (Auto Mode) - log said everything was ok
No, I never found a clear solution. I ended up starting with a new Plex install and restoring an old database that I was lucky enough to have and was confident was not broken. I then restored the history from the “broken” Plex database. Thus my new install was like nothing had changed (outside of a few minor settings I had to redo).
I believe the issue was caused by two potential issues: 1) my database corrupted from a Plex update in a way that DBRepair could not see or 2) I had a permissions issue on my Plex Docker that caused things to get messed up. I also started having out of space errors on my transcode directory, even though I clearly had enough space - which leads to me to think I had a permissions issue.
As painful as I thought it would be, it only took my ~30 minutes to get everything back up and running. So if you are having this issue you might want to bite the bullet and reinstall.
Either way, I would quickly identify a prior database that isn’t impacted by the issue and keep it safe while you troubleshoot.
DO NOT USE CHATGPT, editing the database tables directly never ends well. Ill take a look at the server logs above and make further comments then.
EDIT:
Looked at the log file, since its an excerpt I dont have the whole picture, but it looks like you have disabled direct streaming, and have an upload throttle which is forcing everything to transcode, and that is where you are having issues.
Depends on who wrote it. the ONLY scripts I recommend are written by Plex employees. ChuckPa’s tools have proven to be reliable. Plex uses a modified version of sqllite, so unless you are using that version to edit the tables, the risk for database damage is very high just by opening/saving the database. Now factor in either AI or amateur sql commands and the risk is even higher.
Database rollback is a valid option but tends to be the conservative/last option I tend to recommend as it may just be hiding underlying issues vs actually fixing them.
it happened again. So at least at my place it seems to be related due to a change from ls287 to ls288 made two days ago, a container rollback before “fixing” the DB.
As I thought of giving that fancy script a spin, I did it and ran into some issues. Primarily because I have different rights insight the docker container itself. I adapted the script a little and posted it here:
@smiba Please create a new thread with a copy of your server logs and details of the issue. Best to not mix things up between multiple users who may have different issues.
I think we’re all having the same issue, and I’m not sure why after many years of using Plex this has started to show up. My comment was mostly as a way to boost this thread and give a better idea the scope of the issue to the Plex team.
I just had this start for me. I’m running a Synology NAS (21+) and never have had issues. I saw where the reset queue may work. But I’ve never done the code like that. Do I copy it and then paste it to plex somewhere or do I paste it in the synology DSM somewhere? Thanks for any advice.
I just check for logs and this error is popping up.
[Req#64b/Transcode/0901213a-1cf2-47d1-86ac-26e478d35f96/a52e8682-b147-4a72-8ccf-f60dda3e117f] [eac3_eae @ 0x7fd1f8b92b40] EAE timeout! EAE not running, or wrong folder? Could not read ‘/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/tmp/pms-ada3c886-8077-4f04-adc2-789c97ebe9e7/EasyAudioEncoder/Convert to WAV (to 8ch or less)/0901213a-1cf2-47d1-86ac-26e478d35f96_17896-0-179.wav’
Update: I found out my issue was either the codex or I needed to increase my Inotify. I ran the inotify then I stopped plex and deleted the codec folder. Restarted plex and tried again and it worked remotely and locally. Which ever did it, that worked for me. But I still would like to know where I run that script. Maybe a stupidly quick question, but I would love to know. Thank again for any help.
I made an update to my gist as play_queue_generator killed all my playlists. This was a huge issue for me, therefore I played around till it worked fine for me.
