@ChuckPA said:
It’s generally bad form however, in this case, what you’re experiencing are hangs. The database reports at locked. I see you are running 1.10.1. I recommend you stop PMS, reboot the machine, reinstall the previous version (1.10.0) which is public and verify the same behavior.
Got it. I’ve uninstalled 1.10.1 and reinstalled 1.10.0. I’ll post if it doesn’t solve the problem.
Thanks for the help and sorry for the the hijack.
@ChuckPA said:
@thompry said:
Plex crashed again. I have attached the log for this crash. Plexpy alerted me that Plex Media Server stopped working at 21:18. I had to manually exit out of Plex on the taskbar and go into Task Manager and end the Process before I could get it to start back up.The transcoder crashed, not PMS.
Dec 08, 2017 21:15:54.666 [13936] DEBUG - Using default transcode duration of 120 minutes Dec 08, 2017 21:15:54.666 [13936] DEBUG - Started session successfully: fdf5ea4dc0a1633ad0c2826324d060f6 Dec 08, 2017 21:15:54.667 [31588] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\PlexTranscoder.exe' exit code for process 30284 is 1 Dec 08, 2017 21:15:54.669 [7740] DEBUG - [TranscodeOutputStream] Input processing thread started at offset 0 for -1 bytes. Dec 08, 2017 21:15:54.669 [31588] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\PlexTranscoder.exe' exit code for process 30284 is 1 Dec 08, 2017 21:15:54.669 [31588] DEBUG - Streaming Resource: Terminating session 182A09E8:fdf5ea4dc0a1633ad0c2826324d060f6 which is using 3953kbps of WAN bandwidth. Used is now 72836kbps Dec 08, 2017 21:15:54.669 [31588] DEBUG - Streaming Resource: Terminating session 182A09E8:fdf5ea4dc0a1633ad0c2826324d060f6 which is using transcoder slot. Used slots is now 10 Dec 08, 2017 21:15:54.669 [31588] DEBUG - Streaming Resource: Terminated session 182A09E8:fdf5ea4dc0a1633ad0c2826324d060f6 with reason Conversion failed. The transcoder crashed or failed to start up. Dec 08, 2017 21:15:54.669 [21620] DEBUG - Killing job. Dec 08, 2017 21:15:54.669 [21620] DEBUG - Job was already killed, not killing again. Dec 08, 2017 21:15:54.670 [21620] DEBUG - Stopping transcode session fdf5ea4dc0a1633ad0c2826324d060f6What was being played at that time?
If you are uncertain, please recreate the failure, post that log set plus the XML (hover over item - get info - view XML). This will allow me to know what the transcoder was basing its actions on
The movie “Jingle All The Way” was starting up. I have uploaded the XML of it below. Would the transcoder crashing cause the plex server to immediately stop responding and kill all streams because that is what happens?
May I have the full log? I need to see the MDE and preceding steps as I requested in the full ZIP set. A log excerpt does not tell me enough
I posted the full logs in a previous post when I accidentally double posted. Here they are again attached below. If this isn’t what you need I apologize and don’t understand what else you need.
I missed that. I apologize. I’m reviewing them now.
I see the problem.
You have the transcoder temporary directory on a network share. This is not wise. File locking, which is required, is not supported over SMB shares.
Plex Media Server.log:Dec 08, 2017 21:19:28.690 [12668] ERROR - Failed to delete session directory (boost::filesystem::remove: The process cannot access the file because it is being used by another process: "O:\Transcode\Transcode\Sessions\plex-transcode-615aeb1f48f2008f2dcafda8b886f4d2-fef8593c-0226-4a56-8e6a-e7e78d9c2269\chunk-00385")
The error manifests as this in your logs.
Plex Media Server.5.log:Dec 08, 2017 21:00:17.256 [20720] ERROR - Throttle: timed out trying to read chunk 1
Plex Media Server.5.log:Dec 08, 2017 21:00:17.990 [17008] ERROR - Throttle: timed out trying to read chunk 1
This occurs because the transcoder for the DCA codec has two parts. One for audio and and the main transcoder for the video. When on a network share, without proper locking support, they cannot operate correctly.
If you create a directory on any hard drive attached to the machine, your issue will stop happening.
The transcode directory isn’t on a network drive. My O: drive is a PCIE SSD directly attached to the server. I have moved the directory to a standard ssd and the crashes still occur.
You’ve just exceeded my understanding of Windows. There is an OS level problem which is beyond my ability to help with.
I’m sorry I can’t be of more help.
Do you have a backup program or antivirus program that scans that folder? If so, don’t. This is a temp folder so no need to include this in those scans.
I have all backups and antivirus (including Windows Defender) disabled.
For the antivirus, are you using either ESET or Kaspersky. We have seen issues from these even when they are disabled. Only a total uninstall of these programs seems to help.
I don’t have any Antivirus installed other than the built in Windows Defender which is disabled. Is it possible that Plex is still somehow holding onto those transcode chunks when it tries to clear/or read them? This install of Windows is only a few weeks old and pretty much just has Plex running on it. As stated earlier, I reinstalled windows server 2016 because of this issue which the problem remained. 3+ months ago Plex Media Server would run for months without a single crash or issue.
I am seeing the message (ERROR - Failed to delete session directory) at times when the server is running fine as well so i’m not so certain that this is the cause of the crashes.
I’m not sure what’s causing the lock. I don’t think it’s another Plex process. Can you reproduce the crash, then check that “O:\Transcode\Transcode\Sessions” folder and using Windows File Explorer try to manually delete the files in there and see if you get a cannot access error. Then open up task manager and close each Plex tasks 1 at a time and then try deleting the files again. Keep going with the other Plex processes until you can delete those files. If you still can’t after closing all Plex tasks, then it would point to some other program on your computer.
I will try that the next time it crashes and let you know the results.
The server crashed a little while ago and I followed the steps you listed above and tried to delete the Transcode folder as I end each process one by one. Windows wouldn’t let me delete the folder until I ended easyaudioencoder.exe. This process was the last plex process I ended.
Another thing I would like to note from looking through the logs is it seems that the server crashes shortly after a bunch of items having to do with sync run. I checked plexpy and there were quite a few syncs that said error and quite a few that said processing or in progress even though nothing was being synced at the time. I know some of these items have been listed here for a couple of months. Could this possibly be causing the server issues? I went ahead and followed the instructions in the following link to delete the sync that were listed as error or in progress: https://www.reddit.com/r/PleX/comments/4j2pk5/remove_sync_entries_from_database_possible/
I have attached the portion of the log listing the Sync data that occurred right before the server crashed.
The server has still been crashing daily with pretty much the same data in the logs. easyaudioencoder.exe is the only process that is preventing the transcodes from being deleted. Even after all plex processes are closed the transcode folder can’t be deleted until easyaudioencoder.exe is forced to stop.
It just crashed again about 15 minutes ago. This time I had to end about 8 Python (32 bit) processes before windows would allow me to delete the Transcode folder. I checked each process and they were all running from: C:\Program Files (x86)\Plex\Plex Media Server (PlexScriptHost)
ok, that process is related to the transcoder so it sounds like Plex is trying to transcode a file and crashing. This crash is serious enough that it makes the rest of Plex not functional anymore. Since it did work for a little while, my guess is that you have a video file that is corrupted or somehow toxic to Plex’s transcoder. There is a sync job involving this file so when it tries to transcode this file to get it read for sync, it crashes. I cannot tell from your log snippet what file it might have been. Can you provide me with the full set of logs after the next crash.
The server has been crashing anywhere from 1 to 4 times per day for the past week or so. I have many logs saved for each one of the crashes and have attached one of the more recent below. The crash happened between 8:25 and 8:35 in these logs.
