I’m also having this issue. Just happened this morning as a matter of fact. Yesterday 10 people were watching, I was monitoring the CPU and it barely went over 20 percent. Still, randomly without warning I got a “lost connection to the server” message. The server itself was still running but essentially all of the processes had crashed. I was forced to restart the system since I couldn’t kill the sever or transcoder from task manager for some reason. Not sure why it’s been happening recently. Also get random playback errors ever since moving metadata directory to external HD. Error usually would say “Couldn’t retrieve the play queue for this item. Please try again”. Eventually plays after trying different other shows and coming back to that one. I obviously don’t want my users having to deal with that. If someone is able to help with this I would greatly appreciate it.
Hey @ChuckPa, so sorry to hear the amount of grief that release had caused you - I think you mentioned or one of your team members mentioned the lack of communication on the major changes to the database structure before rolling out. Not fun when that happens but definitely a part of the process at times as we are all human - usually we just hope it doesn’t result in something like this. Hope you are getting some time to recover and rest for the long weekend!
I have to say I am stable now (on v. 1.22.2.4274), but I was hoping if you could when the dust settles - please take a look at my logs as I do experience other issues I would love some insight on (again if you don’t mind).
Basically, what happens is (often) my TV Shows library gets stuck in a loop of scanning for say 5 seconds / stop scanning for say 1/10th of a second (it won’t actually say it is scanning any shows when I click on the Activity button on the top right of the NavBar) - just says “Scanning TV Shows” then stops for a tenth of a second and starts back up. This has happened for around a year through many different Server versions.
While this is happening, on my clients I notice when I go to a movie, or a show or anything - aside from the name of the show, episode or movie, all metadata will briefly disappear and change the focus (if I was previously focused on say the actors) back to the media control buttons.
On the server side, if I try cancelling the scan just from clicking on the kebab menu icon next to the library - it will stay stuck in the loop. If I click on Settings in the NavBar, then click on Libraries (under MANAGE) then click on the CANCEL SCAN button (next to ADD LIBRARY), it will break the loop for some time. Or I can right click on the Plex icon in the System Tray and click on Cancel library Update - this will also break the loop.
Under SETTINGS then Library, I have the following options configured Scan my library automatically (TRUE) & Run a partial scan when changes are detected (TRUE). When the server is stuck in this scanning loop, nothing is being added or removed from that library.
If you would like me to submit a new ticket or topic (or if there is an existing forum topic on this subject), please let me know! Otherwise, if there is any more information or logs I can provide you to be at your service, let me know.
Thank you so much either way in advance!
EDIT: Added version I am running now (and STABLE 
) PMS v. 1.22.2.4274
And thank you so much to the entire Plex team that helped get the fix out!!!
Please create a fresh thread.
In that thread,
- Verify you have DEBUG logging enabled, VERBOSE disabled
- Recreate / capture what’s happening
- Download the logs
- Attach them
- Ping me
Well I updated to the latest beta 4276 last night, it was working at the time I updated (I think) but after it went into the “unavailable” state again. I decided to just leave it and go to bed, hope it hashes something out overnight, but it was the same in the morning.
I force closed the server process and then started it again, and it came back up again. Hopefully it’ll stay that way now with this release? I turned in debug logging while I could still get to the web ui… maybe there will be some other clue in the logs now if it dies again.
Just FYI - I am stable as far as this topic issue goes on v. 1.22.2.4274. I am staying on this version for a bit.
Maybe try rolling back to 1.22.2.4274 @BinaryJay? I took @ChuckPa’s advice to stay put on that version to give him some rest 
May i suggest keeping version numbers correct ?
(It’s confusing enough with all the stuff of yesterday 
)
Public = 1.22.1.4275
Beta = 1.22.2.4276
I upgraded last night before bed and the server is unresponsive again this morning.
I’ll try downgrading after work.
Same thing again. Went to bed, unresponsive in morning. Created a new topic with my logs, this time I had debug level logs enabled.
Update : Thought my issue was fixed, got 4 days uptime. Now I’m crashing every 8-16 hours again with no logs. Plex just stops running, I log into the server and the tray icon is there but when I put my mouse over it it disappears. Will hang around for another update but if not fixed I’m definitely bailing on plex and trying an alternative. It’s useless if it crashes more than once a year.
Is this the issue I’m experiencing? How do I fix a deadlock?
Hi everyone, I wanted to give a quick update. I resolved my issue. It took some time, but I think my database was very confused, and probably destroyed after going forward and backwards so many times.
4163 was always the most stable prior to all the recent releases. No matter what version I went to, even 4276, I had issues, and it kept crashing after a few hours. To resolve this, I completely removed Plex from my Windows server, rebooted. I then restored a database from 2/8 (almost 2 months old), and installed 4163. I rebooted, and everything was running smoothly. I waited until Plex updated all the libraries and went through updating the DB, etc. Then, I upgraded to the latest beta release. From that moment forward, I haven’t had issues. Keep in mind, I had previously updated to the latest beta release, and still had issues using my most recently-abused database. To give you an idea as to why I think my DB was hosed, I’ll elaborate. I updated/downgraded at LEAST 10 times over the past 2 weeks. As we know, this was through the major hub update, so I realized that DB was on its last leg after going through that many changes. I also would refresh Plex sometimes, even on the stable 4163 version, and the page would not exist, or some strange error would happen. Refresh again, and it worked. Very, very strange behavior. Once I restored a backup database from 2/8, installed 4163, then updated STRAIGHT to 4276 without applying any other updates, it seems to be running smoothly. After about 24 hours, it did crash… but that was 2 days ago and seems to be fine up until this point. I will keep everyone updated if things change, but I really think my DB was very confused.
Needless to say, DB backups are very important. If you don’t have them enabled, I strongly advise to check that box. It’s saved my ass numerous times since I first configured Plex in 2016.
There’s a strong chance that the DB just didn’t remove some things when I downgraded, and caused issues, and it carried over through the updates. I’m not a DB guru, but that’s my assumption.
This is still occuring on a daily, hourly basis
Glad your issues fixed. I’m still getting crashes, no idea what to do next. Here’s my latest log files Plex Media Server Logs_2021-04-06_17-03-14.zip (4.2 MB)
Can I get some help on what to do next? I pay for Plex Pass and I can’t find any other way to contact Plex.
You know we are all f@*&ed when the support guy spends all his time hassling you about the log files - as if they can’t see anything on their own in-house systems. Because if Plex cant understand how big of a failure this server issue is and can only look at it from submitted log files then they are never going to understand what they have f@@£ed up in their own design. Plex has been a failure for years - and they are just burying themselves deeper and deeper in something they cant get out of. Instead of trying all the new fancy tricks they should focus on developing a simple media server that plays our content reliably. Thats all we ever wanted at the start. Now they can’t even do that anymore.
Take the complaints to reddit, if you’re not adding anything to the conversation there’s no point voicing it here.
Im adding this conversation. I have the same issues all the other on this thread are having. Clearly there’s no point being nice and polite to Plex as they treat us like we are their colleagues rather than paying customers. Going round in circles on logs has not got anyone a solution from what I’ve seen. So I wouldn’t bother sending mine in either. So what I’m asking for is a solution from Plex - not mindless back and forth about logs with zero answers or explanations from Plex. And this is multiplied across many threads on the same issue this last month (or longer). Maybe you just like talking about logs every day - but I just want Plex to explain their mistake and tell us when its fixed. Which is what this forum is meant to be for!
I’m jumping in on this! I thought it was just a me issue. Logs attachedPlex Media Server Logs_2021-04-06_07-48-20.zip (4.1 MB)
Can someone point me to a repository of old builds?? I’m truly sick of this and need to go back to something that worked. I get that Plex is a small outfit, but it’s still $5/month that I’m paying for a service that isn’t really working.
I don’t know if I’ve just been lucky but I have been up for I think three days straight now on [1.22.2.4276] and just updated to [ 1.22.2.4282] and it came up again without complaint. Prior to the last few days it had been dying every single night while I slept.
One thing that I did do was go back to a recent db backup from a week or so before I had all of the issues and then rescan all the differences again… might be worth it if you haven’t tried.
