I can’t for the life of me figure out why my plex server keeps getting unresponsive at certain intervals. I haven’t been able to figure out why by looking at the logs, but maybe one with better knowledge can give it a go? It happened just around the time that I downloaded the logs. Also I’m not getting any crash reports, as the server is still running, but I just can’t connect to it.
Thanks in advance!
@thomasjensen1194 said:
I can’t for the life of me figure out why my plex server keeps getting unresponsive at certain intervals. I haven’t been able to figure out why by looking at the logs, but maybe one with better knowledge can give it a go? It happened just around the time that I downloaded the logs. Also I’m not getting any crash reports, as the server is still running, but I just can’t connect to it.
Thanks in advance!
you have disabled debug logging
Please enable debug logging - see https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
Then restart the server
and on next hang please note down the time and establish if it is permanent hang or transient - and then get the logs zip and indication for when the server was unresponsive and if permanent or for a short period of time
Hi again.
It has been very hard to pinpoint the exact time the server stops responding, as the server doesn’t crash but just hangs. I just can’t connect to it sometimes. But I’m pretty sure with these logs I managed to get, that the hang happened between 15 and 16 on June 16th.
Let me know if that’s not enough detail, I’m very sorry I can’t get any closer, as I just don’t know when it really happens. I only realise when I try to connect again. It’s understandable if you can’t use that for anything, but let me know if you need me to to something different.
Thanks in advance
Also I forgot to add that it’s a permanent hang for all users.
@thomasjensen1194 said:
Hi again.It has been very hard to pinpoint the exact time the server stops responding, as the server doesn’t crash but just hangs. I just can’t connect to it sometimes. But I’m pretty sure with these logs I managed to get, that the hang happened between 15 and 16 on June 16th.
Let me know if that’s not enough detail, I’m very sorry I can’t get any closer, as I just don’t know when it really happens. I only realise when I try to connect again. It’s understandable if you can’t use that for anything, but let me know if you need me to to something different.
Thanks in advance
@thomasjensen1194 said:
Also I forgot to add that it’s a permanent hang for all users.
Thanks for the logs
I can see the last request processed by the server was at 11:47:02 am on Jun 16, 2018. So the server was probably locked out from then up to time of logs being captured at 16:46
It looks like a deadlock and it could be the same issue as one that is currently being fixed. To establish if it is the same and the cause, i would need a process dump at the time of deadlock and also a list of the /connections
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
The following are the steps for getting diagnostics for a deadlock
It would need shell access to the Linux environment on the NAS.
On the next deadlock, in a browser get this request to this server (assuming it is on IP 192.168.1.150)
https://192-168-1-150.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:32400/connections?X-Plex-Token=zzzzzzzzzzzzzzzzz
Substitute the server token for the zzzzzzzzzzzzzzzzzzz and the server plex.direct secure connections identifier for the xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
See this article for how to find the token - the secure connections identifier will also be visible on the screen - so you can find both values
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/
1 Like
@sa2000 said:
@thomasjensen1194 said:
Hi again.It has been very hard to pinpoint the exact time the server stops responding, as the server doesn’t crash but just hangs. I just can’t connect to it sometimes. But I’m pretty sure with these logs I managed to get, that the hang happened between 15 and 16 on June 16th.
Let me know if that’s not enough detail, I’m very sorry I can’t get any closer, as I just don’t know when it really happens. I only realise when I try to connect again. It’s understandable if you can’t use that for anything, but let me know if you need me to to something different.
Thanks in advance
@thomasjensen1194 said:
Also I forgot to add that it’s a permanent hang for all users.Thanks for the logs
I can see the last request processed by the server was at 11:47:02 am on Jun 16, 2018. So the server was probably locked out from then up to time of logs being captured at 16:46
It looks like a deadlock and it could be the same issue as one that is currently being fixed. To establish if it is the same and the cause, i would need a process dump at the time of deadlock and also a list of the
/connectionsYou 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
The following are the steps for getting diagnostics for a deadlock
It would need shell access to the Linux environment on the NAS.
On the next deadlock, in a browser get this request to this server (assuming it is on IP 192.168.1.150)
https://192-168-1-150.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:32400/connections?X-Plex-Token=zzzzzzzzzzzzzzzzzSubstitute the server token for the zzzzzzzzzzzzzzzzzzz and the server plex.direct secure connections identifier for the xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
See this article for how to find the token - the secure connections identifier will also be visible on the screen - so you can find both values
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 processThe 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/
Hi,
I’m having the same issue as well, with exactly the same description. Next time I run into this I can reply to my own thread if you have a chance to take a look there as well. I literally just restarted from a hang, but I’ll check.
One clue I might have is that I VPN into my work network quite often. Sometimes if I’m watching something on plex I’ll connect to my work network. This obviously causes my IP to change and the buffered video will continue to play but as soon as the buffer is done, it’ll go into the “loading” swirl and stop loading. Upon then PMS is unresponsive until I restart it. But this is just me, no one else does this and the server still crashes constantly for me.
Thanks!
@Blaze9 said:
@sa2000 said:
@thomasjensen1194 said:
Hi again.It has been very hard to pinpoint the exact time the server stops responding, as the server doesn’t crash but just hangs. I just can’t connect to it sometimes. But I’m pretty sure with these logs I managed to get, that the hang happened between 15 and 16 on June 16th.
Let me know if that’s not enough detail, I’m very sorry I can’t get any closer, as I just don’t know when it really happens. I only realise when I try to connect again. It’s understandable if you can’t use that for anything, but let me know if you need me to to something different.
Thanks in advance
@thomasjensen1194 said:
Also I forgot to add that it’s a permanent hang for all users.Thanks for the logs
I can see the last request processed by the server was at 11:47:02 am on Jun 16, 2018. So the server was probably locked out from then up to time of logs being captured at 16:46
It looks like a deadlock and it could be the same issue as one that is currently being fixed. To establish if it is the same and the cause, i would need a process dump at the time of deadlock and also a list of the
/connectionsYou 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
The following are the steps for getting diagnostics for a deadlock
It would need shell access to the Linux environment on the NAS.
On the next deadlock, in a browser get this request to this server (assuming it is on IP 192.168.1.150)
https://192-168-1-150.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:32400/connections?X-Plex-Token=zzzzzzzzzzzzzzzzzSubstitute the server token for the zzzzzzzzzzzzzzzzzzz and the server plex.direct secure connections identifier for the xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
See this article for how to find the token - the secure connections identifier will also be visible on the screen - so you can find both values
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 processThe 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/Hi,
I’m having the same issue as well, with exactly the same description. Next time I run into this I can reply to my own thread if you have a chance to take a look there as well. I literally just restarted from a hang, but I’ll check.
One clue I might have is that I VPN into my work network quite often. Sometimes if I’m watching something on plex I’ll connect to my work network. This obviously causes my IP to change and the buffered video will continue to play but as soon as the buffer is done, it’ll go into the “loading” swirl and stop loading. Upon then PMS is unresponsive until I restart it. But this is just me, no one else does this and the server still crashes constantly for me.
Thanks!
Thanks for the info. Have been looking at your logs. These may well be the same issue that is currently being fixed - see http://forums.plex.tv/discussion/comment/1686321/#Comment_1686321
I will respond to your forum topic http://forums.plex.tv/discussion/324616/pms-constantly-crashes-unreachable-unless-restarting-container-both-via-plex-tv-and-localhost
I haven’t encountered a deadlock since you asked for the crash logs, but I’ll keep monitoring the server. So far it seems to have been fixed by recent updates, but I’ll keep checking. Thanks!
Alright the deadlock happened again.
I’ve sent you the connection list in a private message, and attached the logs to this message. I hope it helps, and I hope you can find the uploaded crash logs.
Plex Media Server Logs_2018-06-27_00-06-43.zip (2.6 MB)
Thanks for the logs and the crash report and connections list.
I do have a development build that i have made available to a few users with what appears to be similar lockout. Unfortunately I do not have a docker image to make available to you to try. Assuming we get good feedback from the users that received this build, I anticipate that the deadlock fixes will be included in the 1.13.4 beta.
That sounds perfect. Thank you so much for your help. I’ll let you know when the beta rolls around, if it fixes my issue.
I have had this type of problem for well over a year and I don’t know how many plex updates. Mine wont go 7 days without hanging up. when my apple tv cant find my server, I go upstairs to my server and stop and start plex and its fine. I am running iTunes on the machine too and most times I can just go over to that app on my apple tv and watch what I was planning to watch but iTunes changed their format where its difficult for me to find anything as I have too many M4V files. I am running a dell T110 server with Windows 7 pro and x3430 quad core processor with 10gb of ram running OS on a 256gb SSD and all my data on 4 5tb hard drives in raid 5 on server. I think next revision of Plex under scheduled tasks is option to shut down and restart all the plex service either every day before or after backups and see if I can keep this thing running as I hate having to run up the stairs and restart the thing when it decides not to talk to anything.
Plex Media Server version 1.13.4.5251 has just been released as beta. It has fixes for two deadlocks following investigations from diagnostics provided in this forum thread
See Release Notice Plex Media Server
- (Playback) Rare deadlock with stopping sessions (#8659)
- (Streaming Brain) Rare deadlock involving bandwidth limits (#8498)
1 Like
