I have looked at the logs and i can see what looks like a deadlock before one of your shutdowns - the shutdown at 16:31:49. Deadlocked just before 16:26:40.662 .
I would advise following the guidelines for capturing diagnostics for deadlocks - I have several forum posts on the subject. This is one Server Crashing (reproduceable)
For deadlocks, need list of connections, a process dump and debug logs - see below
Diagnostics for Deadlocks on NAS/Linux
- Ensure debug logging remains enabled. (Settings / Server / General / Show Advanced)
- Ensure crash reporting is enabled. (Settings / Server / General / Show Advanced)
When you get the lockout (and please wait at least 5 minutes trying to access the server, before deciding there is a deadlock), do the following
in a browser get this request to this server
http://10.10.10.11:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxxxx
Substitute the server token for the xxxxxxxxxxxxxxxxxxx
See this article for how to find the token
https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
(This assumes your server remains on IP address 10.10.10.11)
Copy the response to a text file and send it to me by private message referencing this forum topic
Then get a process dump through the command line in Linux
kill -SEGV <pid>
where <pid> is the PID number for the plexmediaserver process
The crash report should get uploaded when you restart the server
Wait for few minutes and then get the logs zip and attach here. The crash uploader logs would give the information I need to locate the dump. The other logs would be needed for the investigation of the deadlock
(I did notice that one of your shutdowns was only 17 seconds after a successful request that completed ok. For deadlocks, it is important that you wait longer than that - at least 5 minutes - before deciding tit could be a deadlock
