Thank you very much. The 1.13.8 log shows what looks like a deadlock with the first visible sign of the deadlock at 20:45:50. There is also evidence of transient lockouts that occurred before that
To investigate deadlocks we need process dump captured during a deadlock as well as list of connections and the logs
Could you try and capture the evidence from the latest beta. I do see you ran 1.13.9 earlier
If the server access starts to fail but the plexmediaserver process remains running then it could be a deadlock
I will paste here what is required to investigate deadlocks on NAS and Linux systems
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://192.168.1.209: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 192.168.1.209)
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
