So with no massive number of extras - is the server still crashing when recommendations/on deck settings reinstated ?
Would like debug server logs of the crash and copy of the database if that is the case
would you be willing to help me as well?
i have the latest pms version on windows 10 and i am getting crashes daily. i call them crashes but perhaps hung up is more appropriate? i think itās happening when 20 people or more on on my plex at night. when i go to check the users on my plex it shows the videos still playing, but they arenāt. it will just show this for several hours until i refresh plex. once i refresh plex it then shows plex canāt connect to the internet and if i try to reload plex from the windows tray it disappears. i have to restart to make it work normal again.
i have 30k movies on my plex and we use to have port exhaustion. i donāt know if that is still a thing. i had not had crashes like this for a while until about a month or two ago. now itās regular.
i am almost to the point of reinstalling windows and plex again. i really rather not, but i will do whatever it takes to make plex stop crashing.
Plex Media Server Databases_2018-07-11_15-15-16.zip (22 Bytes)
Plex Media Server Logs_2021-12-30_08-57-15.zip (5.4 MB)
while trying to download these files my plex just crashed. i donāt know if any of this will help you or not.
Sent you a PM with the requested items.
I have rolled back to the suggested 1.21.0.3711 PMS and have not had any crashing.
However, I just noticed that none of the new TV shows I add are being added during scans. Crud.
Thanks for all the diagnostics
The latest two sets of diagnostics show an issue relating to the āRecently Released Episodesā hub for TV Shows Libraries where if the server is slow in responding, then Plex Web is retrying the request but appears to omit the paging header items (start point and how many to return) ending up with a massive request crashing the server when formulating the response which would be for all episodes in the library)
I have reproduced this on Plex Web 4.66.1
I was unable to repro on 4.69.1 which is in the latest 1.25.4 beta release of PMS
Also it has been seen to aise on Plex for Windows app version 1.39.1 - althought I have not been able to reproduce that
updated to the latest plex media server and crashes all over again. so frustrating.
all i did was do one movie folder scan and then tried to match one of the latest movies. plex would not respond or load anything after.
Plex Media Server Databases_2018-07-11_15-15-16.zip (22 Bytes)
Plex Media Server Logs_2022-01-25_02-32-22.zip (5.1 MB)
im still getting crashing once a day sometimes twiceā¦
Happy to look into the instances of the crashes you are getting
I believe you had deadlocks before as well as some crashes back in December
If the Plex tray icon disappears when you hover on it then it is a crash. If it stays but the server is not accessible then it is a deadlock
For crashes I would like to see debug server logs for period leading up to the crash plus the dump file - either captured by Windows following the regedit outlined here Crash Logs: Plex Media Server | Plex Support or the mini dump produced by Plex Media Server itself - this gets copied to %TEMP% when processed - so we would need to look at the file there - it is a filename with no filename extension
if it is a deadlock - then would need the /connections list and the manually produced process dump and server logs
yeah the icon disappears on the system tray.
where do i find the %TEMP%
To find where %TEMP is - just start a windows command line session within a logged in session with same windows account as that which Plex Media Server.exe runs under and then do this to find the path
echo %TEMP%
I expect it to be pointing to
C:\Users\djkev\AppData\Local\Temp
I have looked at the logs which covered period Jul 12, 2022 17:27 to 22:05
I see that there was a lockup where the server was inaccessible. No evidence of any crashes but some deadlock that led to requests being queued up
This lockout started around 17:40 - soon after the launch of PMS at 17:27
You shutdown PMS and restarted it 20:09 - at that point there were over 1000 queued requests and the Plex Media Server started returning error code 503 to requests - the 503ās started at 18:24
The shutdown and restart at 20:09 happened within 1 second duration which makes me think you must have a script / automated action doing this.
So server was restarted at 20:09 and ran till 20:15 when it appears that you probably rebooted windows and Plex Media Server started again at 20:22
To investigate lockups / deadlocks, there is specific set of diagnostics which includes getting a list of connections through the loopback IP address and also forcing a process dump (previously specified here 503 Service Unavailable - Plex Media Server / Desktops & Laptops - Plex Forum)
I would like to send you a development build of Plex Media Server with a fix for a compiler bug that may lead to such issues and crashes - I expect to have that available sometime next week. That would be best option rather than go through the process of capturing the deadlocks diagnostics.
As mentioned in my earlier post, these logs showed a deadlock/lockout that led to the server becoming inaccessible.
I have sent you a development build 1.28.1.5978-004356b0e which has a fix for a compiler bug that affected windows platforms. Could you run with this version and if you do get a lockout - like that which happened on 12th July between 17:40 and 20:09, please collect the diagnostics outlined here:
Could you send me a link that allows me to download without special access being granted - ie just using anyone with a link but send me the link by private message
Are the diagnostics when using the development build ?
Please Media Server 1.28.2 has just been released as a beta release
It has a fix for a deadlocks issue that was identified last week
- Server could hang in certain circumstances (#13758)
Last beta version seem to have issue when refreshing libraryā¦ the server crashedā¦ the last stable version dont have this issue.
Thanks for the feedback - could be something specific to your database. I canāt do anything about it without debug server logs captured after the crash to start an investigation.
Send you log files today, sorry for the delay, no issue with the version Version 1.28.0.5999
but issue appears with newer version
Try to repair the database but found no issueā¦ my database seem to be ok when i run the how-to
thanks!
I cannot find any recent messages from you for this
Is the server still crashing ? Please send me fresh debug server logs
Thanks
