Hi,
So This has been an on-going issue for a few months now, but has been happening almost 1x a day now. Attached are my logs. I’m not entirely sure why the issue is occuring. I’m running the latest LinuxServer.io plex image. The same machine was running plex on windows before and it was 100% stable, not a single issue at all. Never needed restarts or anything. Just this docker container seems to be having the issue.
Thanks for the help!
@Blaze9 said:
Hi,So This has been an on-going issue for a few months now, but has been happening almost 1x a day now. Attached are my logs. I’m not entirely sure why the issue is occuring. I’m running the latest LinuxServer.io plex image. The same machine was running plex on windows before and it was 100% stable, not a single issue at all. Never needed restarts or anything. Just this docker container seems to be having the issue.
Thanks for the help!
Thanks for the logs. I can see that requests got stuck at 22:56:25 on 18 June. It could be a deadlock within the Plex Media Server process with threads being locked out due to a deadly embrace between 2 threads. Process dump and connections list would be needed to confirm that. Although the logs do show some entries at the time that have been seen associated with this bug.
The deadlock i am referring to is one investigated here http://forums.plex.tv/discussion/comment/1686321/#Comment_1686321 and that post has links to other forum topics
The diagnostics needed to investigate a deadlocks is as follows
You would need to ensure that Crash Reporting is enabled - see server settings / general / show advanced as well the debug logging. We would be forcing a process dump which results in a crash report generated and would get uploaded on the following restart
On the next deadlock, in a browser get this request to this server (assuming it is on IP 192.168.88.13)
http://192.168.88.13:32400/connections?X-Plex-Token=zzzzzzzzzzzzzzzzz
Substitute the server token for the zzzzzzzzzzzzzzzzzzz .
See this article for how to find the token https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
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 in a ssh session
kill -SEGV <pid>
where <pid> is the PID number for the Plexmediaserver process
The crash report would get uploaded when you restart the server
Wait for few minutes after restart and then get the logs zip and attach here. that will identify the upload information for the process dump
See https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Plex Media Server version 1.13.4.5251 has just been released as beta. It has fixes for two deadlocks - one of which is probably the one observed in the logs provided here
See Release Notice Plex Media Server
