This discussion was created from comments split from: PMS 1.9.5.4339-46276db8d Unresponsive, have to close and restart PMS..
Also on 1.9.5, I dont have the exact same issue but have had a number of crashes since moving to this version. Not sure if its related to your issue or if its something else entirely (or an issue with my server), but I figured I would piggyback here instead of making a whole new thread.
I am attaching some logs taken after I restarted my plex server this morning.
@mashuto said:
Also on 1.9.5, I dont have the exact same issue but have had a number of crashes since moving to this version. Not sure if its related to your issue or if its something else entirely (or an issue with my server), but I figured I would piggyback here instead of making a whole new thread.I am attaching some logs taken after I restarted my plex server this morning.
Thanks for the logs
I have not been able to find any crash reports for the time when you restarted the server.
Logs show that you restarted at 10:16:15 am on Oct 19, 2017
The log file before that goes up to 10:00:00 - so presumably a hang at that time?
There is no evidence of a any crash report being generated for this
There is also no evidence of a deadlock after 10:00:00
The last activity was the completion of a DVR recording of Flipping Out - E1 - What Will Jeff Do?' at 10:00:00
Do you recall if the Plex icon was still showing in the system tray when you restarted at 10:16?
If it is a hang, then would need a process dump to go with the logs
There is evidence of a crash at 17:49 on 19th October and one at 22:58 on 18th October
I do not have logs for these - one of them (the 17:49 crash) is currently under investigation and is to do with switching between hardware and software transcoding. This specific crash can be avoided in the interim by disabling hardware transcoding
The crash at 22:58 on 18th October, I would need to see logs for it (if it repeats itself)
And if you do get a hang as opposed to a crash - (check windows task manager to see if Plex Media Server.exe is still running), then would need process dump as well as logs
If it is a crash and Plex Media Server.exe does not show in windows task manager, then look for a dmp file within
C:\Users\admin\AppData\Local\Plex Media Server\Crash Reports\1.9.5.4339-46276db8d\PLEX MEDIA SERVER before you restart the server and copy the file out - in case there is an issue with uploading it
@sa2000 said:
@mashuto said:
Also on 1.9.5, I dont have the exact same issue but have had a number of crashes since moving to this version. Not sure if its related to your issue or if its something else entirely (or an issue with my server), but I figured I would piggyback here instead of making a whole new thread.I am attaching some logs taken after I restarted my plex server this morning.
Thanks for the logs
I have not been able to find any crash reports for the time when you restarted the server.
Logs show that you restarted at 10:16:15 am on Oct 19, 2017
The log file before that goes up to 10:00:00 - so presumably a hang at that time?
There is no evidence of a any crash report being generated for this
There is also no evidence of a deadlock after 10:00:00
The last activity was the completion of a DVR recording ofFlipping Out - E1 - What Will Jeff Do?'at 10:00:00Do you recall if the Plex icon was still showing in the system tray when you restarted at 10:16?
If it is a hang, then would need a process dump to go with the logsThere is evidence of a crash at 17:49 on 19th October and one at 22:58 on 18th October
I do not have logs for these - one of them (the 17:49 crash) is currently under investigation and is to do with switching between hardware and software transcoding. This specific crash can be avoided in the interim by disabling hardware transcodingThe crash at 22:58 on 18th October, I would need to see logs for it (if it repeats itself)
And if you do get a hang as opposed to a crash - (check windows task manager to see if Plex Media Server.exe is still running), then would need process dump as well as logs
If it is a crash and Plex Media Server.exe does not show in windows task manager, then look for a dmp file within
C:\Users\admin\AppData\Local\Plex Media Server\Crash Reports\1.9.5.4339-46276db8d\PLEX MEDIA SERVERbefore you restart the server and copy the file out - in case there is an issue with uploading it
Sorry if those logs are no good. Each crash this time the icon was not there anymore. I also disabled hardware transcoding yesterday and just had another crash about 15 minutes ago.
I unfortunately already restarted the server and did not look for a dmp file, but if it happens again I will check again.
And dont know if I should make a new thread here or not, dont know if my recent issues are at all related.
@mashuto I have moved the posts to a separate topic as the issue was not unresponsiveness but actual process crashes
Do capture the logs after every crash until we get a matching set : logs + crash reports
I have been having crashes almost daily since sometime in the 1.9.X series of versions, I’m not sure exactly when it started, but I believe 1.8.X was more stable. I’ve attached the log files from just a moment ago in which you can see that the PMS log stopped at 19:00 and resumed at 21:55 when I noticed the server was down and restarted it. I have noticed the CPU on my Synology pegged out at 95%+ from the PMS process only a couple of minutes prior to a crash, but I did not capture the logs from that particular event. I also have the crash reports set to send to Plex.
Synology: 6.1.3-15152 Update 8
HDHR: 20170930
@tarrick said:
I have been having crashes almost daily since sometime in the 1.9.X series of versions, I’m not sure exactly when it started, but I believe 1.8.X was more stable. I’ve attached the log files from just a moment ago in which you can see that the PMS log stopped at 19:00 and resumed at 21:55 when I noticed the server was down and restarted it. I have noticed the CPU on my Synology pegged out at 95%+ from the PMS process only a couple of minutes prior to a crash, but I did not capture the logs from that particular event. I also have the crash reports set to send to Plex.Synology: 6.1.3-15152 Update 8
HDHR: 20170930
Thanks for the logs. Can see a crash that must have happened between Nov 03, 2017 19:00:00 and 21:55:11
However for some reason no crash report was produced or uploaded.
I do have a crash report from Nov 01, 2017 22:00:04 which i will report to the development team, however , there is no evidence to indicate if the 3rd November was the same
@sa2000 said:
@tarrick said:
I have been having crashes almost daily since sometime in the 1.9.X series of versions, I’m not sure exactly when it started, but I believe 1.8.X was more stable. I’ve attached the log files from just a moment ago in which you can see that the PMS log stopped at 19:00 and resumed at 21:55 when I noticed the server was down and restarted it. I have noticed the CPU on my Synology pegged out at 95%+ from the PMS process only a couple of minutes prior to a crash, but I did not capture the logs from that particular event. I also have the crash reports set to send to Plex.Synology: 6.1.3-15152 Update 8
HDHR: 20170930Thanks for the logs. Can see a crash that must have happened between Nov 03, 2017 19:00:00 and 21:55:11
However for some reason no crash report was produced or uploaded.
I do have a crash report from Nov 01, 2017 22:00:04 which i will report to the development team, however , there is no evidence to indicate if the 3rd November was the same
New crash, restarted the server almost immediately this time as I noticed it the moment it happened since it crashed while I was watching a show. Logs attached. The resource monitors in Synology appear to only start recording when they’re open so it’s hard to get resource utilization from before the crash, but if there’s any other information that you need, I can try to provide and I can continue to provide logs after crashes if you like.
@tarrick said:
@sa2000 said:
@tarrick said:
I have been having crashes almost daily since sometime in the 1.9.X series of versions, I’m not sure exactly when it started, but I believe 1.8.X was more stable. I’ve attached the log files from just a moment ago in which you can see that the PMS log stopped at 19:00 and resumed at 21:55 when I noticed the server was down and restarted it. I have noticed the CPU on my Synology pegged out at 95%+ from the PMS process only a couple of minutes prior to a crash, but I did not capture the logs from that particular event. I also have the crash reports set to send to Plex.Synology: 6.1.3-15152 Update 8
HDHR: 20170930Thanks for the logs. Can see a crash that must have happened between Nov 03, 2017 19:00:00 and 21:55:11
However for some reason no crash report was produced or uploaded.
I do have a crash report from Nov 01, 2017 22:00:04 which i will report to the development team, however , there is no evidence to indicate if the 3rd November was the sameNew crash, restarted the server almost immediately this time as I noticed it the moment it happened since it crashed while I was watching a show. Logs attached. The resource monitors in Synology appear to only start recording when they’re open so it’s hard to get resource utilization from before the crash, but if there’s any other information that you need, I can try to provide and I can continue to provide logs after crashes if you like.
Thank you. It is probably another manifestation of the bug that led to the crash on 1st November. Appears to be when starting a scheduled recording. I have passed this to the development team
@sa2000 said:
@tarrick said:
@sa2000 said:
@tarrick said:
I have been having crashes almost daily since sometime in the 1.9.X series of versions, I’m not sure exactly when it started, but I believe 1.8.X was more stable. I’ve attached the log files from just a moment ago in which you can see that the PMS log stopped at 19:00 and resumed at 21:55 when I noticed the server was down and restarted it. I have noticed the CPU on my Synology pegged out at 95%+ from the PMS process only a couple of minutes prior to a crash, but I did not capture the logs from that particular event. I also have the crash reports set to send to Plex.Synology: 6.1.3-15152 Update 8
HDHR: 20170930Thanks for the logs. Can see a crash that must have happened between Nov 03, 2017 19:00:00 and 21:55:11
However for some reason no crash report was produced or uploaded.
I do have a crash report from Nov 01, 2017 22:00:04 which i will report to the development team, however , there is no evidence to indicate if the 3rd November was the sameNew crash, restarted the server almost immediately this time as I noticed it the moment it happened since it crashed while I was watching a show. Logs attached. The resource monitors in Synology appear to only start recording when they’re open so it’s hard to get resource utilization from before the crash, but if there’s any other information that you need, I can try to provide and I can continue to provide logs after crashes if you like.
Thank you. It is probably another manifestation of the bug that led to the crash on 1st November. Appears to be when starting a scheduled recording. I have passed this to the development team
It’s anecdotal so take it for what you will, but the crashes have kept continuing at a minimum once every other day but sometimes as often as twice a day. After you pointed out that the crashes appeared to occur when starting a recording which coincided with my own observations, it had gotten frustrating to the point that I even setup a scheduled task to run 5 minutes after every hour to start the PMS service if it were stopped. However, I finally decided to roll back to 1.8.3 which I remembered being much more stable and I have not experienced a crash yet after 3 days now.
@tarrick - a fix for this old crashes issue has now been released in beta 1.15.2.793
See Release Notice
- (DVR) Fix a long-standing but rare crash when starting a live tune (#7790)
1 Like
