For one it was just database optimization that was taking a long time to complete and you restarted the server whilst it was still optimizing. I have come across database optimizations in the past taking 40 minutes or more to complete
In other logs I see repeated log lines for requests from a WAN IP address - you could try to block that IP address and we then see if it makes a difference.
IP Address 23.123.141.242 - see if you can establish if that is coming from one of the users you shared your server with - first to try is blocking it. And if problems persist, get fresh server logs
There is also this IP Address 173.73.150.194 with similar logged errors - so looked into that as well / block with the other one to see if that resolves the issue
Extracts from one of the logs
Aug 16, 2023 18:34:29.545 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44940: End of file
Aug 16, 2023 18:34:29.581 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44942: End of file
Aug 16, 2023 18:34:29.617 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44944: End of file
Aug 16, 2023 18:34:29.660 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44946: End of file
Aug 16, 2023 18:34:29.698 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44948: End of file
Aug 16, 2023 18:34:29.745 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44950: End of file
Aug 16, 2023 18:34:29.785 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44952: End of file
Aug 16, 2023 18:34:29.832 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44954: End of file
Aug 16, 2023 18:34:29.871 [13404] DEBUG - Request: didn't get any data from [::ffff:23.123.141.242]:44956: End of file
Well, this problem continues to happen and it happens even when the two IP addresses you listed arenât trying to connect.
I couldnât find a way to block incoming IP addresses on the Plex Support pages⊠Could you direct me to where I can find out how to do that â I WILL TRY ANYTHINGâŠ
** updated I found a thread on Reddit **
Here are two more logs from this afternoon - I have around 6 logs saved from the many times that the server has been crashing.
I will have a look at the logs. It is possible there may be some networking issue that is bringing this up. It will be useful to capture the requests coming but that will need some extra settings to allow me to decrypt the tls https dialogue that wireshark captures
I will continue with this via a private message giving you the advanced settings to add to the Plex Media Server in the registry. We would need to have wireshark capturing the network packets - so it would be good if you can get the issue to arise soon after launch of Plex Media Server - as leaving wireshark running for hours could exhaust system resources.
I shut down PMS via the Plex Service Icon, Ran the update from the Plex Updates folder, allowed the update to complete, declined running PMS - as I always do and proceeded to run PMS via the Service â
However, it PMS did nothing. It showed up as running in Task Manager, but that was it.
I then waited a couple of minutes refreshing the PWA I have setup for Plex and still nothing - nothing except my libraries with yellow triangles everywhere.
I then decided to restart my PC and have the Plex service automatically start PMS on bootup.
When started, the PWA still showed yellow triangles everywhere. I waited a good 4 minutes watching the Plex Media Server.exe in Task Manager and there was not CPU% given - like it wasnât doing anything.
I shut down PMS via the Service and when PMS was o longer in Task Manager I re-ran PMS ânormallyâ as a regular app â only then did I see it was doing some kind of database update â which wasnât indicated in the release notes⊠boo!
Anyway, I watched and waited for the database to finish and when it had, Plex was working properly again.
I restarted my Windows PC again so that Plex would automatically run as a service - and it is.