Yes the logs do confirm a deadlock issue
I have added you to the message thread that has a download link for 1.28.1 alpha build
thanksā¦ ill install it and keep you posted
cheers
I tried the 64-bit install and experienced the exact same issue as with the 32-bit install. What info do I need to provide to try this alpha release and is that even possible not that I have installed the 64-bit version?
upload your log files so sa2000 can confirm you are having this deadlock issue
Thereās dozens of logs filesā¦ Which files specifically and how soon after the crash? Do I need to have verbose logging turned off? If so, Iāll have to turn that off and wait for another crash.
Also, I keep losing posting privileges until I delete all browsing history. Thatās been happening about as long as this ādeadlockā issue. Iām not sure if the two are related or not.
verbose is not needed.
make sure that Enable Plex Media Server debug logging is ticked
go to manage ā troubleshooting and click on download logs
once downloaded, upload the zip file here and sa2000 can check it
1 Like
Logs attached with debug logging enabled. This is the 64-bit install with the same issue as the 32-bit install.
Plex Media Server Logs_2022-07-28_07-18-42.zip (3.3 MB)
Hi @sa2000 can you add me please, in want to try 1.28.1 thanks
They said you can go back to 32 bit, but be sure to uninstall 64 bit before doing so. From my understanding, never install 32 bit directly over a 64 bit version. Just be sure to uninstall is all.
Most recently on 7/27 at 19:58 and 22:33
Attachment deleted
I too have been experiencing the deadlock issue and found this thread. I installed the 64 bit version late last night and it has not crashed (really stalled) again yet, so my logs are probably clean.
I also had issues with not all libraries showing up on restart. Sometimes a couple would be missing, sometimes they would be there. Anyone else experience this or could it be something else unrelated? Started happening at the same time after years of not having issues along these lines.
1 Like
Iāve been running Plex for at least 3 years without issue and my Plex Media Server has been on 24/7 since then. I have never made any drastic changes to my PMS and definitely not made any config change at all in the past few weeks that might have cause a sudden unexplained and repeated/persistent deadlocks out of the blue!
I have been experiencing a sudden onset of deadlocks on my PMS since yesterday. It happened twice within a day and I had to restart my PMS service. I did a reboot on my server after the two deadlocks and am monitoring the situtation.
It has not deadlocked yet but streaming is still unstable as playbacks may suddenly freeze as the server becomes unresponsive. Sometimes it might self recover, other times it enters into a deadlock and while the PMS tray icon is still running, there is no response from any client and Plex Dash app was also not able to read any data or stats from the server (i.e. completely unresponsive).
I truly believe that Plex had caused this very widespread issued (also mentioned very widely on Reddit recently) after the most recent update to PMS. PLEASE FIT IT! Iām a Plex pass user and donāt believe we deserve this!
Nobody deserves it or expects it (c.f. the Spanish Inquisition as well). Thankfully we know why this is happening and it appears thereās already an alpha which resolves the issue.
4 Likes
I would need to see debug server logs to confirm the issue - could you do that
Thanks for the workaround 
But i did some testing and rolled back to 1.25.8.5663
Havnt had a crash since, and its been over 1 week now.
Thanks for the logs. Looks different issue. The database optimization hung for some reason. Could you at some point shut down Plex Media Server and copy out the db files - there may be 1 or 3 files - all in this path
C:\Users\Dave\AppData\Local\Plex Media Server\Plug-in Support\Databases\
File name
com.plexapp.plugins.library.db
and may also be these
com.plexapp.plugins.library.db-wal
com.plexapp.plugins.library.db-shm
Please copy out the files and zip and upload on dropbox/google drive etc and send me a link by private message - will try to optimize it and see if it hangs for me. May need some more diagnostics after this
Thanks
Could you also have a look at the Windows Event Log through Event Viewer and open up the System Event Log and see if there were any disc related events after 02:00 am on the 28th July
Is the C: Drive an HDD / SSD ?
The last database related log entries before you restarted the server at 06:24 am were
Jul 28, 2022 02:02:04.778 [34928] DEBUG - [Database optimization/com.plexapp.plugins.library.db] Activity: updated activity 9d053879-f05f-4a7c-a634-a283cbfb96b4 - completed 40.0% - Optimizing database
Jul 28, 2022 02:02:08.170 [34928] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (E:\jenkins\server\321523030\Library\FullTextSearch.cpp:58): 3.328125 seconds
Jul 28, 2022 02:02:10.248 [34928] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (E:\jenkins\server\321523030\Library\FullTextSearch.cpp:71): 1.734375 seconds
Jul 28, 2022 02:02:15.028 [34928] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (E:\jenkins\server\321523030\Library\FullTextSearch.cpp:81): 5.281250 seconds
Jul 28, 2022 02:02:20.002 [34928] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (E:\jenkins\server\321523030\Library\FullTextSearch.cpp:94): 4.718750 seconds
Jul 28, 2022 02:02:20.108 [34928] DEBUG - [Database optimization/com.plexapp.plugins.library.db] Database optimization: starting.
I am sorry the logs do not go back that far
The period covered by the logs was
Jul 28th 02:53 am to 09:57 am
You would need to capture the logs soon after the issue arises - do it on restart following a hang. At this point I only need logs to confirm if a deadlock was encountered on version pre 1.28.1 so I can include you in the alpha release trial
@sa2000 - Have you see my logs ?
I will PM you the link to the db files. I have three db files with different dates but I do not have db-wal or db-shm files.
The C: drive is solid state NVMe. I also have a D: drive which is a standard SSD. I have an E: drive but itās a mapped drive that has nothing to do with Plex at all.
I do not see anything in the Event Viewer related to disc drives. Thereās only this entry several times after 2AM:
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
Turns out I have the issue here aswell. I have 2 Servers setup in different homes, one we kept losing every few hours so have moved over to a Mac.
The other done it for the first time yesterday. Have just set the debug logging to off? I believe thats the request to use for providing logs in the future.
Spotted this in the BETA update today, talking about the same scenario perhaps?
**(Windows) The server could crash due to incorrect behavior in Microsoftās linker (#13588)
