The server became unresponsive after what looks like a possible deadlock - where one thread holds a lock and does not release it and then other threads hang waiting for the lock
The deadlock happened after May 12, 2022 14:34:33
Requests started to queue up after that and when the number gets too high the Plex Media Server starts to give a 503 http response code until you restarted it at 15:00
(apart from that there is also the errors pasted above of the transcoder process failing with out of memory errors - at this point i would treat that as a separate matter - the transcoder failure was when streaming this file B:\Movies\Disney\Homeward Bound II Lost in San Francisco (1996)\Homeward Bound II Lost in San Francisco (1996).mkv
There is no evidence of the Plex Media Server process itself having any memory allocation failures)
Deadlock issues are not easy to investigate but I do have a standard set of diagnostics that should be captured to find out more about it and what may have caused it
See my post here for what diagnostics are needed for a deadlock on Windows
Hello, I added LogMemoryUse as a string value, not a DWord which I have rectified. I have also moved the Plex database to a 4TV SSD.
I have created the Plex Media Server.dmp and zipped it and the file is 85.6 MB in size. I need to know an address to send the link so you can gain access to this file
I have used 7-Zip to split the file into 4 files. you need to unzip each file and extract the uncompressed files to create the original file which is 268 MB.
Hello,
The info I sent you last was a Plex dump of the Plex Media Server.exe however I had already started Plex. This dump was created before I restarted Plex. It is a lot larger than the previous.
I have also added the token info and the server logs.
Again, un-zip all the Plex Media Server files 1 to 8 and then use 7-zip to create the file.
Thank you - I will have a look at the files. I have removed the dump components from your posts as dumps may contain sensitive data - best to use Private Message to send dump files and links to where dump files are - i was expecting the zip of the dmp file to be uploaded to Dropbox or Google drive etc and a link to download it sent to me by private message
I will see where i get to with 7-zip and stitching the files together
thank you for the reply. When I upload the dump file to dropbox or google drive I need an address to send the link. what is the address I can send the link to so you will receive it??
There are several ways to share / give access. You can create a link that anyone receiving the link would be able to view - the link uses random long string and would be unlikely to be guessed or used by others
Plex did crash this time since the Plex Server.exe was not still running and I was unable to create a dump file. The Icon was still in the system tray however and a couple of Plex Transcoder’s were still running. token.txt (7.6 KB) Plex Media Server Logs_2022-05-20_01-47-10.zip (6.9 MB)
Again, The Plex Icon was still visible in the task bar however when moving the mouse over it it disappeared. Plex is not running in Task Manager, there are 6 Plex Transcoder (32 bit) files listed, Plex Update Service (32 bit) and PlexScriptHost (32 bit) Plex Media Server Logs_2022-05-23_01-22-07.zip (7.3 MB) token.txt (709 Bytes)
Thanks - Looked at the logs and the problem was memory allocation failures to do with a library that appears to have over 38,000 items
We are working on changes to Plex Media Server to manage the aggregation of metadata for owned and shared servers better in terms of memory usage - In the meantime, you could split your movies library into several smaller libraries or stop sharing your server with users that have their own Plex Media Servers
Same issue - the server crashed running out of memory - when requests came in for your movies library from PMS servers owned by markdxxxxl and anchorsxxxxxy
Please see my earlier reply
Server is running out of memory because of the issue I described
You have a movies library with 38,460 movies and TV Shows library with 3659 shows
Shared users of your server, those that have their own Plex Media Servers are sending requests to the server that lead to the crashes after memory allocation failures
The fix is being worked on and when it comes out., the version with the fix will need to be installed on all the Plex Media Servers owned by your shared users
Until then
remove access to your server to those users that have their own servers
or
Split your libraries into several much smaller libraries
I have uploaded to files to WeTransfer, see link above.
I previously removed access to the PMS servers for markdxxxxl and anchorsxxxxxy so I don’t have access to their servers however they still have access to Malflix. Are you saying I have to remove access for these users?
If I increase the memory of the server, will this rectify the problem?
Please confirm you could access the files from WeTransfer.
I have downloaded the files - so you can delete them
This looks different from the previous crash - with both high memory usage and some sort of lockout leading to requests queuing up
I see that the dump was taken at 02:27:04 on the 25th, That is good. But the http://127.0.0.1:32400/connections?X-Plex-Token=xxxxxxxxxxxxx request was not made then but was done after the server was restarted i.e. after the problem was resolved by the restart. The server was restarted at 02:29:43 and the /connections request (what you saved into token.txt ) was done at 02:29:49 - did you try this request when the server was locked out at 02:27 ?
I will have a look at the dump next week - in meanwhile could you increase the number of log files from the default - See registry setting LogNumFiles - suggest having it set to 20
Hoping we can get the logs to cover the time when the problem starts and there is build up of requests. For this log files setting, see article Advanced, Hidden Server Settings | Plex Support
See if you can get the connections list when the issue arises next time - at same time (just before) you take the process dumps and also with the larger number of log files - the server would need restarting after making the registry change
Went back to the earlier crash and there was also this user with a server that sent a large request : “Jason Duxxx”
I tried to create a token before starting Plex however this failed since the Plex needs to be running.
You Said:
See if you can get the connections list when the issue arises next time - at same time (just before) you take the process dumps and also with the larger number of log files - the server would need restarting after making the registry change
Do you mean from the above the take the process dump, start Plex, take the token and then the log files. The log files were a lot larger this time.
