I have looked into the logs to see why the server needed to be restarted. For any issue with the Plex App for the Sony - this would need to be looked into separately with logging from the app as well as the server log
The server appears to have locked up at around 17:16:02 on September 9th. I can see that an internal request from the system.bundle process failed to get seen by the Plex Media Server process. This will need to be investigated as a deadlock with specific diagnostics which includes a process dump as well as list of connections as well as the logs.
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, do the following
in a browser get this request to this server
http://192.168.178.30: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.178.30)
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